4.6.2 Protocol : Landis & Gyr TELEGYR 805 / 809

 

Telegram structure

The telegram structure of the protocol TELEGYR 805/809 is divided into 3 types. Their format is determined by DIN 19244. Formats with fixed and variable length are also admitted as the single control character E5H. Each telegram consists of single UART characters, each with one start bit, 8 bits information, one parity bit and one stop bit. The transmission of data bytes takes place after the principle "LSB first".
It is an asynchronous protocol with hamming distance = 4. The sequence of user data characters is terminated by a 8 bits checksum. The checksum is the arithmetic sum over all user data octets.

 

Information about the structure of the telegram see
<TELEGYR 805/ 809 : Telegram structure>

 

TELEGYR 805/ 809 : Configuration

 

 

With the channel button ( channel 1 ...12 ) on the bottom following settings are possible :

 

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

Attention, the connection type should be set to full duplex for monitoring !
 
Full duplex :

Most of the modems are full duplex and can transmit data in both directions simultaneously. DTE ( LIAN 98 ) and DCE ( Modem ) work simultaneously as transmitter and receiver. None of both transmitters has to wait for clearance for transmitting data. Therefore the signals RTS and CTS are not significant. Sure, LIAN 98 is setting the control signals RTS and DTR to 1 when it is ready for transmission and receipt but it does not check the signals CTS and DSR.
Half duplex :

In case of a half duplex connection DTE ( LIAN 98 ) as well as DCE ( Modem ) can work as transmitter and receiver, hereby only one data line ( 2-wire connection ) is available that can be used alternately for transmission or receipt of data. The control signals RTS and CTS are used in order to define the allocation of transmission or receipt. When LIAN 98 should work as transmitter it activates the signal RTS and waits for the confirmation of the modem via the signal CTS. After the receipt of the signal CTS the data are transmitted and after the transmission of the data the signal RTS is set to 0. In each other case LIAN 98 is working as receiver only.

As long as the LIAN 98 software is ready for transmission and receipt the signal DTR is activated in order to show the modem that LIAN 98 is ready for operation, as well the software expects an activated DSR signal from the modem.
RTS Leading delay

0 ... 1000 msec
This parameter ist only used for the connection type "half duplex" and is determined by the initial transient behaviour of the used transmission equipment.
The RTS Leading defines the delay time from activating RTS signal to transmitting the first character and is used for modems whithout the hardware handshake signals "RTS and CTS". In this case the "RTS signal" must be led back over the "CTS line" to the PC with the help of a brazing bridge in the monitor cable. Dependent of the used modem it may be necessary to connect additionally the DTR-pin with the DSR-pin.
This function is deactivated if the "Leading and the Trailing" is set to NULL and therefore the control signals are analyzed diectly from the modem.
RTS Trailing delay

0 ... 1000 msec
This parameter ist only used for the connection type "half duplex" and is determined by the final transient behaviour of the used transmission equipment.
The RTS Trailing defines the delay time from the last character transmitted up to the RTS signal is deactivated.
This function is deactivated, if the "Leading and the Trailing" is set to NULL.

 

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 )

 

TELEGYR 805/ 809 : Simulation

 

No simulation is implemented for the protocol TELEGYR 805/ 809. For this protocol LIAN 98 can only be used for monitoring.

 

TELEGYR 805/ 809 : Pre-filter / Pre-trigger

In order to make analysis for the received transmission blocks easier it is also possible to filter objects besides the telegram header. A telegram will only be passed if minimum one object gets through the filter. Only this objects will be displayed on the screen.

 

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.

 

TELEGYR 805/ 809 : Monitoring filters

 

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

With this option already set monitoring filters for one channel can be deactivated temporarily without deleting them.
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.

= Only values equal to 'from' are let through.
# Only values not equal to 'from' are let through.
< Only values less than 'from' are let through.
> Only values greater than 'from' are let through.
r 'from' and 'till' define a valid range
add Adds the next OR-element.
remove Removes the current OR-element.

 

TELEGYR 805/ 809 : Action filters

 

For protocol TELEGYR 805/ 809 is no simulation implemented. Therefore all settings in the action filter are without effect.

 

 

Action filter released

yes / no

With this option already set action filters for one channel can be deactivated temporarily without deleting them.
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.

= Only values equal to 'from' are let through.
# Only values not equal to 'from' are let through.
< Only values less than 'from' are let through.
> Only values greater than 'from' are let through.
r 'from' and 'till' define a valid range
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.

 

TELEGYR 805/ 809 : Start trigger

 

With the receipt of a telegram pre-defined as start trigger, recording is started.

 

 

Start trigger released

yes / no

With this option already set start triggers for one channel can be deactivated temporarily without deleting them.
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.

= Only values equal to 'from' are let through.
# Only values not equal to 'from' are let through.
< Only values less than 'from' are let through.
> Only values greater than 'from' are let through.
r 'from' and 'till' define a valid range
add Adds the next OR-element.
remove Removes the current OR-element.

 

TELEGYR 805/ 809 : Stop trigger

 

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

With this option already set stop triggers for one channel can be deactivated temporarily without deleting them.
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.

= Only values equal to 'from' are let through.
# Only values not equal to 'from' are let through.
< Only values less than 'from' are let through.
> Only values greater than 'from' are let through.
r 'from' and 'till' define a valid range
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.

 

TELEGYR 805/ 809 : Message display format

 

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.
( see also "FMT file - Display format" )

 

 

Plaintext format 1

Everything is displayed : Transmission block header and telegrams in the block

 

Plaintext format 2

Telegrams in the block without transmission block header

 

Plaintext format 3

Telegrams in the block with transmission block header and block information hexadezimal represented

 

Plaintext format 4

Transmission block header and block information hexadezimal represented
and short telegrams with fixed length and single characters

 

Plaintext format 5

Only short telegrams with fixed length and single characters

 

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.

 

TELEGYR 805/ 809 : Error messages

 

Error checks during receive

 

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 length ( 2 bytes ) and second start character in frames with variable length.

 

*** 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 ).
Normally a time out 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 in connection with a line error.
*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. 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.

 

TELEGYR 805/ 809 : Parameter list

 

The parameter list is not used for the protocol TELEGYR 805/ 809.

 

 

MAYOR GmbH

Wuerzburger Ring 39,  D 91056 Erlangen

Manual LIAN 98

LIAN 98 Protocol Router, Simulator and Analyzer
© Copyright 2001, 2006, 2011 by MAYOR GmbH. All Rights reserved.