Alarm information:
Cause |
Communication diagnostic on the second EtherCAT line |
<code> |
Error codes: •0x0001 = link error •0x0002 = I/O blocked after link error (I/O reset required) •0x0004 = link error (redundancy adapter) •0x0008 = missing frame (redundancy mode) •0x0010 = send resources exhausted (I/O reset required) •0x0020 = watchdog enabled •0x0040 = Ethernet driver (miniport) not found •0x0080 = I/O reset enabled •0x0100 = At least one device in 'INIT' state (but only after ECAT line started correctly) •0x0200 = At least one device in 'PRE-OP' state (but only after ECAT line has started correctly) •0x0400 = At least one device in 'SAFE-OP' state (but only after ECAT line has started correctly) •0x0800 = At least one device indicates an error state •0x1000 = DC not synchronized |
Output condition |
EtherCAT network management anomalies and bit 3 and bit 0 set in the variable fb_flag |
Effect |
Communication not active |
What to do |
Check network |
Alarm mask |
am[50].4 |
Alarm par prominent |
Yes |
Alarm type |
|
Notes |
This alarm is generated if enabled via the variable fb_flag. By default the equivalent alarm 88 is generated, which, being major, drops the power set. If a command changes the EtherCAT network state from OPERATIONAL(ECAT_SET_STATE), the alarm is no longer generated or can be delayed(ECAT_SLAVE_DISCON_TIME). Alarm 18 is generated if an axis is associated with the node |
