8  Program FIPP : Filter Preset Program


8.1 Introduction

With the program FIPP you can define telegram-specific filters and triggers. If you start FIPP from LIAN (program LIAN: menu item <Run | FIPP>, see above), it is used for defining pre-filters or pre-triggers, i.e. the settings already have an effect while recording with SIMO. If the filters are only to have an effect while analysing the recording with TRAP, you have to call FIPP from TRAP (program TRAP: menu item  <Filter>).

The filter(s) serve to limit the recording/analysis to certain data records. For the simulation actions can be caused with the receipt of defined records. Therefore the possibility exists to define action-filters, that cause a send-sequence or send one or more message-buffers (TDB) .

Triggering means that you can define a telegram with the help of the protocol-specific filters and this telegram initiates recording/analysis. The number of the telegrams recorded afterwards can be determined by the user. Under <Date | Time> the recording/analysis can be limited to a certain time or period of time.

8.2 Funktion keys

[F1] Help on the current meu item
[Alt]-[X] Quit programm FIPP. 

8.3 Assignment of keys

8.3.1 Entry mask

The following key assignments apply for the entry fields of the telegram-specific filter and trigger masks.

[arrow right] Cursor right
[arrow left] Cursor left
[arrow down]
[Tab]
return

  
next field
[arrow up]
[Shift]-[Tab] 

previous field
[PgUp] previous OR-element (filter or trigger)
[PgDn] next OR-element (filter or trigger)
[F10] save settings and leave entry mask

Please note that the settings are subject to a plausbility check, that means only valid values can be set, otherwise the curser does not move. 

8.4 Menu commands

8.4.1 Filter

Definition of the pre- and / or action filters for recording or  postfilter for analysis.

As one is interested only in some specific parts of the recorded sets in most cases, it is possible to activate data-format-specific filters as well as for the recording as also for the later analysis of an archive. By setting the corresponding filters and triggers a carefully directed data preselection can be achieved, which results in a reduction of the data to be analized later.  

With the filter settings one distinguishes in principle between a pre-filter for recording and a post-filter for analysis. If you start  FIPP from LIAN it is used for defining pre-filters, i.e. the settings already have an effect while recording  with SIMO. If a post- filter is to be defined, FIPP has to be started from the program TRAP. The filter will then only have an effect when analysing the received and recorded records.

With the parameter <channel unlocked> you can exclude certain channels from recording / analysis.

If the filter field is activated for a selected channel the entry mask for defining the filter is opened. With the option <filter unlocked> the filter handling for a certain channel can be enabled or disabled. 

For the simulation actions can be caused with the receipt of defined records.Therefore the possibility exists to define action-filters, that cause a send-sequence  or send one or more message-buffers (TDB).

The setting of the action can be enabled or disabled with the option <action unlocked>  for a certain channel.

If you activate the action-field for a selected channel the entry mask for the action-filter definition is opened.

The analysis (postfilter) can be limited to a certain  number (<number [last(n)] records>)  of the data  records  last  received (<last(n) records>).

You can quit the  entry masks via  [F10]; the settings  are saved automatically.

The meaning of the fileds in detail:

Channel unlocked

With  this function  the recording  (SIMO) or the analysis (TRAP) can be  limited  to  particular channels.  This  option is  especially useful  for the analysis, since with it you can divide up the archive file into several  files for one channel each.

available settings :

n channel disabled
y channel enabled for transmitted and received data records
r channel enabled for received data records
t channel enabled for transmitted data records
Filter unlocked

available settings :

n filter handling for the current channel is disabled
y filter handling for the current channel is enabled
Filter settings

If you activate this option you can filter the recording and the analysis according to telegram-specific features; for this you can determine several filter masks linked with an OR-operator for one channel.

For the filter masks the following operators are valid:

= only values equal to 'from' are let through
# only values not equal to 'from' are let through
s only values less than 'from' are let through
g only values greater than 'from' are let through
r 'from' and 'to' define a valid range

Action unlocked

This option is only available for "pre-filters" ! !

available settings :

