Protocol : ABB - Indactic 2033


 

The telegram circulation is controlled by the master station, i.e. RTU only replies on inquiry. The analysis of telegrams ( D-words ) in monitoring direction is only possible concerning the command sent before in control direction. Therefore for line recording with LIAN DOS two channels are used and correspond with each other; you have the choice between channels 1 + 2 or 3 + 4. On the first channel recording is done in control direction ( master -> RTU ) and on the second channel in monitor direction ( RTU -> master ). The advantage of this 2 channel recording mode is that RTU messages ( D-words ) can be analyzed with the previous master command.

 

Indactic 33 : Parameterization

 

 

CDE adapter

Switch setting PDM because of synchronous transmission.

Baud rate

50 - 2400 Baud ( variable )

Modulation mode

Synchronous pulse code modulation

Procedure

Pseudohalfduplex ( PHD ) is the Indactic 33 standard transmission mode.

Control direction :
A telegram ( file ) consists of between 1 and 18 words coded with B, C, D and G. The gaps between the control telegrams are contineously filled up with synchronisation words ( 1110 1011 1001 0000 ). The transmission never stops.

Monitoring direction :
A telegram consists of 0 to 17 words coded with C, D, G. A common synchrocharacter "SC" ( 111 0100 ) precedes every telegram sent to the master station with the exception as answer after a call CI1/ CI2 the special synchrocharacter "SC*" is used. The synchrocharacter itself may be preceded by some zeroes. The "SC*" contains the RTU base address in its low order 4 bits. An eight bit extended address is optional appended for extended addressing mode. Additionally measuring data can also be coded with CRC-8.

Tolerance limit

0 - 50 %

PC send ( TxT ) level

-12 volt / +12 volt

Acknowledge watch

yes / no

Direction setting

control / monitoring

Message gap

At least two synchro words are defined by ABB.

Hamming distance

4
The hamming distance = 4 is obtained when 5 hamming bits are transmitted with each data word.

 

Indactic 33 : Telegram structure

 

Word structure :

 

M1 bit will be transmitted first.

Mode bits ( M1, M0 ) 0 : B-word, Block
1 : G-word, Group
2 : D-word, Data
3 : C-word, Control
Linking bit ( L ) 0 : Last word of the message, no words following.
1 : Other words following.
I7, I6, I5, I4, I3, I2, I1, I0 Information bits
H4, H3, H2, H1, H0 Hamming check bits

 

 

Byte structure :

 

B-Word :

The B word specifies the station address of the involved RTU and the kind of data transfer to take place. It will be transmitted by the master station in the control direction only.

 

RTU base address 0... 14 : The station address where the command is directed.
15 : The global address ( broadcast address ) directed to all stations.
Data type 0 : command ( B0 )
1 : setpoint ( B1 )
2 : reserved ( B2 )
3 : cyclic setpoint ( B3 )
4 : change of state indication priority 1 ( B4 )
5 : counter ( B5 )
6 : contact status, indication status ( B6 )
7 : change of state indication priority 2 ( B7 )
8 - 15 : analog/ digital measurand ( B8 ... B15 )

 

G-Word :

The G word is the information address. Each group of 8 bits ( 1 byte ) within the RTU can be addressed by this group address. The group addresses from 0 up to 15 ( file number = 0 ) are used for system internal commands, setpoints or indications.

 

File number

0... 15
A file or block is a unit up to 16 adjacent bytes ( 128 bits ) and is the largest amount of information that may be transmitted in a single telegram.

Byte offset

0... 15
A byte is a group of 8 bits and is assigned an address within a file.

Counter number

0... 63
Maximum of 64 up and down counters per RTU.
 0    1st counter of RTU
 1    2nd counter of RTU
 :
63  last counter of RTU

Measurand number

 0    1st measurand of file
 1    2nd measurand of file
 :
15  16th measurand of file

Extended address

0... 255
Beside the 4 bit base address ( BA ) an additional 8 bit extended address ( EA ) can be used. RTU's with base addressing mode and RTU's with extended addressing mode may by used within the same system. Preferable BA = 0 should be selected for extended addressing mode.
Extended address for RTU
. over 'C34 Gext ...' in control direction
. over 'SC*BA EA'   in monitoring direction

 

D-Word :

The D word describes the information itself.

 

 

 

 

 

Command type

0 : Operate
1... 7 : reserved

Function code

