Protocol : IEC 60870-5-102


 

The protocol IEC 60870-5-102 is also available in the LIAN 98 Software,
running under the operating system Microsoft® Windows® ( 32/ 64 bit ).

see : LIAN 98 Protocol Router, Simulator and Analyzer


 

IEC 60870-5-102 : Parameterization

 

 

CDE adapter :

Baud rate :

Modulation mode :

Data byte :

Stop bit :

Parity :

Time out :

Link address fields :

ASDU address fields :

Signature :

Switch setting PCM

50 - 115 200 baud

pulse-code-modulation asynchronous

8 bit (fix)

1 bit (fix)

even (fix)

250 msec (variable)

0 - 2 with or without structure

1 - 2 with or without structure

yes / no

 

Link transmission procedure

Concerning to the IEC 60870-5-102 description balanced transmission is not supported. With LIAN DOS it is however possible to support this transmission procedure.
B :

  Balanced
  

Point to point

If balanced transmission procedure is used, each station may initiate message transfers. The balanced mode is restricted to "point-to-point or multiple point-to-point".
Balanced transmission can be used in full duplex mode.

Balanced transmission can be used in full duplex transmission

U :
 
Unbalanced

Party line

Unbalanced transmission is used in SCADA systems in which a master station controls the data traffic by polling outstations sequentially.

The master station (master) 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.

 

Telegram structure

IEC TCP 102 protocol standard admits exclusive 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 are used. 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.

Frame with variable length :
Frame is used for data transmission of user data between controlling and controlled station.

 

Frame with fixed length :

Frame with fixed length is normally used for link layer services. In special cases can frame with fixed length be used as an acknowledge instead of single character.

Single character:

Single characters are normally used in order to confirm service data of the link layer and user data. 

E5 H = ACK: positive acknowledge.


Control field :

RES Reserved
PRM

 

 

Primary  message

0 = message from a  secondary station (substation) 

1 = message from a primary station (master station) 

FCB

 

Frame count bit  - primary station

changing value for  consecutive  SEND / CONFIRM or REQUEST / RESPOND message per station.

FCV

 

 

Frame count bit valid - primary station

0 = changing function of FCB is not valid

1 = changing function of FCB is  valid

ACD

 

 

Access demand - secondary station

0 = no access demand  on transmission of data class 1

1 = access demand  on transmission of data class 1

DFC

 

 

Data flow control - secondary station

0 = more messages are accepted

1 = further messages can cause a data overflow

Function code:
 

