|
Protocol : IEC 60870-5-104 |
Telegram structure |
|
IEC 60870-5-104 the network access for IEC 60870-5-101 using standard
transportation profiles. |
|
Information about the structure of the telegram and ethernet frames see |
|
The PC must be connected to the network hub or switch before LIAN 98 will be started, otherwise parametrization of the network in LIAN can not be done. |
![]() |
Local machine |
| Network adapter |
If there are several network adapters in the PC the corresponding adapter to be tested has to be selected here. |
| Network protocol |
Here the suitable protocol ( e.g. TCP/IP ) for the test must be selected. |
| Host Name |
The name of the PC declared during the network installation is displayed here. It can be set via the network settings in the Windows system control. ( No input is possible, it is only a display field ! ) |
| IP address |
The IP-address allocated to the network adapter is displayed here. It can be set via the
network settings in the Windows system control. ( No input is possible, it is only a display field ! ) |
| Port number |
When LIAN 98 is used as client ( RTI simulation ) the port number = 0 must be entered.
During the establishment of the client connection a free port address will be allocated to LIAN 98 automatically. |
Remote machine |
| Port number |
When LIAN 98 is used as client ( master simulation ) the port number of the station to be tested
must be entered. Normally it is the port number =2404. |
Capture |
| Time out |
Recommendation : 200 msec |
Settings in the channel window |
![]() |
| ASDU address fields |
2 bytes ( fixed ), structured or unstructured can be selected. |
| . Output format |
dec / hex |
| . Bit structure |
The 16 bit ASDU address can be divided in maximum 4 bit-fields. In the default division the address is byte by byte structured ( 8 + 8 ). But also any other values can be set ( e. g. 2 + 6 + 8 ). The entry begins always from the higher bit and the sum of all bits must be of course 16. |
| Object address fields |
3 bytes ( fixed ), structured or unstructured can be selected. |
| . Output format |
dec / hex |
| . Bit structure |
The 24 bit object address can be divided in maximum 6 bit-fields. In the default division the address is byte by byte structured ( 8 + 8 + 8 ). But also any other values can be set ( e. g. 2 + 6 + 4 + 4 + 8 ). The entry begins always from the higher bit and the sum of all bits must be of course 24. |
IEC 60870-5-104 : RTI ( Client/ Master ) Simulation |
|
LIAN 98 is simulating CLIENT ( master ) and can communicate with up to 32 connected servers simultaneously. |
![]() |
| ASDU address ( target = server ) |
It is the ASDU address of the server with which one will test mostly. All telegrams
to be sent are provided with this ASDU address out of the SIM list and sent to the corresponding server. |
| IP address ( target = server ) |
This is the IP address of the default server with which one will test mostly. |
| Originator address ( source = client ) |
All telegrams to be sent will be provided with this originator address during the master simulation. |
| t0 Connection establishment |
[ sec ] Network connection establishment
timeout |
| t1 Response Timeout |
[ sec ] Response timeout |
| t2 A C K R S N in case of no data message |
[ sec ] |
| t3 Used for sending test frames |
[ sec ] |
| unacknowledged I frames (k) maximum ( A C K R S N ) |
Maximum difference ( k ) between the received sequence number ( RSN ) and the last acknowledged RSN. The transmitter stops the transmission at k unacknowledged I frames. |
| ACK latest after receiving I frames (w) |
This parameter ( w ) indicates the number of received I frames after the RSN will be acknowledged at latest from LIAN 98 with a S frame ( A C K R S N ). |
| Send A C K R S N |
yes / no |
| Enable time synchronization |
yes / no |
| Time SYNC cycle |
1 - 1440 minutes |
| Time SYNC command |
TDB buffer number where the telegram "C_CS_NA_1" ( ID 103, COT 6 ) 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 message "C_IC_NA_1" ( ID 100, COT 6 ) is stored |
|
Insert server addresses number of addresses delete insert |
Multi-Server operation : |
| Send STARTDT |
yes / no |
| Send STOPDT |
yes / no |
| Send TESTFR |
yes / no |
| Send TESTFR confirm |
yes / no |
| Generate execute command |
yes / no |
| ACTCON response timeout ( confirmation activation ) |
This parameter defines the time in seconds that LIAN 98 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 ( deactivation ) |
This parameter defines the time in seconds that LIAN 98 at most has to wait for an ACTTERM Respond ( COT 10 ) before the message "*E: ACTTERM is missing !" is displayed. |
| enable test procedure |
yes / no |
| Test cycle time |
0 - 255 seconds |
| Test command |
TDB buffer number where the telegram "C_TS_TA_1" ( ID 107, COT 6 ) is stored. |
|
LIAN 98 is working as server and can provide 4 connected CLIENTS simultaneously |
![]() |
| ASDU address ( source = server ) |
This ASDU address is the source address and will be inserted in each telegram sent during slave simulation. |
| Originator address ( target = client ) |
All telegrams to be sent during slave simulation will be provided
with this origin address and transmitted to the client with this address. |
| t0 Connection establishment |
[ sec ] |
| t1 Response Timeout |
[ sec ] Response time out |
| t2 A C K in case of no date message |
[ sec ] |
| t3 for sending test frames |
[ sec ] |
| max. difference RSN to send A C K R S N |
Maximum difference ( k ) between the received sequence number ( RSN ) and the last acknowledged RSN. |
| Latest A C K after receiving I-frames |
The parameter ( w ) indicates the number of received I-format frames after which the RSN should be acknowledged at the latest from LIAN 98 with a S-format frame ( A C K R S N ). |
| Send ACKRSN |
yes / no |
| STARTDT / STOPDT controlled |
yes / no |
| End of initialization |
yes / no |
| Send TESTFR |
yes / no |
| Enable time synchronization |
yes / no |
| Set new system date/
time ( PC ) |
yes / no |
| Time correction ( for system time of the PC ) |
0 - 9 999 msec |
| Send STARTDT confirm |
yes / no |
| Send STOPDT confirm |
yes / no |
| Send TESTFR confirm |
yes / no |
| Send ACTCON respond |
yes / no |
| Send 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 ). |
| Send ACTCON respond on test command |
yes / no |
| Allow receipt of monitoring telegrams in control direction |
yes / no |
|
Another highlight of LIAN 98 is the use of the software as protocol router between the
protocols IEC 104 and IEC 101. When using all eight channels the IEC101 substations can be connected via the channels 1...7
and can communicate with an IEC104 client via channel 8 ( TCP/IP network ). |
![]() |
IEC 60870-5-104 : Simulation procedures |
Simulation of the communication services : |
Simulation of the application functions : |
| cyclic data transmission |
Cyclic data transmission is used to provide a continuous updating function of current
values of process variables in balanced and unbalanced transmission procedures. |
| General interrogation |
The general interrogation application function is used to update the controlling station after the station
initialization procedure 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 |
The controlling station sends a "SELECT command" ( ID 45... 50, COT 6 ) to the controlled
station which responds by a "SELECT confirmation" ( COT 7 ) message if it is ready to receive the announced command.
The time from the "SELECT command" to the "SELECT confirmation" is controlled by a configurable timeout
interval ( Response timeout ). |
|
|
IEC 60870-5-104 : Monitoring ( Capture network communication ) |
|
LIAN 98 records all IEC 60870-5-104 data packets of an ethernet,
provided the data are available on the LAN interface of the PC running LIAN 98. This means that the PC has to be connected
directly to the same network hub as the IEC 60870-5-104 client ( master ) without using a switch or router. |
![]() |
| Ethernet type |
0800H ( fixed ) |
| IP version |
4 ( fixed ) |
| Protocol |
6 ( fixed ) |
| IP Address Client |
IP address of an IEC 60870-5-104 client ( Master station ). The network traffic between this client and the server(s) will be recorded. The required stations must be indicated in the server list and the PC must be connected with the client over the same network hub. |
| IP address server ( input field ) |
Use this field to enter the IP addresses
of the servers in the server list. |
| Port number server ( input field ) |
Use this field to enter the port numbers of servers in the server list. |
|
Insert server addresses number of addresses delete insert |
Each particular server to be captured
must be inserted in the server list. LIAN 98 will use this list
to prefilter the network traffic.If no server address is inserted all
IP addresses will be captured. |
![]() |
|
The screen shot above shows the user data of the transmission blocks. Also, if it is required the particulare network headers
( MAC-, IP-, TCP header ) can be displayed. The output format is set via the FMT file - Display format.
The headecimal values can be suppressed separately, of course. |
|
Information to the structure of the
telegram- and ethernet frame. |
|
All process dependent data are available in a data base system in the control center computer.
LIAN 98 offers the possibility to import these process data and use it for the simulation. |
![]() |
| Use data points ( PAR list ) |
yes / no |
|
|
|
| Simulation range |
The parameter list is organized line by line and can accommodate up to 2500 data points,
each line is one data point. |
| Line from |
1 ... number of data points |
| Line till |
> line from ; maximum number of data points |
|
|
|
| Gap time |
0 ... 255 [sec] |
| Number of passes |
1 ... 255 |
| Send change of state on process command |
yes / no |
| Send interrogated information on GI command |
yes / no |
| Number of messages per GI block |
1 ... 128 |
| Gap between GI blocks |
1 ... 36000 [x 100 msec] |
![]() |
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 | Add the next OR-element. | ||||||||||
| remove | Remove the current OR-element. |
![]() |
| 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. |
![]() |
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. |
![]() |
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 display format can be set for each channel separately over <FMT File - Display format>. In order to optimize the output you can choose between different plaintext settings. |
![]() |
| Plaintext format 1 |
Everything is displayed : |
![]() |
| Plaintext format 2 |
Everything 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 plain text 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 frame |
the start sign, the length, the frame checksum and the stop sign |
| *E: NETWORK ! |
Error during writing on the network, system error e.g. socket failure. |
| *E: NET PACKET ! |
The captured length is not equal to the packet length. |
| *E: MAC HEADER ! |
The length of the MAC Header is incorrect or the data packet is not be interpretable. |
| *E: IPv4 HEADER ! |
The length of the IPv4 header is incorrect. |
| *E: TCP HEADER ! |
The length of the TCP header is incorrect. |
| *E: Length ! |
The length of the user data is not equal to the length of the APDU ( Application Protocol Data Unit ). The length of the MAC, IP or TCP header could also be incorrect. |
| *E: Format ! |
The APCI format is wrong. ( Application Protocol Control Information ) |
| *E: SYNC ! |
The receive routine initially searches for 68H. Each other character is noted as synchronization error. |
| *E: Control field ! |
The U format frame, a frame with fixed length cannot be interpreted. |
| *E: VSQ ! |
The information stored in the field "variable structure qualifier" is senseless. |
| *F: INFOBJ length ! |
The length of the information ( object ) range is not plausible. |
Error checks during simulation |
| *E: unexpected ! |
The respond at this time was not expected. |
| *E: Sequence ! |
The received send sequence number or receive sequence number is wrong or a message with variable length ( I format ) is missing. |
| *E: Parameter k ! |
|
| *E: COT ! |
The TypeID set in the ASDU is not provided ( see protocol specific parameter - PAR file ) or is not expected as feedback. |
| *E: TypeID ! |
The TypeID set in the ASDU is not provided. ( see protocol specific parameter - PAR file ) |
| *E: Direction ! |
During RTU simulation LIAN 98 has received in control direction a message from the monitoring direction. This error message can be deactivated in the simulation list ( see settings for RTU simulation in the SIM file ). |
| *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-104 : 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 ) for this TypeID entered. Otherwise an error message is displayed when receiving the telegram ( E:TypeID, E:COT ). Additionally the length of an information object without the length of the object address is defined for each TypeID. |
![]() |
IEC 60870-5-104 : Process data |
|
LIAN 98 offers the possibility to import process data available on the control
center computer and use it for the simulation. This causes for testing a significant reduction in expenditure of time, because
you must not edit the particular telegrams. The telegrams are automatically generated by LIAN 98 on the basis of
the data point list. |
![]() |
|
The process data description is organized line by line and can accommodate up to 2500 data points, whereby each data point is one line. |
| Address of ASDU ( station number ) high, low |
The "common Address of ASDU" is normally the station number
and the same for all objects in an ASDU. According to standard it contains of 2 octets ( high, low ). In LIAN 98
the process data always refer to one station. For the simulation this address must also be entered into the
RTI- or RTU list. |
| Station name |
maximum 15 ASCII characters |
|
|
|
| Information object address ( IOA ) high ... low |
Address of the data point |
| type ASDU name |
Type identification ( TypeID ) |
| value |
Object state ( OFF, ON, ... ) |
| step |
changing state |
| S/ E |
qualifier of command ( QOC ) : select / execute |
| time |
qualifier of command ( QOC ) :
Command pulse duration |
| data point |
maximum 69 ASCII characters |
|
Wuerzburger Ring 39, D 91056 Erlangen |
LIAN 98 Protocol Router, Simulator and Analyzer © Copyright 2001, 2006 by MAYOR GmbH. All Rights reserved. |