EX drive option not recognized by 3rd party EtherCAT master

I am testing an EX drive option with a Trio Motion controller that is configured with ESI files for ctrlX Drives. So far, I am successfully able to get standard and compact XCS drives to work with the controller. However, when I connect an EX drive to the controller, sometimes I am unable to get the controller to recognize there is any devices on the EtherCAT network at all. Instead, I get an error that no devices are detected on the network.

I suspect that the EX drive in standalone mode is not responding to the Trio's initial packets to scan the EtherCAT network.

I captured wireshark captures from a Trio connected to an XCS2-F with success. I have attached them for reference.

I tried to capture when the TRio connected to the EX drive, but there is only a single packet from the Trio (BWR command) with no response that I see from the Drive. I'm not sure if there is a specific sequence the EX drive expects to switch to 'parallel' mode that is causing this to not work reliably. Can I get some guidance on the expected way to startup the drive?

EX drive is using FWA-V-0610, with ESI files dated from 2025-11

TrioStartup_XCS2F_Successful.zip
293.91KB
3 replies