4.4.1 Protocol : ABB RP 570/ RP 571


 

Telegram structure

The protocol RP 570/ 571 uses the IEC 60870-5-1, FT 1.2 frame formats. This standard recommends two formats, the fixed and the variable length frame format. Which are used for RP 570/ 571.

 

Information about the structure of the telegram see
<RP 570/ 571 : Telegram structure>

 


RP 570/ 571 : Configuration

 

 

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 )

 

Transmission procedure
U :
unbalanced

For protocol RP570/ 571 only unbalanced transmission is used in which a master station controls the data traffic by polling outstations sequentially. The master station is the primary station that initiates all message transfers while outstations are secondary stations ( slaves ) that may transmit only when they are polled.
The unbalanced mode can be used generally, but must be used in party line configuration.

 


RP 570/ 571 : Simulation

 

RP 570/ 571 : RTI ( Master )-Simulation

 

LIAN 98 as a MASTER can communicate in the polling mode ( unbalanced ) with up to 32 connected substations simultaneously.

 

 

RTU number
( Address of the target station )

All telegrams to be sent are provided with the RTU number out of the SIM list during master simulation. If a number unequal zero is inserted in the telegram ( TDB buffer ), the telegram will be transmitted unchanged with this RTU number already inserted.

Response timeout

1 - 30 000 msec

A fixed time out interval is provided to be used for repeated transmissions. The time out interval and maximum number of retries are configurable and appropriate values will depend on the transmission system.

This parameter determines the time in milliseconds that the program LIAN 98 as master station at most has to wait for an acknowledge before the last transmission is repeated.

Number of frame retries

0 - 255

Via this parameter it is defined how many times the transmission is to be repeated when the reply is missing.

Initialize communication

yes / no

The master synchronizes its link with the substation by transmitting the command "Status Check Instruction" ( SCI ). The secondary station normally responds with an "Executed Response" ( EXR ) or after a substation restart with an "Execute Response, RTU restarted" ( EXRR ). When this response was received by the master station the connection is established.

Status Check Instruction

TDB buffer number where the command "Status Check Instruction/ Communication" ( SCI : function 15, CMD bit = 1 ) is stored.

Enable clock synchronization

yes / no

After the communication is established LIAN 98 will transmit first of all a time synchronization command "Time Sync Instruction" ( TSI ) and will repeat it cyclic depending on the parameter "Clock SYNC cycle time", if this parameter is activated.

Clock SYNC cycle time

1 - 1440 minutes

Dependent on this time LIAN 98 as master station will transmit the time synchronization command continually.

Clock SYNC command

TDB buffer number where the command "Time Sync Instruction" ( TSI : function 12, CMD bit = 1 ) is stored.

Use system date/ time

yes / no

The system time of the PC will be taken over into the time synchronization command ( TSI : function 12, CMD bit = 1 ) before the command will be transmitted, if this parameter is activated. Alternatively the telegram remains unchanged as before edited by the user.

Enable general interrogation

yes / no

After the communication is established LIAN 98 will transmit a general interrogation command "Status Check Instruction" ( SCI ) and will repeat it cyclic depending on the parameter "GI cycle time", if this parameter is activated.

GI cycle time

1 - 1440 minutes

Dependent on this time LIAN 98 as master station will transmit the general interrogation command continually.

GI command

TDB buffer number where the command "Status Check Instruction/ General Interrogation" ( SCI : function 15, CMD bit = 1 ) is stored.

Insert scan addresses
Number of addresses
delete
insert

Unbalanced : ( party line )
All stations to be processed at this line have to be inserted into the scan list. LIAN 98 establishes the connection to this stations and interrogates continuously the user data of this stations.

In order to insert the addresses please proceed as follows :

Activate "Insert scan addresses" ( button "insert" will be displayed ).
Insert in the fields "RTU number" the station to be entered in the scan list.
Take over the station number into the scan list by clicking "insert".
When all stations are inserted, please deactivate "insert scan addresses" ( button "insert" disappears ).

In order to delete a station out of this list select it and click "delete".

Disable automatic station scan

Unbalanced : yes / no

