|
4.2.2 Protocol : IEC 60870-5-102 |
Telegram structure |
|
IEC 60870-5-101 protocol standard admits only frame format FT 1.2 defined in IEC 60870-5-1 ( Transmission frame
formats ). Formats with fixed and variable block length are admitted. Also the single control characters E5H is admissible |
|
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 ), 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 ) |
| Timeout |
1 - 9999 msec ( variable ) |
| Transmission procedure |
|
Settings in the channel window |
![]() |
| Link address fields |
( 0 not used for IEC 102 ) 1... 2, structured or unstructured |
| ASDU address fields |
1... 2, structured or unstructured The ASDU address field contains of one or two octets in the data unit identifier. The length of the common address of the ASDU is a parameter defined by the system. |
| Signature |
yes / no |
|
In the polling mode ( unbalanced ) LIAN 98 simulates a MASTER and can communicate with up to 32 connected meter deveices simultaneously. |
![]() |
| Link address ( address of the target station ) |
All telegrams to be sent are provided with the link address of the SIM list during master simulation. |
| Address of ASDU ( address of the target station ) |
All telegrams to be sent are provided with the ASDU address of the SIM list during master simulation. |
| Response timeout |
1 - 30 000 msec |
| Number of frame retries |
0 - 255 |
| Enable station initialization |
yes / no |
| Request link status |
TDB buffer number where the message "Request link status" ( PRM = 1, function 9 ) is stored. |
| Reset of remote link |
TDB buffer number where the message "Request link status" ( PRM = 1, function 0 ) is stored. |
| Enable Login / Logout |
yes / no |
| Start session |
TDB buffer number where the private LOGIN command "Start session and send access key" ( ID 183, COT 6 ) is stored. |
| Finish session |
TDB buffer number where the private LOGOUT command "Finish session" ( ID 187, COT 6 ) is stored. |
| Read Product specification |
yes / no |
| Enable clock synchronization |
yes / no |
| Use system date/ time |
yes / no |
| Clock SYNC cycle time |
1 - 1440 minutes |
| Clock SYNC command |
TDB buffer number where the private command "C_CS_TA_2" ( ID 181, COT 6 ) is stored. |
|
Insert scan addresses Number of addresses delete insert |
Unbalanced : ( party line ) |
| Disable automatic station scan |
Unbalanced : yes / no |
| Request user data class 1 |
Unbalanced : |
| Request user data class 2 |
Unbalanced : |
| Scan delay |
Unbalanced : 0 - 30 000 msec |
| ACTCON response timeout ( activation confirmation ) |
This parameter defines the time in seconds that the program LIAN 98 as primary station at most has to wait for an "ACTCON Respond" ( COT 7 ) or "DEACTCON Respond" ( COT 9 ) before the message "*E: ACTCON missing !" is displayed. |
| ACTTERM response timeout ( termination activation ) |
This parameter defines the time in seconds that the program LIAN 98 as primary station at most has to wait for an "ACTTERM Respond" ( COT 10 ) before the message "*E: ACTTERM missing !" is displayed. |
![]() |
| Link address |
All telegrams to be sent will be provided with the link address out of the SIM list during slave simulation. |
| Address of ASDU |
All telegrams to be sent will be provided with the ASDU address out of the SIM list during slave simulation. |
| Response timeout |
Balanced : 1 - 30 000 msec |
| Number of frame retries |
Balanced : 0 - 255 |
| Station initialization |
Balanced : yes / no |
| Request link status |
Balanced : |
| Reset of remote link |
Balanced : |
| End of initialization |
yes / no |
| Enable clock synchronization |
yes / no |
| Set new system date/ time |
yes / no |
| Time correction ( for system time of the PC ) |
0 - 9 999 msec |
| Use system date/ time ( for TypeID 72 ) |
yes / no The system time of the PC will be token over before sending M_TI_TA_2 ( ID 72, COT 5 ) if this parameter is activated. Otherwise the telegram remains unchanged as before edited by the user. |
| Use E5H for respond on Request data class 2 |
Unbalanced : yes / no |
| Use only data class 2 messages |
Unbalanced : yes / no |
| Generate ACTCON respond |
yes / no |
| Generate ACTTERM respond |
yes / no |
| ACTTERM delay time |
This parameter defines the time in seconds that the program LIAN 98 delays the transmission of the "Activation Termination" respond ( COT 10 ). |
|
IEC 60870-5-102 : Respond on primary functions ( quittances ) |
![]() |
|
LIAN 98 receives a message with one of the following function codes from a primary ( PRM = 1 ) station
and will send the message in the TDB buffer you have specified. |
Function code numbers used from the primary station in the control field ( PRM = 1 ) |
| Function | Frame type | Service function | FCV |
| 0 | Send/ CONFIRM expected | Reset remote link | 0 |
| 1 | Reserved | ||
| 2 | Reserved | ||
| 3 | Send/ CONFIRM expected | User data | 1 |
| 4 | Send/ CONFIRM expected | User data | 0 |
| 5 | Reserved | ||
| 6 | Reserved for special use by agreement. | ||
| 7 | Reserved for special use by agreement. | ||
| 8 | Reserved | ||
| 9 | Request/ RESPOND expected | Request status of link | 0 |
| 10 | Unbalanced : Request/ RESPOND expected | Request user data class 1 | 1 |
| 11 | Unbalanced : Request/ RESPOND expected | Request user data class 2 | 1 |
| 12 | Reserved | ||
| 13 | Reserved | ||
| 14 | Reserved for special use by agreement. | ||
| 15 | Reserved for special use by agreement. |
Function code numbers used from the secondary station in the control field ( PRM = 0 ) |
| Function | Frame type | Service function |
| 0 | CONFIRM | ACK: Positive Acknowledge |
| 1 | CONFIRM | NACK : Message not accepted, link busy |
| 2 | reserved | |
| 3 | reserved | |
| 4 | reserved | |
| 5 | reserved | |
| 6 | Reserved for special use by agreement. | |
| 7 | Reserved for special use by agreement. | |
| 8 | Unbalanced : RESPOND | User data |
| 9 | Unbalanced : RESPOND | NACK : Requested data not available |
| 10 | reserved | |
| 11 | RESPOND | Status of link or access demand |
| 12 | reserved | |
| 13 | Reserved for special use by agreement. | |
| 14 | Link service not functioning | |
| 15 | Link service not implemented |
IEC 60870-5-102 : Simulation procedures |
Simulation of the communication services : |
| LIAN 98 orientates to the function code and the PRM bit in the control field of the link layer.
The parameter [response timeout] determines the time in milliseconds that LIAN 98 after transmitting a primary message at most has to wait for
an acknowledge before the transmission is repeated or a new message is
sent. Via the parameter [number of frame retries] it is defined how many times the message is to
be repeated. As long as the program LIAN 98 is waiting for an acknowledge no further telegram is sent. Send
records are put down in the send list temporarily and will be sent after the
receipt of the acknowledge. |
| Station initialization |
The primary station synchronizes its link with the
secondary station by transmitting
"Request status of link" ( FKT = 9 ) and "Reset of remote link" ( FKT = 0 ). The
secondary station responds with
"Status of link" ( FKT = 11 ) and "ACK" ( FKT = 0 ) and when the "ACK" is received
of the primary station the connection is established. |
| Data acquisition by polling ( unbalanced ) |
Data acquisition is used in unbalanced data transmission procedures to update
the controlling station with
actual states of process variables in the controlled stations. The controlling station performs polling by interrogating ( function code
10 and 11 ) the controlled stations sequentially. Controlled stations may
only transmit when they are polled. |
![]() |
| Reset remote link in unbalanced mode |
Simulation of the application functions : |
| Acquisition of events ( unbalanced ) |
There are two classes of data specified, class 1 data contains spontaneous data and class 2 data contains
cyclic data. Also defined is the link service "Request user data class 2" (
FCT 11 ) used for polling controlled
stations. Two consequences are possible in each controlled station when the polling telegram is received: |
|
|
|
| Clock synchronization |
Date and time of controlled stations are initially synchronized by the controlling station after initialization
and afterwards re-synchronized periodically. |
|
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 |
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 |
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 |
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 |
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 : |
![]() |
| Plaintext format 2 |
No link layer is displayed : |
![]() |
| Plaintext format 3 |
Only information objects/ elements are displayed. |
![]() |
| Plaintext format 4 |
Only link layer is displayed. |
| Plaintext format 5 |
No information objects/ elements are 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 length of the telegram is wrong. |
| *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. 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 ( 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. |
|
| |
| *E: TypeID ! |
The TypeID set in the ASDU is not provided. |
| *E: COT ! |
The cause of transmission set in the ASDU is not provided
or is not expected as response. |
| *E: Record address ! |
The record address set in the ASDU is not provided. |
| *E: INFOBJ length ! |
The length of the information object is not plausible. |
| *E: Signature ! |
The value of the signature in the message is incorrect. |
Error checks during simulation |
| *E: DIR bit ! |
Balanced : Direction bit is set wrong. |
| *E: PRM bit ! |
Primary message bit is set wrong. |
| *E: FCB bit ! |
Frame count bit is set wrong. |
| *E: FCV bit ! |
Frame count bit valid is not correct set. |
| *E: unexpected ! |
The respond at this time was not expected. |
| *E: Link state ! |
No station initialization is done, but in the message the FCV bit is already set to valid. |
| *E: Link address ! |
The received link address is incorrect or the entry in the SIM list is wrong. |
| *E: ASDU address ! |
The received ASDU address is incorrect or the entry in the SIM list is wrong. |
| *E: ACTCON missing ! |
An expected "Activation Confirm" ( COT 7 ) respond was not received within the parameterized "Response timeout". |
| *E: ACTTERM missing ! |
An expected "Activation Termination" ( COT 10 ) respond was not received within the parameterized response timeout.. |
IEC 60870-5-102 : ASDU parameter |
|
The ASDU list is used for the plausibility of the received telegrams, both for recording as well as for the simulation. Telegram types, used in the project, have to be marked in the list and the respective permissible causes ( COT ) and record address for this TypeID entered. Otherwise an error message is displayed when receiving the telegram ( E:TypeID, E:COT, *E:Record address ). |
![]() |
|
Wuerzburger Ring 39, D 91056 Erlangen |
LIAN 98 Protocol Router, Simulator and Analyzer © Copyright 2001, 2006, 2011 by MAYOR GmbH. All Rights reserved. |