About cc2go

Hi, the EoE settings looking good, to acces via the CORE to the WAGO device you need to set a route. You can check before, that a EoE connection is visible in the CORE Web UI connection settings. Example of routing and what I mean, you can find in the docu of the EtherCAT Master App: https://docs.automation.boschrexroth.com/doc/3233068867/acyclic-communication-mailbox/latest/en/ When a EtherCAT device supports firmware update via FoE, with the CORE runtime and EtherCAT Master v1.16, it's possible to do a FoE firmware update with ctrlX IO Engineering as well. ... View more

Process data communication is possible without the IODD. The porcess data mapping, where your data are, you can mostly find in the docu of the IO-Link devices. Depending on the EtherCAT IO-Link Master, it's possible with the manufacture tools to set parameters in the IO-Link devices. ... View more

Use the ctrlX as router, for ifm Moneo or LR device, is supported and will work, with the ifm firmware which supports EoE. ... View more

Hello, IODD of the IO-Link devices is not supported with the ctrlX IO Engineering. which version of Ethercat Master and ctrlX IO Engineering are you using? You are using the latest ESI and FW of the WAGO device? Can you see any diagnosis in the EtherCAT Master or on the WAGO device in the ctrlX IO Engineering online? May we can have a MS Teams, send me a PN. ... View more

thanks to @CodeWasi he did a Profinet capture, after a first investigation, the device send a Status: Error: "RTA error", "PNIO", "RTA_ERR_CLS_PROTOCOL", "AR consumer DHT/WDT expired (RTA_ERR_ABORT)" we checked the last cycle times, it's mostly below 8ms. The observation was, reboot/power cylce the device will not force the issue, reboot/power cylce the controller will force the issue. The question is, why send the device this abort? ... View more