Hello MST ,
The Safety Configuration is OK, but has nothing to do with the connection establishment problem.
The device assignment to the FSoE-Slots with 6 Byte In/ 6 Byte Out fits to the selected profile. As well the address is fitting to the slot number.
This error has its root cause typically if there are filling bits in the FSoE-Datablock. In this case the PLC-based copy method to establish a FSoE-Connection is not applicable, since the PLC copy masks these bits. They are needed during start-up of the FSoE-connection and generate a CRC-Error.
Then the right method is the ctrlX IO Engineering using the Slave-to-Slave-Mapping in the EtherCAT-Master object. If this does not work there is another mismatch.
There are some actions that come to my mind:
- Please post the Slave-to-Slave configuration.
- Please create a Wireshark record during the establishment of the FSoE connection and post here. This will allow our experts to analyse what goes wrong with your connection.
- Please check the Device Description files, whether they fit to your firmware version on the SAFEX-C.12. You find it inside the Collaboration Room and you can get there via ctrlX Store and the ctrlX WORKS ( LINK They are part of the Firmware-package.
- The most recent Engineering version to be used with FW V1.0.1.29 is 1.7.1.8239 that you can find in the very same Collaboriation Room in another folder.
- Another possible solution would be to update your controller to the most recent firmware and the fitting Engineering. This Engineering comes with generic ESI-File import for third-party FSoE-Slaves. For a single device the update can be done with assistance of our technical support. Since in this step IT Security and µSD-Card support have been added, a number of conditions have to be met and considered. That's the reason why this firmware is not available for self-service.
If you need further assistance, please contact my technical support colleague Dias.
Best regards
Your ctrlX SAFETY team
M_Mohann, DNS28 : FYI