Error handling and diagnosis
BC5250
77
Version: 2.0.0
7
Error handling and diagnosis
7.1
Diagnostics
DeviceNet state
In many cases it is important to know whether the communication with the higher-level master is still OK. To
this end, link the
NodeState
variable with your PLC program. A TwinCAT configuration is required for this
purpose.
Fig. 72: DeviceNet diagnostics byte in the System Manager
Error number
Description
Remedy
0
no error
none
1
Node is deactivated by the scanner, node is no longer
in the masters scan-list.
For Slave Devices it means that there is no Data-
Exchange between the Master and the Slave. The
Master has released the DeviceNet Slave
Check the configuration
2
No data exchange between node and DeviceNet
Master, node access timeout
Check the connection
18
Node is configured, ready for data exchange
none
42
Electronic Key Error: Vendor ID
Check identity of DeviceNet
slave
43
Electronic Key Error: Device Type
Check identity of DeviceNet
slave
44
Electronic Key Error: Product Code
Check identity of DeviceNet
slave
45
Electronic Key Error: Revision
Check identity of DeviceNet
slave
46
Error writing start-up attributes
Check identity of DeviceNet
slave
47
Wrongproduced IO-Data length
Check identity of DeviceNet
slave
48
Wrong consumed IO-Data length
Check identity of DeviceNet
slave
49
Idle Mode (for Slave Devices): no valid IO-Data is
exchanged via DeviceNet
Check whether the master is in
idle mode