When the communication establishment is finished, LIAN 98 starts automatically the request of the user data ( priority 1/ 2 ). If this requests are not wanted it can be deactivated here.

Request user data priority 1

Unbalanced :
TDB buffer number where the command "Request A" ( function 0, CMD bit = 1 ) is stored.

Request user data priority 2

Unbalanced :
TDB buffer number where the command "Request B" ( function 8, CMD bit = 1 ) is stored.

Scan delay

Unbalanced : 0 - 30 000 msec

This parameter determines the time that the program LIAN 98 delays the next request of data priority 2.

Send execute command

yes / no

An "Execute Command" ( EXC : function 13, CMD bit = 1 ) is automatically sent from LIAN 98 during Master simulation after the receipt of an "Check Back Response" ( CBR : function 10, CMD bit = 0 ); when this parameter is activated.

CBR response timeout

This parameter defines the time in seconds that the program LIAN 98 as master station at most has to wait for an "Check Back Response" ( CBR ) before the message "*E: ACTCON missing !" is displayed.

 

RP 570/ 571 : RTU ( Slave )-Simulation

 

 

RTU number

All telegrams to be sent are provided with the RTU number out of the SIM list during slave simulation. If a number unequal zero is inserted in the telegram ( TDB buffer ), the telegram will be transmitted unchanged with this RTU number already inserted.

Send CCR1 response

yes / no

TDB buffer number where the telegram "Cycle Complete Response, Priority 1" ( CCR1 : Funktion 0, CMD-Bit = 0 ) is stored.

Send CCR2 response

yes / no

TDB buffer number where the telegram "Cycle Complete Response, Priority 2" ( CCR2 : function 1, CMD bit = 0 ) is stored.

Send EXRR response

yes / no

TDB buffer number where the telegram "Execute Response, RTU restarted" ( EXRR : function 2, CMD bit = 0 ) is stored.

Send EXR response

yes / no

TDB buffer number where the telegram "Executed Response" ( EXR : function 3, CMD bit = 0 ) is stored.

Send NXR response

yes / no

TDB buffer number where the telegram "Not Executed Response" ( NXR : function 4, CMD bit = 0 ) is stored.

Send CBR response

yes / no

Double-throw process command, quittance to select command "Check Back Response" ( CBR : function 10, CMD bit = 0 )

Enable clock synchronization

yes / no

 

Set new system date/ time

yes / no

The system time of the PC will be adjusted to the received time values of the time synchronization command "Time Sync Instruction" ( TSI : function 12, CMD bit = 1 ), if this parameter is activated.

Time correction
( for system time of the PC )

0 - 9 999 msec

A correction value can be entered for the setting of the PC system time with a time synchronization command. It will be added onto the received value in the synchronization command.

Use system date/ time

yes / no

The system time of the PC will be inserted in telegrams with time stamp before transmission, if this parameter is activated. Otherwise the telegram remains unchanged as before edited by the user.

 


RP 570/ 571 : Pre-filter/ Pre-trigger

 

 

 

RP 570/ 571 : 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.

 

RP 570/ 571 : Action filters

 

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

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.

 

RP 570/ 571 : 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.

 

RP 570/ 571 : 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.

 


RP 570/ 571 : 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 : Telegram header, telegram number and information elements

 

Plaintext format 2, 3

No header is displayed : Only information elements

 

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.

 


RP 570/ 571 : Error messages

 

Error checks during receipt

 

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 ( both 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 or 10H. 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: unexpected !

The respond at this time was not expected.

*E: Link address !

The received station address is incorrect or the entry in the SIM list is wrong.

*E: Sequence !

The sequence number ( SEQ ) in the command does not correspond to the SEQ expected by LIAN 98. This error message can occur at the beginning after switching on the RTI simulation, when the SEQ of the master and the substation are not still synchronized. Subsequently LIAN 98 takes over the new SEQ of the received command and expects in the next command a SEQ increased by one.

 


RP 570/ 571 : Parameter list

 

The parameter list is not used for the protocol ABB RP570/ RP571.

 

 


MAYR Software

Wuerzburger Ring 39,  D 91056 Erlangen

Manual LIAN 98


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