Faults - gefran EXP-ETH-GD-ADV Instruction Manual

4.2. Faults

When drive configuration errors or alarms occur the GDNet master device may
signal the presence of certain faults.
Fault codes
The following faults are currently managed
• Type H faults
X Y Description
0 - No communication between GDNet node
and ADV200 device application SW
1 - Application SW identification code mismatch
2 - IPA IDB configuration mismatch
3 - IPA ODB configuration mismatch
These serious errors, which cannot usually be recovered in run-time, block the
device or prevent it from being used.
If at least one type H fault is active, the StatusA and StatusB values are FALSE.
• Type P faults
X Y Description
0 - Drive alarm status signal.
Check drive alarms using the following
4770 "First alarm"
4840 "Stato allarme basso"
4842 "Stato allarme alto"
For details of these errors, the ADV200 must read specific information via the
SDO interfaces.
If at least one type P fault is active, the CardStatus value is TRUE.
• Type A faults
X Y Description
0 0 SDO input management errors
0 1 SDO output management errors
These errors are detected in the master device manager. The slave device (EXP-
ETH-GD-ADV) does not generate alarms.
Errors that occur in I/O exchange via SDO do not result in the device being
disconnected, the error is simply signalled; the manager that generated the error
continues to process the next I/O exchange.
If at least one type P fault is active, the CardStatus value is TRUE.
parameters:
EN- 26