|
4.6.1 Protocol : Landis & Gyr - SCTM Communication |
|
The transmission procedure is in accordance with the SCTM procedure ( coded serial tele-metering ) of the
company Landis & Gyr. A "Conversational Information Transfer" similar ISO 2629-1973 resp. ECMA 29 is used that includes additionally an
acknowledgement procedure with increased code security as well as the opportunity for multi point transmission. |
Telegram structure |
|
The telegram circulation is controlled by the master station ( ZS ) i.e. The RTU ( US ) replies only on inquiry. The analysis of the telegrams in monitoring direction is only possible in relation to the previously in control direction sent query. Therefore two channels corresponding with each other are used. One can select between channel 1 + 2 or 3 + 4. Recording in control direction ( Master -> RTU ) is done on channel 1 and recording in monitoring direction ( RTU -> Master ) on channel 2. The 2-channel recording has the advantage that RTU telegrams can be analyzed with the help of the previous master query. |
|
Information about the structure of the telegrams see |
![]() |
|
With the channel button ( channel 1 ...12 ) on the bottom following settings are possible : |
|
Each character has one start bit ( binary = 0 ), 7 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 |
7 bit ( variable ) |
| Stop bit |
1 bit ( variable ) |
| Parity |
even ( variable ) |
| Time out |
1 - 9999 msec ( variable ) |
Settings in the channel window |
![]() |
| Number of station fields |
0, 3, 5 or 8 |
|
|
![]() |
|
|
|
|
![]() |
|
|
|
|
|
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 three different plaintext settings. The plaintext format
is set separately for each channel. |
![]() |
| Plaintext format 1 |
Everything is displayed : Telegram header and information element |
![]() |
| Plaintext format 2, 3 |
No header is displayed : Only information element is displayed. |
![]() |
| Plaintext format 4, 5 |
No information element is displayed : Only telegram header is displayed. |
![]() |
|
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 parity. |
| per frame |
the start character, the frame checksum and the end character, 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 stop byte ( 16H ) is missing or set wrongly. |
| *E: Format ! |
The repetition of the length or the start characters in the message header are faulty. For a fixed frame telegram, may be the parameter "Number of link address fields" is not set correct. |
| *E: Checksum ! |
The message checksum in the checksum byte is incorrect. |
| *E: SYNC ! |
The receive routine initially searches for 68H, 10H, E5H ( oder 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 ( Z/ U ) is set wrong. |
| *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. |
|
The parameter list is not used for the Landis&Gyr SCTM protocol. |
|
Wuerzburger Ring 39, D 91056 Erlangen |
LIAN 98 Protocol Router, Simulator and Analyzer © Copyright 2001, 2006, 2011 by MAYOR GmbH. All Rights reserved. |