Hi,
I'm trying to connect our C15 safety PLC to a CtrlX core via Ethercat protocol from one side and to a CtrlX Drive via FSOE protocol tot hte other side and I have some qiestion about both these connections:
1. C15 to CtrlX Core via Ethercat
I configured the connection as you can see in the attached file and it works but I could not understand why I have a gap in the PLC IOs address where I read and write the information from/to the C15.
Why I read the input dataa from the C15 staring from byte 25 when the 1st input bye is byte 12 ?
What are the previous bytes for ?
Same thing for the plc output : staring address %QB24 and QB56 must be use to set C15 input 0-3
What are the previuos output byte used for ?
2. FSOE communitation from C15 to CtrlX drive
I set the communication as you can see in the attached files but the safety sytatu of the drive do not change even if I set the safety bit commands
Why even if the safety bit of the the 2Byte Bit-Coded SMM (780-784) (Slave 1) function are true the drive safety status is still EMERGENCY STOP ??
Why in the C15 status bar I have the message: "RunIntern" as shown in the pccture above?
What am I missing ?
Many Thanks for your help
Giuseppe
For the first issue:
The functional output starts at Byte 5:
In your case, the inputs starts at address %IB25 and the outputs at %QB56:
Hello @Maax ,
there are at least 3 touch points to the documentation of ctrlX SAFETY:
1. The "direct" one to the media directory where you can find doc, VDMA 66413 LIB and certificate/declarations
2. The ctrlX AUTOMATION Doc (Content Delivery Portal) ctrlX SAFETY subdirectory (link to media directory, enhanced Release Notes)
3. The ctrlX AUTOMATION Community "docs"-Link
Finally they all link to the very same documents in the media directory.
BTW: Your question about "where to find the functional output table".
- It is Section 9.2 of the Programming Manual
- The first 5 bytes of the functional outputs are generated by the firmware consisting of state, alive counter, reserved bytes and Error (Alarm, Fatal Error) indication. Only at Byte 5 the application defined IO image starts.
Best regards
Your ctrlX SAFETY team
Hello @giustola69 ,
Your questions
"...
Why even if the safety bit of the the 2Byte Bit-Coded SMM (780-784) (Slave 1) function are true the drive safety status is still EMERGENCY STOP ??
Why in the C15 status bar I have the message: "RunIntern" as shown in the pccture above?
What am I missing ?
..." still remain open.
The second question is the answer for the first one. The Controller remains in "RunIntern" as long as FSoE connections are not established, yet. In this case you even see the device diagnostic lightpipe in yellow instead of green.
Many things can be the root cause of the failing FSoE-Connection.
- Improper FSoE-address setting on slave and master side
- Improper FSoE-Modul assigned to the FSoE-Master slot on the FSoE-Master within the EtherCAT-Configuration
- Improper copying of FSoE-Master- to FSoE-Slave-Slot and vice-versa
Action: Please reconfigure with FSoE diagnostic enabled by removing the hook from the below check box:
The default setting is FSoE-Diagnostics Off which means that the application handles these cases, where all signals are safe (= 0) in case of an interrupted or non-established connection. As soon as the Diagnostics are On, every interuption leads to an Alarm and stops/passivates the outputs of the Controller. This is why it is recommended to switch On FSoE-Diagnostics as long as the problem is found and then return to "Switch Off FSoE Diagnostics".
The non-established FSoE connection explains all that behavior: FSoE Status word is all zero and control state in "RunIntern".
Please mark those answers that helped you as a solution!
Hello@Dias and @Drives_Uwe , can you please check and add additional hints! Thank you!
HTH
Best regards
Your ctrlX SAFETY team
