|
4.1.1 General Asynchronous PCM Capture ( protocol independent ) |
Telegram Structure |
|
In this case the telegram structure is unknown for the software. |
![]() |
|
With the channel button ( channel 1 ...12 ) on the bottom following settings are possible : |
| Interface |
For each channel any comport ( COM 1 till COM 24 ) can be selected. |
|||||
| Modem |
An individual modem can be installed and connected for each channel. LIAN 98 is able to process up to twelve modems in the range of COM1 till COM24 simultaneously. Select here the modem assigned to the selected channel. Normally this assignment will be recognized by LIAN 98 and the corresponding modem will be set. |
|||||
| Setup Modem |
The settings of the modem must be executed via the windows control panel "telephone and modems options". With this button you can check the modem settings and see if they correspond to the LIAN 98 configuration. |
|||||
| Connection type |
|
|||||
| RTS Leading delay |
0 ... 1000 msec |
|||||
| RTS Trailing delay |
0 ... 1000 msec |
| Baud rate |
Transmission speed : 25 - 115200 Baud ( variable ) |
| Data byte |
5, 6, 7, 8 Bit ( variable ) |
| Stop Bit |
1/ 1,5/ 2 Bit ( variable ) |
| Parity |
none, odd, even, (1) mark, (0) empty, ( variable ) |
| Timeout |
1 - 9999 msec ( variable ) |
|
Calculation of the timeout : |
|
The Timeout [ msec ] should be only a bit larger than the result of the
following calculation : |
Setting in the channel window |
![]() |
|
In the channel window no further settings are necessary. |
|
For the independent asynchronous PCM protocol no simulation is implemented. It is only suitable for recording of transmission data during the monitoring operation. |
|
Monitoring filters reduce capture on particular pre-defined data records. By setting the corresponding filters a carefully directed data preselection can be achieved, which results in a reduction of the data to be analyzed later. |
![]() |
| Filter released |
yes / no |
||||||||||
| protocol specific filter mask |
Here monitoring can be filtered for telegram specific values in which several OR-linked filter masks can be defined for the channel.
|
||||||||||
| add | Adds the next OR-element. | ||||||||||
| remove | Removes the current OR-element. |
|
For this protocol no simulation is implemented. Therefore all settings in the action filter are without effect. |
![]() |
| Action filter released |
yes / no |
||||||||||
| protocol specific filter mask |
The action filter is described over telegram specific features corresponding to a filter setting. Additionally each action filter requires an allocation to a send buffer or alternatively to a send sequence.
|
||||||||||
| Sendbuffer number ( from, from/ till ) |
In correspondence with the action filter the message buffer "from" or the message buffers "from/ till" are to be sent. |
||||||||||
| Sequence line number ( from, from/ till ) |
In correspondence with the action filter the send sequence is to be started at line number "from" or to be started at line number "from" and to be ended at line number "till". |
||||||||||
| add | Adds the next OR-element. | ||||||||||
| remove | Removes the current OR-element. |
|
With the receipt of a telegram pre-defined as start trigger, recording is started. |
![]() |
| Start trigger released |
yes / no |
||||||||||
| protocol specific trigger mask |
Here you can define telegram specific start triggers for monitoring in which several OR-linked triggers can be defined for the channel.
|
||||||||||
| add | Adds the next OR-element. | ||||||||||
| remove | Removes the current OR-element. |
|
Monitoring can also be stopped by telegram-specific filters and/ or "stop on error" after a defined number of following records. The number of the following records is defined in the field "records after stop on error/ stop trigger" in the global parameters of the VFL settings. |
![]() |
| Stop trigger released |
yes / no |
||||||||||
| protocol specific trigger mask |
Here you can define telegram specific stop triggers for monitoring in which several OR-linked triggers can be defined for the channel.
|
||||||||||
| add | Adds the next OR-element. | ||||||||||
| remove | Removes the current OR-element. |
|
Each alteration in the settings is displayed by an asterisk * in the caption title and will be only effective after saving. |
|
The received messages of all channels are entered binary into the archive file.
Before displaying on screen, the binary archived data are coverted to hexadecimal, decimal, binary and/ or ASCII format
and is set separately for each channel. |
![]() |
|
Because the user data of the the general asynchronous PCM protocol are not known, no plain text display is provided and therefore the different plaintext settings are ineffective. |
| Plaintext format | |
| Format 1, 2, 3, 4, 5 |
Not used and therefore without effect |
Error check during receipt |
| per character |
the start bit, the stop bit and the parity |
| per telegram |
Since the telegram may be unknown no further checks are made. |
| *** TimeOut ! |
During transmission of telegrams there may be no large pauses between the single characters. In case of timeout occurs it is assumed that it is the end of the telegram. The sensitivity is parameterized in the configuration ( timeout ). Normally a timeout is no error but it is stored in the PRO File together with the initial error for a better analysis of the faulty transmission line. |
| *E: COM-PORT ! |
Error during writing on the COM port. May be it is already occupied by by another program. |
| *E: Overflow ! |
Error message from the UART. This error is noted only in the PRO file. |
| *E: Parity ! |
Error message from the UART. This error is noted only in the PRO file. |
| *E: Start/ Stop ! |
Error message from the UART. This error is noted only in the PRO file. |
|
The parameter list is not used for the independent asynchronous PCM protocol. |
|
Wuerzburger Ring 39, D 91056 Erlangen |
LIAN 98 Protocol Router, Simulator and Analyzer © Copyright 2001, 2006, 2011 by MAYOR GmbH. All Rights reserved. |