n action-filter disabled for the current channel
y action-filter enabled for the current channel
Action filter

The action-filter is described over telegram-specific features like a filter-setting. Additionally each action-filter requires an allocation to a sendbuffer or alternatively to a sendsequence

This option is only available for "pre-filters".

For the filter masks the following operators are valid:

= only values equal to 'from' are let through
# only values not equal to 'from' are let through
s only values less than 'from' are let through
g only values greater than 'from' are let through
r 'from' and 'to' define a valid range

Sendbuffer number ( from, from/to ) :

In correspondence with the actionfilter the messagebuffer "from" or the messagebuffers "from/to" is to be sent

Sequence-line number ( from, from/to  ) :

In correspondence with the actionfilter the message sequence is to be started at line number "from" or to be started at line-number "from" and to be ended at line-number "to".

Last (n) records

This option is only available for "post-filters".

The analysis is limited to a certain number of records last received.

If only the last n-records of a channel should be analysed, you enter in the option [Last (n) records] 'yes' and in <number [last(n)] records> the required number.

Is the output <last n-records> disabled, all records of the archive file get taken into account by the filter- and triggerhandling.

number last (n)
records

This option is only available for "post-filters".

Here the number (n) of the <last (n) records> is defined for the relevant channel.

 

8.4.2 Trigger

With a trigger you can define a condition (a record with certain characteristics) which triggers off the recording/analysis of a certain number of succeeding records.

If FIPP is started from LIAN it serves the definition of a pre-trigger, i.e. the trigger has already an effect when recording with SIMO.

If you want to define a post-trigger FIPP has to be started from TRAP. In this case the trigger only has an effect when analysing the received and recorded records.

With <date/ time> the recording/ analysis can be limited to a certain time or period of time.

With a <Stop trigger> ( a record with certain characteristics ) and/ or a <stop on error> you can define a stop condition which triggers off the recording/ analysis of a certain number of succeeding records.

This number is determined in the field <number of records after stop trigger>.

Is a <Start trigger> defined recording/ analysis starts with the satisfaction of the trigger condition.

With the option <Start unlocked> or <Stop unlocked> you can deactivate temporarily a trigger that has been  created  previously.

You can quit the entry masks via [F10]; then all settings are saved automatically.

The meaning of the fields in detail :

Date / Time

As a first  trigger  condition the  time span for recording can be fixed by the parameters [from:date/time] and [till:date/time].

When  analizing, these  parameters are occupied with the beginning and the  end of recording.

The recording is always limited to the period of time determined by the two date- and time-fields, recording is started at the set time [from: date/time] and ended  with [till: date/time].

number of records after stop trigger

Defines how many telegrams are to be recorded after the trigger condition has occured.

stop all channels

Defines, whether after satisfaction of the stop trigger condition recording or analyzing should be stopped on all channels or only on the channel where the stop trigger condition occurs.

Available settings :

n

stop only on the channel the stop trigger condition occurs

y stop all channels
Start unlocked

Available settings :

n trigger handling for the current channel is disabled
y trigger handling for the current channel is enabled
Start trigger

If you activate this option you can define telegram-specific Start-Trigger for recording and analysis; for this you can determine several trigger-masks linked with an OR-operator for one channel.

For trigger masks the following operators are valid:

= only values equal to 'from' are let through
# only values not equal to 'from' are let through
s only values less than 'from' are let through
g only values greater than 'from' are let through
r 'from' and 'to' define a valid range

Recording/Analysing starts when the trigger conditions had occured.

Stop unlocked

Available settings :

n trigger handling for the current channel is disabled
y trigger handling for the current channel is enabled
Stop trigger

If you activate this option you can define telegram-specific Start-Trigger for recording and analysis; for this you can determine several trigger-masks linked with an OR-operator for one channel.

For trigger masks the following operators are valid:

= only values equal to 'from' are let through
# only values not equal to 'from' are let through
s only values less than 'from' are let through
g only values greater than 'from' are let through
r 'from' and 'to' define a valid range

Recording/Analysing starts when the trigger conditions had occured.