0 : Normal indication, recorded w/o time
1 : reserved
2 : Normal indication, recorded with time
3 : Normal indication, recorded with time, but time or sequence unreliable
4 : command echo, recorded w/o time
5 : reserved
6 : command echo, recorded with time
7 : command echo, recorded with time, but time or sequence unreliable

Contact number
( BIT )

0... 7
Bit number within a byte. A bit is the elementary unit of an information and is addressed by the group address and bit number. A bit may represent the state of a single contact or be part of a larger unit.

Length

0... 16
Length of measurand file. Word is following if G word = 4 after B1.

CON
Continuation indicator

0 : No more indications are waiting.
1 : More indications waiting for transmission.

ON / off

For commands the required action or for indications the reported state.
0 : OFF ( not possible for pulse commands )
1 : ON

 

C-Word :

The C-Words are organisation words and used for acknowledgment, function test, to signal special conditions and so on.

 

  direction I7 ... I4 I3 ... I0 Function
CI1 con 1 1 1 1 0 0 0 0 Request spontaneous indications priority 1.
CI2 con 1 1 1 1 0 0 0 1 Request spontaneous indications priority 2.
C34 con 1 1 1 1 0 0 1 0 Extended address follows.
CBA con 1 1 1 1 0 1 1 1 Block all RTU's.
    1 1 1 1 x x x x 9 reserved codes for information transmission to all RTU's.
    1 1 1 1 0 1 0 x 2 forbidden combinations in conflict with CF8/ CF12.
CS con 1 1 1 1 1 1 1 1 Stop any transmission.
         
CA con RTU addr 0 0 0 0 Request acknowledgment, after command or setpoint to all RTU's.
CN mon RTU addr 0 0 0 1 No change of state indication or no spontaneous data available.
    RTU addr 0 0 1 0 reserved
CW mon RTU addr 0 0 1 1 Block or group not wired.
CF8 mon length - 1 0 1 0 0 CRC8 coded 8 bit measurands following after B8...B15 call.
CF12 mon length - 1 0 1 0 1 CRC8 coded 12 bit measurands following after B8...B15 call.
    RTU addr 0 1 1 0 reserved
CB con RTU addr 0 1 1 1 Block RTU
CT con/ mon RTU addr 1 0 0 0 Function test
    RTU addr 1 0 x x 3 codes reserved
CQN con/ mon RTU addr 1 1 0 0 Negative acknowledgement
    RTU addr 1 1 0 1 reserved
CQ con/ mon RTU addr 1 1 1 0 Positive acknowledegment
CQF con RTU addr 1 1 1 1 Positive acknowledgement and call for more.

 

B0 : System internal commands

All commands ( B0 ) with group number <= 15 are treated as system internal commands.

 

group D-word meaning
0 1

Initiate transfer of 8 or 16 bit increments into RAM.

0 2

Request "soft reset" of RTU. Indications of priority 1 and 2 in the main queue are cleared.

0 3

Request reset/ restart of RTU.

0 5

Request the last 5 indications again.

0 7

Request control indications, change RC1 contact ( ED 1705 ) to its opposite state.

5 0

Switch OFF RC2 on ED1705. ( Switch to standard receiver channel ).

5 1

Switch ON RC2 on ED1705. ( Switch to standby receiver channel ).

 

B1 : System internal setpoints

All setpoints ( B1 ) with group number <= 15 are treated as system internal setpoints.

 

group D-words meaning
0 D0... D6 [ D7 ]

Set date/ time in RTU. D-words contain BCD coded time values of 2 digit each.

1 D0... D1 [ D2 ]

Set correction values for clock.

4 D0... D7

Set file length of measurand blocks B8... B15.

7 D0... D1

Set address for remote console function.

7 D0... D2

Set address and new data for remote console function.

 

System internal indications

All indications with group number <= 15 are treated as system internal indications and will be transmitted as priority 1 indications after command B4.

 

group function contact state D-words meaning
0 2 0 1 D0... D3 [ D4 ]

Power on.
D1... D4 = time values.

0 0 1 1 D0

FIFO data lost.

0 2 3 0 D0... D3 [ D4 ]

Local logging again operable.
D1...D4 = time values.

0 2 3 1 D0... D3 [ D4 ]

Local logging not operable.
D1...D4 = time values.

0 0 4 1 D0

Hardware change detected.

0 0 5 1 D0

Software parameter error detected.

0 0 6 1 D0

Hardware parameter error detected.

0 0 7 1 D0

ROM/ RAM error detected.

1 2 1 1 D0... D3 [ D4 ]

Contact is flickering.
D1...D4 = time values.

