|
4.7.3 Protocol : Siemens SINAUT ST7 |
Telegram structure |
|
The SINAUT ST protocol uses the telegram frames FT1.2, FT2 and FT2+ following the standard DIN19244 und IEC60870. Only telegram
format FT1.2 is realized in LIAN 98 at the moment. Formats with fixed and variable length are also admitted as the single characters E5H and A2H. |
|
Information about the structure of the telegram see |
![]() |
|
With the channel button ( channel 1 ...12 ) on the bottom following settings are possible : |
|
Each character has one start bit ( binary = 0 ), 8 information bits and normally one even parity bit and one stop bit ( binary = 1 ). |
| 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 |
|
|
In the polling mode ( unbalanced ) LIAN 98 simulates a MASTER and can communicate with up to 32 connected substations simultaneously. |
![]() |
| Station number ( Address of the target station ) |
All telegrams to be sent are
provided with the station number of the SIM list during master
simulation. .Exception for unbalanced mode : |
| Target TLN Number |
|
| Source TLN Number |
|
| Response timeout |
1 - 30 000 msec |
| Number of frame retries |
0 - 255 |
| Enable clock synchronization |
yes / no |
| Clock SYNC cycle time |
1 - 1440 minutes |
| Clock SYNC command |
TDB buffer number where the organizational telegram ( ORG 256 ) is stored. |
| Use system date/ time |
yes / no |
| Enable general interrogation |
yes / no |
| GI cycle time |
1 - 1440 minutes |
| GI command |
TDB buffer number where the organizational telegram ( ORG 0 ) is stored. |
|
|
|
|
Insert scan addresses Number of addresses delete insert |
Unbalanced : ( party line ) |
| Disable automatic scan |
Unbalanced : yes / no |
| Polling |
Unbalanced : |
| Scan delay |
Unbalanced : 0 - 30 000 msec |
|
|
|
| Acknowledge |
Unbalanced : |
![]() |
| Station number |
All telegrams to be sent will be provided with station number out of the SIM list during slave simulation. |
| Source TLN number |
All telegrams to be sent will be provided with the source TLN number out of the SIM list during slave simulation. |
| Target TLN number |
All telegrams to be sent will be provided with the target TLN number out of the SIM list during slave simulation. |
| Response timeout |
Balanced : 1 - 30 000 msec |
| Number of frame retries |
Balanced : 0 - 255 |
| Enable clock synchronization |
yes / no |
| Set new system date/ time |
yes / no |
| Time correction ( for system time of the PC ) |
0 - 9 999 msec ( correction of
transmission time ) |
| Clock SYNC command |
TDB buffer number where the organizational telegram ( ORG 256 ) is stored. |
| Use system date/ time |
yes / no |
|
|
|
| Acknowledge |
Unbalanced : |
SINAUT ST7 : Simulation procedures |
Simulation of the communication services : |
| Station initialization |
|
| Data acquisition by cyclic polling ( unbalanced ) |
|
Simulation of the application functions : |
| Cyclic data transmission |
|
| Acquisition of events ( unbalanced ) |
|
| General interrogation |
The general interrogation is used in
order to update the controlled station after the initialization or when
the controlling station detects a loss of information. |
| Clock synchronization |
Date and time of controlled stations are initially synchronized by the controlling station after initialization and afterwards re-synchronized periodically. |
| Command transmission |
|
|
It is absolutely necessary to set the start byte ( 10H or 68H ) for the filter- and trigger settings. With the start byte is determined whether the filter definition is valid for a telegram with fíxed length or a telegram with variable length. |
|
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, object number and information elements |
![]() |
| Plaintext format 2 |
No header is displayed : Object number and information elements |
![]() |
| Plaintext format 3 |
No header and object number is displayed : Only information elements are displayed |
![]() |
| Plaintext format 4 |
No object number and information element is displayed : Only telegram header is displayed |
![]() |
| Plaintext format 5 |
No information element is displayed : Only telegram header and object 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 receive |
| per character |
the start bit, the stop bit and the even 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, 10H, E5H ( or A2H ). 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: DIR bit ! |
Direction bit has an incorrect value |
| *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: ASDU address ! |
The received TLN number is incorrect or the entry in the SIM list is wrong. |
| *E: Sequence ! |
The telegram counter ( TC ) in the telegram is wrong. |
| *E: TypeID ! |
The used TypeID is not provided. |
SINAUT ST7 : TypeID assignment list |
|
Unfortunately the TypeID is not recognizable out of the ST7 telegram. In the process system it is defined by the subscriber and the object number. In LIAN 98 an unambiguous TypeID is defined for each data type in order to display the information ( message, measurand ... ) in an easily readable plaintext and not only hexadecimal. With the help of the parameter list the correct typeID can be assigned to the objects of individual subscribers. Organizational telegrams are unambiguous and must not entered in the parameter list. |
![]() |
| line |
Line number : ( 1 ... 512 ) |
| SUB from |
from subscriber number : The assignment is valid for that subscriber number, if the parameter "SUB till" is not specified. Otherwise, the assignment applies to all subscriber numbers in the specified range. |
| SUB till |
till subscriber number : If this parameter is specified, the assignment is valid for the entire range of subscriber numbers. |
| OBJ from |
from object number : The assignment is valid for that object number, if the parameter "OBJ till" is not specified. Otherwise, the assignment applies to all object numbers in the specified range. |
| OBJ till |
till object number : If this parameter is specified, the assignment is valid for the entire range of object 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 ST7 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. |