Hey guys, I'm working on a Beckhoff TwinSAFE project using TwinCAT 3 with 2 EL6910 Safety controllers. I need to establish data exchange between them. I have set up a Custom FSoE Connection on both controllers with matching IO configurations and linked the data to the appropriate Messages. Both sides of the Custom FSoE Connection have the same Safe Address and share the Alias Device. Despite being able to successfully verify and download the project, I am unable to run it as the Custom FSoE Connection State keeps toggling between 0x64 (reset) and 0x65 (starting). The diagnosis indicates that the FSoE Master and StartUp-Slave are reporting Failsafe Value active. Unfortunately, I have not been able to find a solution in the Beckhoff manual or through their support. I'm hoping that someone here can assist me with resolving this issue. Thank you in advance for your help! - Jack.
Hello, I hope you were able to resolve the issue. Thank you in advance for your response.
The issue has been resolved thanks to a factory Safety engineer from Beckhoff Germany who informed me that setting an Error Acknowledge for COM ERR Ack of the FSoE Connections is not permitted unless certain conditions are met. This feature will be disabled in future versions.
Hi Jack, sounds like you've crossed all the T's and dotted all the I's. One possibility could be a mismatch or misconfiguration Issue between the FSoE master and the FSoE slave. Cross-check if they both are running the same firmware version; sometimes even a minor difference can cause hiccups, especially when dealing with Beckhoff TwinSAFE. I would also check the safety settings of the IO devices on both the FSoE master and the slave. It's crucial to ensure that their safety configurations match. Lastly, don't forget to examine the wiring, including power and Ethernet connections. Loose or miswired connections can also trigger this type of issue. Remember that the TwinSAFE components need to be wired together with the EtherCAT network. I hope this helps!
Hi Jack, it sounds like you've got all the initial setup correct, but still having trouble getting it to run. One often overlooked point is to double-check if you've updated to the latest firmware on both the EL6910 units. Old or mismatched firmware can sometimes cause issues with FSoE connections, leading to the alternating state issue you're seeing. Also, ensure that the ghost nodes have been cleared. If there are still ghost nodes with same address but different Alias Device in your project, then data exchange might be difficult to establish. Give it a try and let us know. Hope this helps!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: The toggling between 0x64 and 0x65 states may indicate issues with the FSoE communication setup or configuration mismatch between the controllers. It could also point to problems with the Safe Address, Alias Device, or IO configurations.
Answer: Answer: To address the 'Failsafe Value active' error, ensure that the data exchange setup, including the Custom FSoE Connection, is correctly configured with matching parameters on both controllers. Verify the Safe Address, Alias Device, and IO configurations to ensure consistency.
Answer: Answer: While the Beckhoff manual and support resources are valuable, community forums and discussion platforms like this one can also provide helpful insights and solutions from experienced users who may have encountered similar challenges.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.