1 0 [ 2 ] 2 1 D0,
[ D1... D3, D4 ]

Command output disturbed.
D1...D4 = time values.

2 2 0 0 D0... D4

Most significant part of time variables have changed.
D1...D4 = time values ( hour, day, month, year ).

5 0 0 0 D0

RC2 of ED1705 is OFF ( automatically by RTU ).

5 0 0 1 D0

RC2 of ED1705 is ON ( automatically by RTU ).

5 0 1 0 D0

RC2 of ED1705 is OFF ( by internal command ).

5 0 1 1 D0

RC2 of ED1705 is ON ( by internal command ).

5 0 2 0 D0

RC2 of ED1705 is OFF ( manually with CI ).

5 0 2 1 D0

RC2 of ED1705 is ON ( manually with CI ).

 

System internal status information

All status informations with group number <= 15 are treated as system internal status information and will be transmitted after command B6.

 

group D-words meaning
0 D0... D6 [ D7 ]

Read date/ time from RTU clock. D-words contain BCD coded time values of 2 digit each.
Another 3 D-words will be appended, if the stop watch modul ED1628 is installed.

1 D0

Read actual correction value of RTU clock. D0 = long term drifft correction.

3 D0... D15

Read RTU diagnostic table I.

4 D0... D15

Read RTU diagnostic table II.

7 D0... D2

Read addressed location ( remote console function ).

 

Indactic 33 : Monitoring ( Recording )

 

 

The control direction setting is used for RTI/ master simulation. A master sends control telegrams and receives monitoring telegrams.
The monitoring direction setting is used for RTU/ station simulation. A substation sends monitoring telegrams and receives control telegrams.
Because of the simulation done with one channel, the parameterization refers always to the direction of transmission.

For recording only 2-channels should be used. One channel to record control telegrams and the second channel to record the monitoring direction.

Following settings in the parameterization are required :
. CHANNEL 1 : Monitoring direction to record control telegrams on the COMport 1.
. CHANNEL 2 : Control direction to record telegrams in monitoring direction on COMport 2.
Alternatively channel 3 and 4 can be used instead of channel 1 and 2.

Since version of LIAN DOS v3.57.3 the RTU messages ( D-words ) can be analyzed with the previous master command, therefore the above settings are strictly recommended. If only one channel is used for recording in monitoring direction the information ( indications, measurements, .. ) will be displayed in a generally format.

In order to record the control direction the continuous synchronisation words must be sent on the line from the connected master. With the recognition of the synchronisation words the message "Sync OK !" appears in the system message window. Only then control telegrams can be received.

 

Indactic 33 : Simulation

 

Indactic 33 : RTI (Master) Simulation

The setting "control direction" is necessary for RTI/ master simulation.

 

 

RTI simulation is divided into several steps :

The used transmisson mode is pseudohalfduplex ( PHD ). In this mode, the master never stops its transmission activity. The gaps between the "master -> RTU" telegrams are filled up with synchronisation words, allowing a permanent sychronisation of the RTU receiver. In order to switch on the contineous synchronisation words please enter in the command window of the program SIMO the command "RTI" without any further parameters.
After that enter the command "RTI <rtu base address> [<extended address>]" for continuing simulation.
Base addresses ( < 15 ) are entered automatically into the telegrams and spontaneous message queries. If an extended address is declared, it will be assumed. By entering "RTI" again the simulation mode is switched off.

 

The automatism of message queries works as follows :

 

Start a query manually ( e.g. with a sequence ).

If a RTU has spontaneous messages to transmit, it is reported with " SC* ".
Program SIMO starts the query sequence : B4 - CQF - CQF ... CQ

Therefore you can realize all queries with sequences ( see SIMO : command "LF" and command "SF" ). In case of present spontaneous messages the sequence is stopped, the messages are interrogated and only then the sequence is continued.

 

Program SIMO reacts on message queries as follows :

 

History Reaction Example
MS ->RTU :   CI1   ( manually )
RTU->MS                SC*

MS ->RTU :   CI1             B4
RTU->MS                SC*            D0... Dn

MS ->RTU :   CI1             B4
RTU->MS                SC*            D0... Dn

buffer 480
  

buffer 483
  

buffer 482
  

B4  - request
  

CQF - acknowledge ( continue )
  

CQ  - acknowledge ( end )
  

MS ->RTU :   CI2
RTU->MS                SC*

MS ->RTU :   CI2             B4
RTU->MS                SC*            D0... Dn

MS ->RTU :   CI2             B4
RTU->MS                SC*            D0... Dn

