Corrected from:EtherCAT E94AYCET communication module FV 4.02
Response of the new version? The EtherCAT module checks at start-up which TA is active in the 94xx standard device and saves the corresponding product code and the PDO mapping in the EEPROM.
What happens?
If the EtherCAT master carries out a bus scan without matching ESI files, all information of the device is loaded directly from the SII EEPROM of the EtherCAT module. So far, the 'Actuator speed' TA with its PDO data has been permanently stored here. This could have produced the consequence that the product code of an 'Actuator speed' TA in the EtherCAT master was configured although a completely different TA was loaded in the 94xx, resulting in a start-up error of the EtherCAT master, since the product code of the master does not comply with that of the slave.
When does the problem occur?
The problem only occurs if no matching ESI data for the slave have been imported to the EtherCAT master. Without ESI files, all EtherCAT properties are loaded directly from the SII EEPROM of the slave.
Which products are affected?
EtherCAT E94AYCET communication module FV 1, 2, and 3
Diagnostics options?
This malfunction occurs if the EtherCAT master outputs a message saying that the product code of the master does not comply with that of the slave.
Short-term measures/recommendations?
If possible, import the Lenze ESI file to the EtherCAT master, or select the product code so that it matches the available TA of the 94xx.
Evaluation:
None
