When the expert mode is selected, all input options in the different lists are unlocked and can be changed. Concerns especially the sim lists of the particular protocols. Normally many parameters have been set correctly and must not be changed therefore.

Determines the name and the path of the archive file in which the received data are to be stored.

The received and the transmitted records of the activated channels are stored chronologically in binary format in a so-called archive for the later analysis. During recording, the transmission is permanently supervised on transmission errors. If an error occurs, an error message ( e.g. error BCC ) is stored in the archive file together with the message data.

The data are translated into plaintext when displaying on screen. The display format is set in the FMT file. ( see section <FMT file> )

The archive is organized as a ring buffer, i.e. if the archive is full, data are entered from the beginning of the buffer again and thereby the oldest information is overwritten. ( see section <ARC file> )

The archive size can be set from 1 to 32 Megabytes. An archive with 32 MB takes about 240 000 transmission records depending on the length of the particular telegrams.

Here the name and the path of the post filter file is determined that should be used for the analysis of the archive data. ( see section <NFL file> )

Here the name and the path of the send sequence file is determined, that is used for the background transmission ( e.g. Simulation ).

A sequence describes a simple procedure and can take in up to 200 instructions ( line 0... 199 ) Several telegrams from different TDB buffers can be linked to a sequence. A small set of commands is put at your disposal in order to control the transmission sequence.

The user can save several sequences in different TSB files and load them again when required. The advantage is that any number whatever you want of send buffers and send sequences can be created in advance and activated when required. ( see section <TSB file> )

Here the name and the path of the protocol file is determined in which the transmission errors are entered.

In addition to the entry of an error into the archive file further detailed information to the error, such as particular faulty transmitted characters with pre- and post history, is stored in a protocol file for later analysis. ( see section <PRO file> )

The user can deposit a personal commentary per channel with this command, which is saved in the configuration file. This commentary is not lost after finishing the recording. A text of maximum 22 characters can be entered.

Pre-selection of protocol type group over the company or the protocol standard of the master or the substation to be tested.

Selection of the protocol to be used for this channel.

The message format of the set protocol type can be selected.
( e. g. Modbus-IDA : RTU- or ASC format ).

Here the name and the path of the TDB buffer file is to be determined, which is used for the current channel.

One message buffer takes in one telegram that can be transmitted later. In total 500 buffers ( 0... 499 ) are available per channel; all together can be saved in a protocol-specific TDB file. The user can save several messages in different TDB files and load them again when required. ( see section <TDB file> )

Here the name and the path of the simulation list is to be determined, that is used for the current channel.

The protocol-specific simulation list file contains all settings that are necessary for the simulation of a certain protocol. ( see section <SIM file> )

Here the name and the path of the protocol-specific prefilter file is to be determined, that is used for the current channel during recording.
( see section <VFL file> )

Here the name and the path of the parameter list is to be determined, that is used for the current channel.

The protocol-specific parameter list file contains additionally settings that are necessary for the simulation of a certain protocol. ( see section <PAR file> )

With the selection [ yes/ no ] is determined if the channel is used during recording.

Default : TRUE = "YES" Button pressed !

With the selection [ yes/ no ] is determined if during transmission an output to screen is done.

The output of the received data during transmission can be suppressed in order to avoid disturbances at high transmission rates or low computer performance.

Default : TRUE = "YES" Button pressed !

With the selection [ yes/ no ] is determined if during transmission an entry into the archive file is done or not.

The suppression of this entry can be suitable in order to avoid errors caused by a low computer performance. ( see section <ARC file> )

Default : TRUE = "YES" Button pressed !

With the selection [ yes/ no ] is determined if during transmission an entry into the protocol file is done or not.

The suppression of this entry can be suitable in order to avoid errors caused by a low computer performance. ( see section <PRO file>)

Default : TRUE = "YES" Button pressed !

With the selection [ yes/ no ] is determined, whether to use between link- and application layer the RDB file or not.

Default : TRUE = "YES" Button pressed !
This default setting can only be changed in the expert mode.

With the selection [ yes/ no ] is determined, whether in addition to the usual simulation also telegrams from the SDB file to be sent.

Default : FALSE = "NO" Button pressed !
This default setting can only be changed in the expert mode.