buffer 481
 

buffer 483
 

buffer 482
 

B7  - request
 

CQF - acknowledge ( continue )
 

CQ  - acknowledge ( end )
 

 

Indactic 33 : RTU (Slave) Simulation

The setting "monitoring direction" is necessary for RTU/ slave simulation.

 

 

In order to start the RTU simulation please enter in the command window of the program SIMO the command "RTU <rtu base address> [<extended address>]". The Program SIMO reacts on incoming instructions with the below listed actions. The buffers to be sent back should in advance be adapted to your requirements. It is not necessary to consider station addresses because SIMO enters them automatically when transmitting. By entering "RTU" again the simulation mode is switched off.

 

Command Reaction Example

B0    - command
B1    - Set points on request
B3    - Cyclic set point

CI1   - Inquiry spontaneous messages prio 1
B4    - Inquiry spon. mess. prio 1 of station
CQF - more messages prio 1
CQ   - End of request

B5    - Request for counters
B6    - Request for indications status

CI2   - Inquiry spontaneous messages prio 2
B7    - Inquiry spon. mess. prio 2 of station
CQF - more messages prio 2
CQ   - End of request

B8    - Request measurands single
B9    - Request measurands single
B10  - Request measurands single
B11  - Request measurands single
B12  - Request measurands single
B13  - Request measurands single
B14  - Request measurands single
B15  - Request measurands single

B8    - Request measurands File 
B9    - Request measurands File
B10  - Request measurands File
B11  - Request measurands File
B12  - Request measurands File
B13  - Request measurands File
B14  - Request measurands File
B15  - Request measurands File

CT    - Function test
CA   - Call acknowledgement
CB   - Block RTU
CBA - Block all RTU's 
CS   - stop any transmission

buffer 493
buffer 493
none

buffer 490
buffer 400
buffer 401... 419
none

buffer 495
buffer 496

buffer 491
buffer 430
buffer 431... 449
none

buffer 458
buffer 459
buffer 460
buffer 461
buffer 462
buffer 462
buffer 464
buffer 465

buffer 468
buffer 469
buffer 470
buffer 471
buffer 472
buffer 473
buffer 474
buffer 475

buffer 492
buffer 493
RTU is blocked
RTU is blocked
none

CQ ( positive acknowledgement )
CQ ( positive acknowledgement )
 

SC asterisk ( SC* )
Message with group
Message with group
 

Message without group
T mess. w/o group ( D0.... Dn/ CW )

SC asterisk ( SC* )
Message with group
Message with group
 

Message without group
Message without group
Message without group
Message without group
Message without group
Message without group
Message without group
Message without group

Message without group/ CW
Message without group/ CW
Message without group/ CW
Message without group/ CW
Message without group/ CW
Message without group/ CW
Message without group/ CW
Message without group/ CW

CT  ( Function test )
CQ
RTU is blocked
RTU is blocked
 

 

Indactic 33 : Filter- and trigger conditions

 

 

Telegram type

TypeID : LIAN-DOS assigns internal an unambiguous type identificarion to each telegram type that also can be used for filtering. In the following list you will find the assigned values.

Block type B byte low : 0... 15 ( B0... B15 )
Control type C byte low : 0... 15 ( input I3... I0 )
Extended address ( EA ) With statement of an extended address for RTU
. via 'C34 EA ...'    ( in control direction )
. via 'SC* BA EA'   ( in monitoring direction )
If it is set in a message this is recognized and automatically filtered.
RTU Base address ( BA ) B byte high or C byte high ( in each case RTU Base address )
Group number G byte : 0... 255 ( numeric value of G byte )

A message must full fill all activated filter conditions. If one activated filter criterion doesn't occur in the telegram, this telegram is disabled. A filter condition not activated ( operator = x ) is ineffective.

Trigger conditions are handled analogously.

 

TypeID direction description
1 con B0 : COMMAND ( B1 G  D0 )
33 con B0 internal : Initiate transfer of 8 or 16 bit increments into RAM.
34 con B0 internal : Request "soft reset" of the RTU.
35 con B0 internal : Request "reset/ restart" of the RTU.
36 con B0 internal : Request the last 5 indications again.
37 con B0 internal : Request control indications, change RC1 contact ( ED 1705 ) to its opposite state.
38 con B0 internal : Switch off RC2 contact on ED1705. ( Switch to the standard receiver channel ).
39 con B0 internal : Switch on RC2 contact on ED1705. ( Switch to the standby receiver channel ).
     
