Corrected from:EtherCat communication module E84AYCET version 02.00.xx.xx.
Response of the new version:
With the version of the EtherCat communication module E84AYCET mentioned above, the described behavior no longer occurs.
Which products are affected?
Inverter Drives 8400 StateLine, HighLine, and TopLine with a firmware version 12.0x.xx.xx
with an EtherCat E84AYCET communication module in version 01.05.xx.xx.
What happens?
Even without a successful synchronisation, the slave changes to 'Operational' although, according to Lenze definition, it should remain in the 'SafeOp' state.
In the case of position followers with absolute set positions, a clicking noise may be heard if the setpoints are not transferred in an equidistant manner.
When does the problem occur?
If an EtherCat E84AYCET communication module in version 01.05.xx.xx is used and an Inverter Drive 8400 with the firmware 12.0x.xx.xx for which the sync signal source selection is 'MCI' C1120=4, and if synchronisation via the bus is set, there is no synchronisation to the EtherCat sync signal.
Diagnostics options?
The C13861 bus status shows 'Operational'. The C13884 parameter (CU sync locked) remains zero; 1 would be correct. The sync instant of reception C370/2 remains zero. If cyclic synchronisation was correct, a value>0 with a low variation should be written here.
Short-term measures/recommendations?
In the respective previous firmware versions, the correct function is provided.
Evaluation:
If the internal synchronisation of EtherCat communication has not been carried out successfully, according to Lenze specification, the bus status should remain at 'SafeOp' so that an unsynchronised bus operation is avoided. For axes with non-synchronised speed setpoints, the expected position time reference is no longer given. The positions of different axes drift away from each other.
For axes with absolute set positions, there is no drift. The missing synchronicity is not necessarily detected during commissioning.
