I can't solve this 3686 error, and also don't understand the meaning, since nothing refers to MS0 in the manual nor in ctrlX SAFETY engineering. Does it simply mean that there's a mismatch between the physical connexions configured and how it's actually wired ? I've tried to disconnect most of them but the problem remains.

I also have Schmersal SFB FSoE slaves.

Some help would be very appreciated.

Thanks in advance.

Thomas

I am trying to implement the following behavior:

An emergency stop (E‑Stop) is provided as a two‑channel, time‑monitored input. Both E‑Stop contacts (channels) should be monitored in such a way that it is possible to detect when one of the channels no longer switches off (i.e., remains stuck). In that case, the input must not be allowed to—return to the state “TRUE” / “OK”.

In the documentation, I found the function start‑up test (“Anlauftestung”). My understanding is that the E‑Stop must first trigger in the monitoring direction (=> both channels = 0) before it can be re‑enabled. This would solve the issue described above, but I am unable to get the function to behave accordingly.

Have I misunderstood the function? Is there another way to achieve the required behavior?

Thank you for your support!

What is the recommended software setup to ensure a correct installation of the laser scanners?

Thank you

My customer wants to connect 13 emergency stop buttons to 13 drives. When one button is pressed, they want all drives to be safe torque off. So the status of a single safe input needs to be passed to the SAFEX which then turns off all the drives.

Also, is it possible to use a SAFEX to communicate with drives by itself? ie. with no ctrlX or other fieldbus master? Or does there always need to be a fieldbus master?

I cannot send the "profile" configuration of the slave device from the SAFEX C12 master. Export (.pak) always fails, no matter the EtherCAT status (Op, SafeOp etc), nor the status of the C12 (Running, Stopped).

• The EtherCAT is running, no error

• The ESI file is integrated into ctrlX IO Config and ctrlX SAFETY

• In ctrlX IO I configured the IN/OUT for the C12 according to what the Schmersal ESI file shows

• In ctrlC SAFETY I configured the "Profile" for the slave with the port (X0-X7) configuration.

• The FSoE address settings match (rotary switches on the device and config in ctrlX SAFETY)

• I can see in the CoE of the slave that it has CRC_0 and CRC_1 values. But in the master, the CRC are 0 for the "MasterCommand" and constantly alternating between 2 values in the "SlaveCommand".

To me it looks like the SAFEX is not able to write the CRC to the slave, or that it cannot match the CRC of the slave.

Anyhow, I'm trying to figure out why the Export (.pak) in ctrlX SAFETY doesn't work. And I am suspicious about the version of my ctrlX SAFETY Engineering tool. My version is : Version: 1.8 Product version: 1.8.3.10207 Compile date: Wednesday, May 22, 2024. Is it a known problem on this version or am I missing something ?

In attachment, the CoE parameters of the Master and the Slave.

Thanks a lot for your support.

Thomas.

I have a request for connecting Safex SMMC communication trough WIFI is this possible?

• Would the SIL level be affected ?

Hardware : Safex -C.15 , via Eth2

Thanks!

C15 Safetylink connects multiple drivers how do I differentiate drivers?

How the driver safetylink address is associated with safety logic？