About MST

MST · ‎10-17-2023

Hi everybody, I'm trying to connect EtherCat Slaves via the slave to slave configuration in the I/O-Engineering (V1.20.1). It works e.g. for the connection between SICK Sensors and the SAFE-X configuration: I can download the configuration as shown in the picture without any problems. As soon as I add any connection using the KRC4_secondary_EL6695_1001 slave (example in the picture below)... ... and download or save the project, the configuration is deleted (see below). It is also deleted, when the configuration is made offline without any conecttion to the EtherCat (Cable unplugged). Therefore I don't think it is overwritten by any other participant in the network. Any idea where my problem is? The communication between the Kuka-Slave and the PLC-App works fine and data exchange is possible. Also the ESI-File is the latest from the KUKA downloadcenter. Thanks for your help and regards 🙂

MST · ‎10-17-2023

Thanks for the infos! Using the slave to slave configuration instead of the PLC based copy method gave me the alarm 7614 "Ungültige FSoE Prozessdaten" instead and dind't solve the problem. Yet it works after: 1) Updating to the recent firmware and the fitting Engineering thanks to the help of your colleagues 2) Connecting the scanner and the SAFE-X via slave-to-slave in the IO-Engineering instead of the PLC copy method 3) Using another ESI-File for the SICK scanner. The file which is pre installed in the engineering seemed to be the big issue in my case

MST · ‎10-11-2023

Hi everybody, I'm trying to connect a SICK microScan3 to a SAFEX-C12 via FSoE. Sadly I get the Alarm 7608 "Ungültiger FSoE Daten CRC" and cant find my mistake. The Firmware Info of my SAFEX-C12 and the Engineering Version please find attached. I configured the connection with the following steps: 1) Configure the FSoE Master: 2) Configure the FSoE Slave according to the parameters in the Slave itself (Disable Safety Configuration Check won't help): 3) Configure the EtherCat in I/O Engineering (The System is running and in state "OP"): 4) Map the data in the ctrlX CORE PLC program (if I map the data in the I/O Engineering an not the PLC Program i get the alarm 7614 "Ungültige FSoE Prozessdaten"): Any ideas where my problem/mistake is? Thanks for your support!

MST · ‎02-15-2023

After finally beeing able to test it, updating the runtime App and the Designer to the same version worked. Thx 🙂

MST · ‎01-24-2023

Hi, deleting the Axis in the Motion App didn't work, but reloading the default parameters in the DRIVE Engineering did. Somehow the Processdataconfiguration of the EtherCat interface was displaced. The data between Motion App and DRIVE Engineering had somekind of offset or sth. like that (See picture attached). The application Profile was set to "Servodrive Profil" in the old an new configuration, yet the interface looks different now and it works. Thanks for your ideas and support!

About MST

I/O Engineering - Slave to Slave connection can't be saved

Re: Alarm 7608 - Connecting FSoE Slave

Alarm 7608 - Connecting FSoE Slave

Re: WebIQ crashing after publishing project

Re: Modulo Axis using Motion App