3.6 NFL file : Post-Filter / -Trigger Settings for the Analysis

 

Offers the possibility to define telegram-specific filters and triggers that control analysis of recorded data.

Filters and triggers for the analysis of the recorded data :

Analysis filter

Post-filters help to limit analysis on particular data records in advance exactly defined. As one is interested only in some specific parts of the records in most cases, it is possible to activate data format specific filters, in which several OR-linked filter masks can be defined for a channel. By setting corresponding filters and triggers a reduction of the data to be analyzed can be achieved. Furthermore the possibility exists to split the archive data in several files ( e.g. one per channel )

Start trigger

A telegram can start analysis with the help of protocol specific filters whereby the number of the following recorded telegrams can be determined by the user.

Stop trigger

Analysis can also be stopped with the help of a telegram-specific filter after a defined number of following records. If Stop on error is activated, monitoring is stopped after a certain number of following records as soon as an error occurs. The number of the following records is defined in the field Records after stop on error/ stop trigger in global parameters.

Time trigger

With date and time analysis can be limited to a certain time or period of time.

 

Parameters global

 

 

General settings valid for all channels

 

Start analysis
( date / time )

With date and time can be defined, when analysis should be started.

Stop analysis
( date / time )

With date and time can be defined, when analysis should be stopped.

Start all channels

Determines, whether after satisfaction of the start-trigger condition analysis should be started for all channels or only for the channel the start-trigger condition has occurred.

Stop all channels

Determines, whether after satisfaction of the stop trigger condition analysis should be stopped for all channels or only for the channel the stop trigger condition has occurred.

Records after stop on error / stop trigger

The number of following records after stop on error or stop trigger has occurred.

 

Parameters corresponding to a channel : Channel 1 ...12

 

Channel released

Analysis can here be limited to particular channels. Therefore the possibility exists, to split the archive file separately after channels.

yes Channel enabled for transmitted and received data records
no Channel disabled
recv Channel enabled for received data records
send channel enabled for transmitted data records
Last (n) records

The analysis is limited to a certain number of records last received. If only the last n-records of a channel should be analyzed, one activates the option <Last (n) records> and enters 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 trigger-handling.
Number (last n) records

Defines the number (n) of the function Last (n) records for the corresponding channel.

 

Filters for analysis

 

 

Filter released

With this option already set filters for one channel can be deactivated temporarily without deleting them.

protocol-specific filter mask

yes / no

Here analysis can be filtered after telegram-specific features in which several OR-linked filter masks can be defined for one channel.

= only values equal to 'from' are let through
# only values not equal to 'from' are let through
< only values less than 'from' are let through
> only values greater than 'from' are let through
r 'from' and 'to' defines a valid range
add Adds the next OR-element.
remove Removes the current OR-element.

 

Start trigger

 

 

Start trigger released

yes / no

With this option triggers already set for one channel can be deactivated temporarily without deleting them.

protocol-specific trigger mask

Here you can define telegram specific start triggers for the analysis in which several OR-linked triggers can be defined for one channel.

= only values equal to 'from' are let through
# only values not equal to 'from' are let through
< only values less than 'from' are let through
> only values greater than 'from' are let through
r 'from' and 'to' defines a valid range
add Adds the next OR-element.
remove Removes the current OR-element.

 

Stop trigger

 

 

Stop trigger released

yes / no

With this option triggers already set for one channel can be deactivated temporarily without deleting them.

protocol-specific trigger mask

Here you can define telegram specific stop triggers for the analysis in which several OR-linked triggers can be defined for one channel.

= only values equal to 'from' are let through
# only values not equal to 'from' are let through
< only values less than 'from' are let through
> only values greater than 'from' are let through
r 'from' and 'to' defines a valid range
add Adds the next OR-element.
remove Removes the current OR-element.

 

Each alteration in the configuration is displayed by an asterisk * in the caption title and will be only effective after saving.

 

MAYOR GmbH

Wuerzburger Ring 39,  D 91056 Erlangen

Manual LIAN 98

LIAN 98 Protocol Router, Simulator and Analyzer
© Copyright 2001, 2006, 2011 by MAYOR GmbH. All Rights reserved.