3 con B1 : SETPOINT ( B1 G  D0... Dn )
49 con B1 internal : Set date/ time in the RTU. ( B1 G  D0... D6 )
50 con B1 internal : Set date/ time in the RTU. ( B1 G  D0... D7 )
51 con B1 internal : Set correction values for clock. ( B1 G  D0 D1 )
52 con B1 internal : Set correction values for clock. ( B1 G  D0... D2 )
53 con B1 internal : Set file length of measurand blocks for B8... B15.
( B1 G  D0... D7 )
54 con B1 internal : Set address for remote console function. ( B1 G  D0 D1 )
55 con B1 internal : Set address and new data for remote console function.
( B1 G  D0... D2 )
     
5 con B2 : reserved
6 con B3 : Cyclic SETPOINT
7 con B4 : Request changed state of indications priority 1.
8 con B5 : COUNTERS
9 con B6 : Input contact status
10 con B7 : Request changed state of indications priority 2.
11 con B8 : Single MEASURANDS
12 con B8 : MEASURAND blocks/ files
     
13 con CI1 : Call indications priority 1.
14 con CI1 : Call indications priority 2.
15 con C34 : Extended address follows.
16 con CBA : Block all RTUs.
17 con CS : Stop any transmission.
18 con CA : Call acknowledgement after command or setpoint to all RTUs.
19 con CB : Block the RTU.
20 con CT : Function test.
21 con CQN : Negative acknowledgement.
22 con CQ : Positive acknowledgement.
23 con CQF : Positive acknowledgement and call for more.
     
65 mon SC* : Special synchrocharacter following after CI1/ CI2 call.
66 mon CQ : Positive acknowledgement.
67 mon CQN : Negative acknowledgement.
68 mon CT : Function test.
69 mon CW : Block/ group not wired.
70 mon CN : No canged state indications, no spontaneous data.
     
71 mon CF8 : CRC-8 coded 8 bit measurands following after B8... B15 call.
72 mon CF8 : CRC-8 coded 12 bit measurands following after B8... B15 call.
73 mon RTU message with group following after B4/ B7 call.
This message type is only used, if the monitoring direction will be recorded on one channel without recording the control direction.
74 mon RTU message without group following after B5, B6, B8... B15 call.
This message type is only used, if the monitoring direction will be recorded on one channel without recording the control direction.
75 mon after B4 internal : System internal RTU indications with group following after B4 call.
76 mon after B6 internal : System internal status information without group following after B6 call.
77 mon after B4/ B7 : RTU indications with group following after B4/ B7 call.
78 mon after B5 : Counters without group following after B5 call.
79 mon after B6 : Input contact status without group following after B6 call.
80 mon after B8... B15 : Single measurand ( 8 or 12 bit ) without group following after B8... B15 call.
81 mon after B8... B15 : Measurand block/ file ( 8 or 12 bit ) without group following after B8... B15 call.

 

Examples of filter conditions shown on the basis of different telegrams :

 

1. Setpoint telegram sequence :
  . filtration for base address :
                          Data type :
                          Group number :

B1 G D0... Dn
( B1 high )
( B1 low )
( G )

2. CRC-8 coded measurands :
  . filtration after C byte ( C type )

CF12 CRC-8 data ( C type )
CF12

3. function test [with extended address]
  . filtration after extended address
                         rtu base address :
                         C byte ( C type ) :

[C34 extaddr] CT
( extaddr ) only with extended address
( CT high )
( CT )

 

Indactic 33 : Transmission errors

 

*E: Tolerance !

The measured character length is beyond the tolerance set in LIAN.

*E: Spike !

Word contains wrong hamming code.

*E: SYNC !

Synchro word recognition is aborted after permissible start bit and renewed trial.

*E: TimeOut !

TimeOut occured before telegram format could be recognized.

*E: BCCode !

One or both check words of the CRC-8 measurement data record are wrong.

*E: Hammingcode !

Word contains wrong hamming code.

*E: BlockLength !

Message is too short ( fault ) or link bit is not 0 in spite of reaching the maximum message length.

*E: MessFormat !

No valid telegram format is recognized.

*E: End sign !

The linking bit is not valid.

*E: ACK missing !

LIAN has received a wrong respond from the substation during master simulation.

 


MAYR Software

Wuerzburger Ring 39,  D 91056 Erlangen

Manual LIAN DOS


LIAN DOS Protocol Simulator and Analyzer
© Copyright 1991, 1996, 2001, 2006-2010 by Werner Mayr. All Rights reserved.