Alarm information:
Cause |
Communication error on the fourth EtherCAT line |
<code> |
Error codes: •0x0001 = Link error •0x0002 = I/O locked after link error (I/O reset required) •0x0004 = Link error (redundancy adapter) •0x0008 = Missing one frame (redundancy mode) •0x0010 = Out of send resources (I/O reset required) •0x0020 = Watchdog triggered •0x0040 = Ethernet driver (miniport) not found •0x0080 = I/O reset active •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 started correctly) •0x0400 = At least one device in 'SAFE-OP' state (but only after ECAT line started correctly) •0x0800 = At least one device indicates an error state •0x1000 = DC not in sync •0x4000 = Number of consecutive lost EtherCAT frames exceeded MAX_LOST_FRAME_ECAT •0x8000 = Network configuration error |
Output condition |
EtherCAT network management anomalies, bit 3 imposed of variable fb_flag or number of consecutive lost frames exceeds the threshold set in parameter max_lost_frame_ecat |
Effect |
Communication not active |
What to do |
Check network |
Alarm mask |
am[34].4 |
Alarm par prominent |
Yes |
Alarm type |
|
Notes |
If you want this alarm to become warning 9218, thus preventing the power set from dropping, set bit 0 of variable fb_flag. 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 |