Stop on error Recording/Analysing is stopped when an error occurs.

available settings

n Stop on error is disabled.for this channel 
y Stop on error is enabled.for this channel.

 

8.4.3 Output

This function gives an overview of the current filter and trigger settings on all four channels. The information can be either displayed on screen or output to printer.

8.4.4 File
Under this menu item you can <load> and <save> filter-files overall or per channel, view the contents of <directories>and <quit> temporarily the program.

8.4.4.1 Load

This function allows loading of the filter- and trigger-settings previously saved by means of <save>.

8.4.4.1.1 Filter overall

This function allows loading of filter- and trigger-settings previously saved by means of <save>. This filter/trigger-file includes settings for all 4 channels.

If you enter a DOS-wildcard ('*') in connection with the corresponding extension (default: '.VFL' for pre- or '.NFL' for postfilter), the filter files (FLT) of the current directory are displayed.

With the arrow keys you can select a certain file and load it with the Enter key.

If you want to view or select a different directory than the current one, you can also put a path in front of the file name.

8.4.4.1.2 Filter per channel

This function allows loading of filter- and trigger-settings previously saved by means of <save>.

This filter/trigger-file includes settings only for one channel.

If you enter a DOS-wildcard ('*') in connection with the corresponding extension (default: ' .FLT' for pre- and for postfilter) the filter files (FLT) of the current directory are displayed.

With the arrow keys you can select a certain file and load it with the Enter key.

If you want to view or select a different directory than the current one, you can also put a path in front of the file name.

8.4.4.2 Save

This function allows saving of filter- and trigger-settings. These setting can be loaded again with <load> at a later time.

8.4.4.2.1 Filter overall

This function allows saving of filter- and trigger-settings.

All filter- and trigger-settings are saved (except date/time). The created filter / trigger-file includes the settings for all 4 channels.

If you enter a DOS-wildcard ('*') in connection with the corresponding extension (default: '.VFL' for pre- or '.NFL' for postfilter), the filter files (FLT) of the current directory are displayed.

With the arrow keys you can select a certain file and load it with the Enter key.

If you want to view or select a different directory than the current one, you can also put a path in front of the file name.

8.4.4.2.2 Filter per channel

This function allows saving of filter- and trigger-settings.

All filter- and trigger-settings are saved ( except date/time ). The created filter / trigger-file includes the settings for one channel only.

If you enter a DOS-wildcard ('*') in connection with the corresponding extension (default: '.FLT' for pre- and for postfilter) the filter files (FLT) of the current directory are displayed.

With the arrow keys you can select a certain file and load it with the Enter key.

If you want to view or select a different directory than the current one, you can also put a path in front of the file name.

8.4.4.3 Directory

Gives an overview of the available files in a directory.

The indication can be specified with the usual DOS-wildcards. If you want to view a different directory than the current one, you can also include a path in front of the DOS-wildcards.

8.4.4.4 OS Shell

With this function you can quit FIPP temporarily. Enter EXIT into the command line in order to return.

8.4.5  Options

8.4.5.1 Configuration

This function gives a short overview of the protocol type and the data format with which each of the four channels has been parameterized.

8.4.5.2 Notebook

The notebook is a small editor with which you can make notes of the current session. The file size is fixed at 200 lines and 76 columns. Lines cannot be added or removed. With [F10] you exit the editor and store your input on hard disk in an ASCII file with extension .pin. The notebook can be called in all program parts (in SIMO in the main menu, elsewhere under menu item <Options | Notebook>).

8.4.6 Quit program FIPP

The current filter and trigger settings are saved in a standard protection file SIMO.VFL (pre-filters) or SIMO.NFL (post-filters) independent of a possible executed saving in a configuration file ( see menu item <save>). These files are automatically loaded with the start of the program. Then the program is ended.

 


MAYR Software

Wuerzburger Ring 39,  D 91056 Erlangen

Manual LIAN DOS


LIAN DOS Protocol Simulator and Analyzer
© Copyright 1991, 1996, 2001, 2006-2010 by Werner Mayr. All Rights reserved.