Corrected from:
EtherCAT E94AYCET FV 3.00 communication module
Behaviour of the new version?
The error register (byte 3) indicates the content of the CoE index I-1001. With the current firmware, the manufacturer-specific 32-bit Lenze error code in the emergency message also is represented correctly according to the EtherCAT specification.
What happens?
In the previous versions, the value 0x00 was indicated in the error register (byte 3) of the emergency message.
In the manufacturer-specific 32-bit error code, the individual bytes were interchanged.
byte 1 => byte 4
byte 2 => byte 3
byte 3 => byte 2
byte 4 => byte 1
Example of resolver wire breakage [0x247b0018]:
previous incorrect representation:
CoE emergency (HEX: 1000, 00, '24 7b 00 18 00')
new correct representation
CoE emergency (HEX: 1000, 01, '00 18 00 7b 24')
When does the problem occur?
The behaviour occurs if the EtherCAT communication module sends an emergency message to the EtherCAT master.
Which products are affected?
EtherCAT E94AYCET FV 2.0 communication module
EtherCAT E94AYCET FV 1.01 communication module
Diagnostics options?
This behaviour is present if the error register (byte 3) of the emergency message contains the value 0x00 and the 4 bytes of the 32-bit Lenze error code are interchanged.
Short-term measures/recommendations?
None