Funktion codes of the control-field in a message sent from the primary station ( 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/ NO REPLY 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 codes of control-field in a message sent from the secondary station ( PRM = 0 ) 

Function Frame type Service function
  0 CONFIRM ACK: Positive acknowledgement
  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

Link adress fields :

Link transmission procedures are using a control field and the optional address field.

The link address is a number for a communication link which is used for the communication lines out from a controlling station. It is only used as an address in the communication network itself, an shall not be a part of total address of a data point.

According to the standard this parameter can consist of 0,1 or 2 octets. 0 is valid only for balanced mode.

Type Identification :

The value <0> is not used. The range of numbers 1 to 127 is used for standard definitions from IEC 60870-5-102 standard.

The range of numbers 128 to 255 are privat and not defined in the standard, but it is recommended that the data unit identifier fields of private ASDUs have the same format as standard ASDUs.

The following tables show the definition of TYPE IDENTIFICATION numbers for process and system information in monitor and control direction.

Process information in monitor direction :

1 Single-point information with time tag M_SP_TA_2
2 Accounting integrated totals, 4 octets each M_IT_TA_2
3 Accounting integrated totals, 3 octets each M_IT_TB_2
4 Accounting integrated totals, 2 octets each M_IT_TC_2
5 Periodical reset accounting integrated totals, 4 octets each M_IT_TD_2
6 Periodical reset accounting integrated totals, 3 octets each M_IT_TE_2
7 Periodical reset accounting integrated totals, 2 octets each M_IT_TF_2
8 Operational integrated totals, 4 octets each M_IT_TG_2
9 Operational integrated totals, 3 octets each M_IT_TH_2
10 Operational integrated totals, 2 octets each M_IT_TI_2
11 Periodical reset operational integrated totals, 4 octets each M_IT_TK_2
12 Periodical reset operational integrated totals, 3 octets each M_IT_TL_2
13 Periodical reset operational integrated totals, 2 octets each M_IT_TM_2

System information in monitor direction :

70 End of initialization M_EI_NA_2
71 Manufacturer and product specification of integrated total DTE P_MP_NA_2
72 Current system time of integrated total DTE M_TI_TA_2

System information in control direction :

100 Read manufacturer and product specification C_RD_NA_2
101 Read record of single-point information with time tag C_SP_NA_2
102 Read record of single-point information with time tag of a selected time range C_SP_NB_
103 Read current system time of integrated total DTE C_TI_NA_2
104 Read accounting integrated totals of the oldest integration period C_CI_NA_2
105 Read accounting integrated totals of the oldest integration period and of a selected range of addresses C_CI_NB_2
106 Read accounting integrated totals of a specific past integration period C_CI_NC_2
107 Read accounting integrated totals of a specific past integration period and of a selected range of addresses C_CI_ND_2
108 Read periodical reset accounting integrated totals of the oldest integration period C_CI_NE_2
109 Read periodical reset accounting integrated totals of the oldest integration period and of a selected range of addresses C_CI_NF_2
110 Read periodical reset accounting integrated totals of a specific past integration period C_CI_NG_2
111 Read periodical reset accounting integrated totals of a specific past integration period and of a selected range of addresses C_CI_NH_2
112 Read operational integrated totals of the oldest integration period C_CI_NJ_2
113 Read operational integrated totals of the oldest integration period and of a selected range of addresses C_CI_NK_2
114 Read operational integrated totals of a specific past integration period C_CI_NL_2
115 Read operational integrated totals of a specific past integration period and of a selected range of addresses C_CI_NM_2
116 Read periodical reset operational integrated totals of the oldest integration period C_CI_NN_2
117 Read periodical reset operational integrated totals of the oldest integration period and of a selected range of addresses C_CI_NO_2
118 Read periodical reset operational integrated totals of a specific past  integration period C_CI_NP_2
119 Read periodical reset operational integrated totals of a specific past integration period and of a selected range of addresses C_CI_NQ_2
120 Read accounting integrated totals of a specific past integration period of a selected time range and of a selected range of addresses C_CI_NR_2
121 Read periodical reset accounting integrated totals of a specific past integration period of a selected time range and of a selected range of addresses C_CI_NS_2
122 Read operational integrated totals of a specific past integration period of a selected time range and of a selected range of addresses C_CI_NT_2
123 Read periodical reset operational integrated totals of a specific past integration period of a selected time range and of a selected range of addresses C_CI_NU_2

 

The program SIMO is able to process user-defined messages from 1-127, provided they do not contravene against the telegram structure of IEC 60870-5-102. 

Variable structure qualifier :

The SQ bit specifies the method of addressing of the following information objects or elements.

SQ = 0

Each single element or a combination of elements is addressed by the information object address. The ASDU may consist of one or more than one equal information objects. The number of objects is binary coded and defines the number of the information objects.

SQ = 1

A sequence of equal information elements (e.g. measured values of identical format) is addressed by the object address. The information object address specifies the associated address of the first information element of the sequence. The following information elements are identified by numbers incrementing continuously by + 1 from this offset. The number of objects is binary coded and defines the number of the information elements. In case of a sequence of information elements only one information object per ASDU is allocated.

Cause of transmission :

The cause of transmission directs the ASDU to a specific application task (program) for processing.

ASDUs in control direction are confirmed application services and may be mirrored in monitor direction with different cause of transmission.

P/N

The P/N-bit indicates the positive or negative confirmation of activation requested by the primary application function. In the case of irrelevance the P/N-bit is zero.

T

In addition to the cause the test-bit defines ASDUs which were generated during test conditions. It is used e.g. to test transmission and equipment without controlling the process.

Common address of ASDU :

Octet 4 and optionaly 5 of the data unit identifier of the ASDU define the address of the integrated total Data Terminal Equipment. The common address is associated with all objects in an ASDU. The length of the address of the integrated total DTE (1 or 2 octets) is a parameter which is fixed per system.

Record address :

The record address is used either as a "record address of a integration period" or a "record address of a single-point information".

Information object address :

The information object address is used as the address of an integrated total or the address of a single-point information.

In all cases the maximum number of different object addresses is limited with 255. If the information object address is not relevant (not used) in some ASDUs, it is set to zero.

Signature : ( optional )

The signature, if it is present, is only defined for ID 2 up to 7, accounting integrated totals. The signature is the arithmetic sum modulo 256 over all octets of an accounting integrated total and its associated identification field.

 


Simulation mode

With the implemented simulation mode the program SIMO offers besides the recording of telegrams the possibility of using the PC as a counter-station.

 

Please note that the simulation was completely revised as of version 3.56.5. Corresponding to the used LIAN-DOS version please read the equivalent section.  

 

Simulation with LIAN-DOS up to version 3.56.4

The simulation can be started via the command 'RTI [time window] [repetitions]. There is no difference between primary- and secondary station or balanced- and unbalanced transmission. The program orientates to the function code and the PRM bit in the control field of the link layer.

The parameter [time window] determines the  time  in 1/10  seconds  that  the  program SIMO as primary station  at most has to wait for an acknowledge before the transmission is repeated. Via the parameter  [repetitions] it is defined  how many times the above procedure is to be repeated. The call  'RTI 10 3' ,for example, defines a monitoring time of  one second and up to 3 repetitions. 

If   'RTI' without parameter is entered, the time monitoring is  switched off  and there are no repetitions. As long as the program SIMO  is waiting for an acknowledge no further  telegrams are  included in the send list. By entering  'RTI' again during running simulation, the simulation is switched off.

The program SIMO as secondary station transmits dependent  on the function code of the primary station automatically acknowledges according to the message buffers listed in the table.  The corresponding telegrams must be of course edited in the declared TDB buffers.

Allocation of TDB ( Transmit data buffer )

number commentary telegram type data (hexadecimal)
492

493

494

495

496

497

498

499

CONFIRM fnct 00       492

CONFIRM fnct 01       493

CONFIRM fnct 02       494

CONFIRM fnct 03       495

action       fnct 08       496

RESPOND fnct 09      497

RESPOND fnct 10      498

RESPOND fnct 11      499

10H fixed length

10H fixed length

10H fixed length

10H fixed length

10H fixed length

10H fixed length

10H fixed length

10H fixed length

10  00  00  00  00  16

10  00  00  00  00  16

10  00  00  00  00  16

10  00  00  00  00  16

10  0B  00  00  00  16

10  0B  00  00  00  16

10  09  00  00  00  16

10  09  00  00  00  16

Course of simulation

Program  SIMO as secondary station

Receipt of telegrams from the primary station
function transmitted from the primary station SIMO transmits TDB
0 SEND-CONFIRM expected

standardizing of the communication unit  of the  secondary station.

buffer 492
1 SEND-CONFIRM expected

standardizing of the user procedure

buffer 493
2 SEND-CONFIRM expected

reserved for  symmetrical transmission procedures 

buffer 494
3 SEND-CONFIRM expected

user data

buffer 495
4 SEND-CONFIRM expected

user data

 
5, 6, 7 reserved for particular use  
8 REQUEST after access demand

the access demand is fixed in the respond

buffer 496
9 REQUEST-RESPOND expected

query of state of communication unit

buffer 497
10 REQUEST-RESPOND expected

query of user data class 1

buffer 498
11 REQUEST-RESPOND expected

query of user data class 2

buffer 499
12 - 15 reserved for particular use  

Program  SIMO as primary station

 Receipt of telegrams from the secondary station
function transmitted from the secondary station actions in SIMO 
0 CONFIRM

positive  acknowledge  (ACK)

switch off timer 
1 CONFIRM

negative  acknowledge  (ACK)

switch off timer 
2 - 7 reserved for particular use  
8 RESPOND

user data

switch off timer 
9 RESPOND

NACK, called up data not available

switch off timer 
10 RESPOND

NACK, message from the link layer not arrived

switch off timer 
11 RESPOND

state of communication unit  or access demand 

switch off timer 
12 - 15 reserved for particular use  

 

Transmission of telegrams to the secondary station
function telegram type / service function SIMO transmits 
0 SEND-CONFIRM expected

standardizing of the communication unit  of the  secondary station

FCB set back

FCB, FCV = 0

ACK function 0

start timer

1 SEND-CONFIRM expected

standardizing of the user procedure

FCB, FCV = 0

ACK function 0

start timer

2 SEND-CONFIRM expected

reserved for  symmetrical transmission procedures 

FCB invert

FCV = 1

ACK function 0

start timer

3 SEND-CONFIRM expected

User data

FCB invert

FCV = 1

ACK function 0

start timer

4 SEND-no response expected

User data

FCB, FCV = 0
5, 6, 7 reserved for particular use  
8 REQUEST after access demand

access demand fixed in response

FCB, FCV = 0
9 REQUEST-RESPOND expected

query of state of communication unit

FCB, FCV = 0

ACK function 11

start timer

10 REQUEST-RESPOND expected

query of user data class 1

FCB invert

FCV = 1

ACK function 8

start timer

11 REQUEST-RESPOND expected

query of user data class 2

FCB invert

FCV = 1

ACK function 8

start timer

12 - 15 reserved for particular use  

 


Extended simulation with LIAN-DOS as of version 3.56.5

All parameters needed for the simulation are set in the program LIAN via menu item  <settings | simulation>  ( see section  5.3.5.16 settings - simulation )

RTI (Master)-simulation
Link address

This link address is the target address and will be inserted in each telegram to be sent during master simulation.

Exception for unbalanced mode :
The link address ( 255 for an one octet address or 65 535 for a two octet address) of a broadcast command is entered in the TDB buffer telegram. 

ASDU address

This ASDU address is the target address and will be inserted in each telegram to be sent during master simulation.

Exception for unbalanced mode :
The ASDU address ( 255 for an one octet address or 65 535 for a two octet address) of a broadcast command is entered in the TDB buffer telegram. 

Response timeout

The IEC 870-5-101 standard specifies a fixed link time-out interval to be used for repeated frame 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 1/10 seconds  that the program SIMO as primary station  at most has to wait for an acknowledge before the transmission is repeated.

Number of frame retries Via this parameter it is defined  how many times the transmission is to be repeated when the acknowledge is missing. 
Enable Station initialization

yes / no

The controlling station synchronizes its link with the controlled station by transmitting "Request status of link" and "Reset of remote link". The controlled station responds with "Status of link" and "ACK" respectively, and when the "ACK" is received in the controlling station the link connection is established.

The telegram "Request status of link" ( PRM=1, function 9 ) must be stored in the TDB buffer 470 and the telegram "standardizing of the communication unit" ( PRM = 1, function 9 ) must be stored in the TDB buffer 471.

Scan delay

( only unbalanced )

 

This parameter determines the time in 1/10 seconds  that the program SIMO delays the next request ( data class 1 or 2 ).

The telegram "Request user data class 1" ( PRM = 1, function 10 ) must be stored in the TDB buffer 473 and the telegram "Request user data class 2" ( PRM = 1, function 11 ) must be stored in the TDB buffer 474.

 

RTU (Slave)-simulation
Link address

This link address is the source address and will be inserted in each telegram sent during RTU simulation.

ASDU address

This ASDU address is the source address and will be inserted in each telegram sent during RTU simulation.

Response timeout

( only balanced )

The IEC 870-5-101 standard specifies a fixed link time-out interval to be used for repeated frame 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 1/10 seconds  that the program SIMO as primary station  at most has to wait for an acknowledge before the last transmission is repeated.

Number of frame retries
( only balanced )

Via this parameter it is defined  how many times the transmission is to be repeated when the acknowledge is missing ( only balanced ). 

Enable Station initialization

( only balanced )

yes / no

The controlling station synchronizes its link with the controlled station by transmitting "Request status of link" and "Reset of remote link". The controlled station responds with "Status of link" and "ACK" respectively, and when the "ACK" is received in the controlling station the link connection is established.

The telegram "Request status of link" ( PRM=1, function 9 ) must be stored in the TDB buffer 470 and the telegram "standardizing of the communication unit" ( PRM = 1, function 9 ) must be stored in the TDB buffer 471.

End of initialization yes / no

The telegram M_EI_NA_1 ( ID 70, COT 4 ) must be stored  in the TDB buffer 479

Generate ACTCON respond yes / no

Is this parameter set to 'yes' automatically ACTCON ( COT 7 ) or. DEACTCON Respond ( COT 9 ) is transmitted during RTU simulation after the receipt of an Activate Command ( COT 6 ) or Deactivate Command ( COT 8 )

Generate ACTTERM respond yes / no

Is this parameter set to 'yes' automatically an ACTTERM Respond ( COT 10 ) is transmitted with time delay during the RTU simulation after the receipt of an Activate Command ( COT 6 ) . 

ACTTERM delay time

This parameter determines the time in 1/10 seconds  that the transmission of ACTERM Respond ( COT 10 ) is delayed.

 

Allocation of TDB Buffers (Transmit data buffer) for the primary station

TDBnum Commentary Frame Data

470

471
  

...

473

474

...

479
   

Request status of link

Standardizing of the communication unit

 

Request user data class 1

Request user data class 2

   

M_EI_NA_1
( End of initialization ) 

10H

10H
   

  

10H

10H

  

68H
  

RES 0 PRM 1 FCB 0 FCV 0 FKT 09

RES 0 PRM 1 FCB 0 FCV 0 FKT 00
  

  

RES 0 PRM 1 FCB 0 FCV 1 FKT 10

RES 0 PRM 1 FCB 0 FCV 1 FKT 11

   

RES 0 PRM 0 ACD 0 DFC 0 FKT 03 // PzP
RES 0 PRM 0 ACD 0 DFC 0 FKT 08 // Gmv

 

Allocation of TDB Buffers (Transmit data buffer) for acknowledges of the secondary station

TDBnum Commentary Frame Data

480

481

482

483

...

485

486

487

488

489

490

491

492

493

494

495

CONFIRM on Function 00

Service not available

Service not available

CONFIRM on Function 03

....

Service not available

Service not available

Service not available

Service not available

RESPOND on Function 09

RESPOND on Function 10

RESPOND on Function 11

Service not available

Service not available

Service not available

Service not available

10H

10H

10H

E5H

...

10H

10H

10H

10H

10H

10H

10H

10H

10H

10H

10H

RES 0 PRM 0 ACD 0 DFC 0 FKT 00

RES 0 PRM 0 ACD 0 DFC 0 FKT 15

RES 0 PRM 0 ACD 0 DFC 0 FKT 15

E5H CONFIRM ACK

...

RES 0 PRM 0 ACD 0 DFC 0 FKT 15

RES 0 PRM 0 ACD 0 DFC 0 FKT 15

RES 0 PRM 0 ACD 0 DFC 0 FKT 15

RES 0 PRM 0 ACD 0 DFC 0 FKT 15

RES 0 PRM 0 ACD 0 DFC 0 FKT 11

RES 0 PRM 0 ACD 0 DFC 0 FKT 09

RES 0 PRM 0 ACD 0 DFC 0 FKT 09

RES 0 PRM 0 ACD 0 DFC 0 FKT 15

RES 0 PRM 0 ACD 0 DFC 0 FKT 15

RES 0 PRM 0 ACD 0 DFC 0 FKT 15

RES 0 PRM 0 ACD 0 DFC 0 FKT 15

 


Simulation procedures

 

Simulation of the communication services :

LIAN DOS 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 DOS after transmitting a primary message  at most has to wait for an acknowledge before the transmission is repeated. Via the parameter [number of frame retries] it is defined how many times the message is to be repeated. As long as the program is waiting for an acknowledge no further telegrams are included in the send list.

LIAN DOS transmits dependent on the function code of a primary message automatically acknowledges according to the defined TDB buffer numbers above. The corresponding frames must be of course edited in the declared TDB buffers.

The program also alternates the FCB bit for each new SEND/ CONFIRM or REQUEST/ RESPOND transmission service directed to the same secondary station. Thus the primary station keeps a copy of the frame count bit per secondary station. In case of reset commands the FCB bit is always zero, and upon receipt of these commands the secondary station will always be set to expect the next frame primary to secondary with FCV = valid ( FCV = 1 ) to have the opposite setting of FCB.

If master simulation and balanced transmission mode are selected the DIR bit is set to 1 in the control field of the link layer for all sent telegrams.

.

Station initialization

The station initialization will be done by LIAN DOS automatically when the master (RTI)- or the slave (RTU) simulation is started.

The primary station synchronizes its link with the secondary station with the transmission "Request status of link" and "Standardizing of the communication unit". The secondary station responds with "Status of link" or "ACK". When the primary station receives "ACK" the link is established.

 

Simulation of the application functions :

Data acquisition by polling
( unbalanced )

Data acquisition is used with unbalanced data transmission procedures in order to update controlling station with actual states of process variables in controlled stations. The controlling station perform polling by interrogating (Function code 10, 11) controlled station sequentially. Controlled stations may transmit only when they are polled.

Cyclic polling is done automatically by LIAN DOS if the Master (RTI)- Simulation is started and party line ( unbalanced ) is set via the configuration.

Transmission of integrated totals

Integrated totals are values that are integrated over a specified period of time.

Integrated totals are transmitted with COT = spontaneous 

 


Plain text display format

 

The output for each channel can be manipulated over the menu item Format in the programs SIMO, TRAP and TDEP. To optimise the output one can distinguish between three plain text settings for protocols with long telegrams ( e.g. IEC protocols )

Plain text F 1

Plain text F 2

Plain text F 3

the complete telegram ( link layer + identification + information ) is displayed

output of  link layer and data unit identifier ( no information )

output of the information objects only

 


Transmission errors

 

Error checks during receive by LIAN DOS :
  • per character the start bit, the stop bit and the even 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 lengths.
*F:BCCode The telegram check sum in the BCC-Byte is incorrect
*F:Block length The stop byte ( 16H ) is missing or set wrongly..
*F:TelFormat The repetition of the length or the start sign in the telegram header is  faulty.
*F:TimeOut Within a telegram, there may be no pause between characters. The sensitivity  can be parameterized in the program LIAN.
*F:Signature Faulty signature
*F:SYNC The receive routine initially searches for 68H, 10H or E5H. Every other character is given an asterisk '*' in SIMO and a synchronization error is noted against it in the protocol.
*F:Overflow Error message by  UART
*F:Parity Error message by  UART
*F:Start/Stop Error message by  UART
*F:VSQ The information stored in the field 'variable structure qualifier' is absurd ,probably caused by wrong field length with the  parameterization.

 

Error checks during simulation by LIAN DOS  ( as of version 3.56.5 ) 
*F: DIR-Bit ! Balanced : Direction bit is wrong.
*F: PRM-Bit ! Primary message bit is wrong.
*F: FCB-Bit ! Frame count bit is wrong.
*F: FCV-Bit ! Frame count bit valid is not correct set.
*F: un-reset ! No station initialization is done yet, but in the message the FCV bit is already set.
*F: unexpected ! The respond was not expected.

 


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.