|
Communication/operation report
|
|
|
(Original Document)
|
|
Communication/operation report
|
|
|
(Original Document)
|
|
Communication report (least significant byte)
|
||
|
Value
|
Meaning
|
|
|
16#00
|
Correct exchange
|
|
|
Operation report (most significant byte)
|
||
|
Value / error code
|
Meaning
|
|
|
Send request code in increments of 16#30
|
Positive result
|
|
|
16#01
|
Request not processed
|
|
|
16#02
|
Incorrect response
|
|
|
16#03
|
Reserved
|
|
|
16#01
|
Exchange stopped on timeout
|
|
|
16#02
|
Exchange stopped on user request (CANCEL)
|
|
|
16#03
|
Incorrect address format
|
|
|
16#04
|
Incorrect target address
|
|
|
16#05
|
Incorrect management parameter format
|
|
|
16#06
|
Incorrect specific parameters
|
|
|
16#07
|
Problem with sending to destination device
|
|
|
16#08
|
Reserved
|
|
|
16#09
|
Size of receive buffer is insufficient
|
|
|
16#0A
|
Size of send buffer is insufficient
|
|
|
16#0B
|
No system resources: the number of simultaneous communication EFs exceeds the maximum that can be managed by the processor.
|
|
|
16#0C
|
Incorrect exchange number
|
|
|
16#0D
|
No telegram received
|
|
|
16#0E
|
Incorrect length
|
|
|
16#0F
|
Telegram service not configured
|
|
|
16#10
|
Network module missing
|
|
|
16#FF
|
Message refused
|
|
|
Operation report (most significant byte)
|
||
|
Value / error code
|
Meaning
|
|
|
16#01
|
Lack of resources communicating with the processor
|
|
|
16#02
|
Lack of line resources
|
|
|
16#03
|
Device missing
|
|
|
16#04
|
Line error
|
|
|
16#05
|
Length error
|
|
|
16#06
|
Communication channel fault
|
|
|
16#07
|
Addressing errors
|
|
|
16#08
|
Application fault
|
|
|
16#0B
|
No system resources: the number of simultaneous communication EFs exceeds the maximum that can be managed by the processor.
|
|
|
16#0D
|
Destination missing
|
|
|
16#0F
|
Intra-station routing problem or channel not configured
|
|
|
16#11
|
Address format not handled
|
|
|
16#12
|
Lack of destination resources
|
|
|
16#FD
|
Invalid parameter
|
|
