SAFEXC.15 is not recognised in the ctrlX IO software

[ericvergara]

Hello,

We have a SAFEXC.15 V1.0.1.19 FPGA207

And the option that the device can be scanned is active

We have added the .xml of the version of the SAFEX, however in the ctrlX IO Software if we "Scan for Devices" it seems that it is not recognised:

We have tried with different ctrlX Cores and with different versions of ctrlX IO but the problem still persists,

Also we have added it offline in the ctrlX IO and transfer it to the bus, then in the Ethercat the device stays in INIT so it is like it is not connected,

How can I solve this?

Thanks,

[Drives_Uwe]

As it looks like you are Bosch Rexroth employee you may follow the internal WebSeminar given in September this year. I will send to you an extra link via Email.

[LuisCtrL]

Hello Uwe,

Can you send me also a link of the training?
We still couldn't find a solution to this. 

Thanks 🙏

[JordiLaboria]

Good afternoon, I think the problem could come from the fact that we cannot modify the "extended Protocol" option of the XF28 and XF29 connectors to "FSoE Slave", as it is described in the manuals.

This is the manual description for both Safex C-12 and C-15:

Can we find a solution for what Eric says?

How can we change this option?

I have tried several versions including 1.7.1.8239 and the result has been the same

Jordi Laboria

E-Mail: jordi.laboria@boschrexroth.es

https://www.youtube.com/channel/UCzE-ieCIkyMsuvyE0UDji9g

DCET/SLF4-ES

[AllAutomation · Accepted solution]

Hello colleagues,

please return the device to DC-AE/SVC432 and ask for cost-free express handling. Most probably there is a defect inside the EtherCAT EEPROM. It results exactly in the symptoms you see in the ctrlX I/O Engineering. The identification by the information from the device description file is not possible. It is not a hardware damage, but a software defect that will be corrected in the factory. You will get your very same device back.

Your ctrlX SAFETY team

@Drives_Uwe , @Dias : FYI