About AllAutomation

Hello @WEMO_MPA , every system has its limitations. E.g. cross circuit detection mechanisms are limited by capacity and inductance of the connected devices (IO circuits) and the cable. The values are specified for a proper operation. If you use it outside the specification, it may work and it is your responsibility. The operation will never be unsafe. It is just a matter whether the monitoring mechanisms create an alarm and reduce the availability of your application. Your ctrlX SAFETY team ... View more

Hello @bclapperton , the original error message indicates the source of the problem. Check the output wiring Check the output supply wiring (say U_P at XG31 or XG33) These problems happen e.g. either if you have loosely wired the peripheral power supply U_P or GND_P or if the RTB front connectors are not plugged in correctly (please check whether the lower side is as deep in the housing as the upper side) or if the RTBs are mixed (wrongly plugged). You certainly have RTBs with white pushers. In this case the mechanical coding is not very deep and consequently, even a wrongly plugged RTB may get contact. Please check whether all codings are matching between RTB and the PCB inside the device. This is all resolved in current versions (change indices) of the product. Your ctrlX SAFETY team ... View more

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 ... View more