|
4.7.1 Protocol : Siemens SINAUT 8-FW PCM |
Telegram structure |
|
Das Telegrammformat ist an DIN 19244, Formatkasse FT 1.2 angelehnt. Im Datenteil wird SINAUT 8-FW Struktur übertragen. Damit werden die Vorteile, wie Datensicherung und PCM Byte-Struktur des normierten Telegrammes genutzt. |
|
Information about the structure of the telegram see |
![]() |
| Interface |
For each channel any COM port ( 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 modem 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 |
8 bit ( fixed ) |
| Stop bit |
1 bit ( variable ) |
| Parity |
even ( variable ) |
| Time out |
1 - 9999 msec ( variable ) |
| Transmission procedure |
|
|
|
![]() |
| Station number ( Address of the target station ) |
All telegrams to be sent are provided with the station number out of the SIM list during master simulation. If a station number unequal zero is inserted in the telegram ( TDB buffer ), the telegram will be transmitted unchanged with this number already inserted. |
| Response timeout |
1 - 30 000 msec |
| Number of frame retries |
0 - 255 |
| Send start-up acknowledgement command |
yes / no |
| Send MSC quittance command |
yes / no |
| Enable test procedure |
yes / no |
| Test cycle time |
0 - 255 seconds |
| Test command |
TDB buffer number where the test command ( CDH 01 ) is stored. |
| Enable general interrogation |
yes / no |
| GI cycle time |
1 - 1440 minutes |
| GI command |
TDB buffer number where the organizational telegram ( CDH 06 ) is stored. |
![]() |
| Station number |
All telegrams to be sent are provided with the station number out of the SIM list during slave simulation. If a station number unequal zero is inserted in the telegram ( TDB buffer ), the telegram will be transmitted unchanged with this number already inserted. |
| Response timeout |
1 - 30 000 msec |
| Number of frame retries |
0 - 255 |
| Send Error bit pattern |
yes / no |
| Send Cause of stop |
yes / no |
| Send System error Bit Map |
yes / no |
| Acknowledge test command, Send test record |
yes / no |
|
|
|
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 the simulation and execution of data tests actions can be caused with the receipt of defined records. Therefore the possibility exists to define action filters, that effect the transmission of a send-sequence or transmit one or more message buffers ( TDB ). |
![]() |
| 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 sent and received messages of all channels are entered binary into the archive file.
Before displaying on screen, the binary archived data are coverted to an easily readable procedure specific plaintext.
In order to optimize the representation it can be chosen between five different plaintext settings. The plaintext format
is set separately for each channel. |
![]() |
| Plaintext format 1 |
Everything is displayed : Telegram header, telegram number and information elements |
![]() |
| Plaintext format 2 |
No header is displayed : Only telegram number and information elements |
![]() |
| Plaintext format 3 |
No header and telegram number is displayed : Only information elements are displayed |
![]() |
| Plaintext format 4 |
No telegram number and information element is displayed : Only telegram header is displayed |
| Plaintext format 5 |
No information element is displayed : Only telegram header and telegram number |
![]() |
|
Additional to the plaintext output the transmission data can also be displayed in hexadecimal, decimal, ASCII, binary ( LSB first ) or binary ( MSB first ). Of course the plain text output can also be deactivated in order to display the transmission data only e.g. hexadecimal. |
![]() |
Error checks during receipt |
| per character |
the start bit, the stop bit and the parity bit. |
| per frame |
the start character, the frame checksum and the end character and the |
| *** TimeOut ! |
Within a telegram, there may be no pause between characters. In case of timeout
occurs it is assumed that it is the end of the telegram and the telegram check is started. The sensitivity can be parameterized in the
configuration ( timeout ). |
| *E: COM-PORT ! |
Error during writing on the COM port. May be it is already occupied by another program. |
| *E: Length ! |
The length of the telegram is wrong. For telegrams with fixed length the length is not 5. |
| *E: Format ! |
The repetition of the length or the start characters ( 68H ) in the message header are faulty, or the stop byte ( 16H ) is missing or set wrongly. |
| *E: Checksum ! |
The message checksum in the checksum byte is incorrect. |
| *E: SYNC ! |
The receive routine initially searches for 68H or 10H. Each other character is noted as synchronization error and inserted in the PRO file. |
| *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. |
Error checks during simulation |
| *E: unexpected ! |
The respond at this time was not expected. |
| *E: Link address ! |
The received station number is incorrect or the entry in the SIM list is wrong. |
| *E: Sequence ! |
The telegram counter ( MSC ) in the received telegram does not correspond to the MSC expected by LIAN 98. This error message can occur at the beginning after switching on the RTI simulation, when the MSC of the master and the substation are not still synchronized. Subsequently LIAN 98 takes over the new MSC of the received telegram and expects in the next telegram a MSC increased by one. |
SINAUT 8-FW PCM : TypeID assignment list |
|
Unfortunately the TypeID is not recognizable out of the Sinaut 8-FW telegram in monitoring direction. In the process system it is assigned data definitions to the telegram number. In LIAN 98 an unambiguous TypeID is defined for each data type in order to display the information ( indications, measurands ... ) in an easily readable plaintext and not only hexadecimal. With the help of the parameter list the correct typeID can be assigned to the telegram numbers. Assignments can vary from station to station. Process telegrams in contol direction and organizational telegrams are unambiguous and must not entered in the parameter list. |
![]() |
| line |
Line number : ( 1 ... 512 ) |
| STA from |
Station number from : The assignment is valid for that station, if the parameter "STA till" is not specified. Otherwise, the assignment applies to all stations in the specified range. |
| STA till |
Station number till : If this parameter is specified, the assignment is valid for the entire range of stations. |
| con |
Control direction : If this parameter is set to 1, the telegram number / type assignment is valid for telegrams in control direction. Otherwise, for telegrams in monitoring direction. |
| TNR from |
from telegram number : The assignment is valid for that telegram number, if the parameter "TNR till" is not specified. Otherwise, the assignment applies to all telegram numbers in the specified range. |
| TNR till |
till telegram number : If this parameter is specified, the assignment is valid for the entire range of telegram numbers. |
| TypeID |
Type of information : Type identification number for the process information in control or monitoring direction. |
|
The state of the delivery of the list is only to see as an example and certainly needs to be adapted to your plant. The definition of the telegram type numbers you will find in the S8FW chapter <Telegram structure>. |
|
Wuerzburger Ring 39, D 91056 Erlangen |
LIAN 98 Protocol Router, Simulator and Analyzer © Copyright 2001, 2006, 2011 by MAYOR GmbH. All Rights reserved. |