How can I get a cRIO-9025 in Active mode with a WAGO EtherCAT 750-354 slave

[graemekb]

I'm trying to get a WAGO 750-354 EtherCAT coupler working as an EtherCAT slave with a cRIO-9025 as the EtherCAT master. 

I'm running the following software:

LabVIEW 2011 SP1

LabVIEW Real-Time 2011 SP1

NI-RIO 4.1

NI-Industrial Communications for EtherCAT 2.3

I've gone through all the whitepapers and configured everything correctly however I can't get the cRIO to enter Active Scan mode.

I have a 4 Digital Input slice and 8 Digital Output slice attached to the coupler which show up during device discovery and I have deployed this configuration to the cRIO.

When I deploy the above configuration and attempt to switch the Scan Engine into Active mode I get the following error:

I have got the hardware working using a Beckhoff TwinCAT system but that required linking a hardware variable to a PLC (application) variable in order for the WAGO system to enter operational mode. I believe that some IO variables need to be defined in order for the EtherCAT bus to sync correctly before becoming operational.

I attempting to replicate this by deploying an IO Test.vi to my cRIO which reads an input and sent this value to the digital output but with no success.

I've attached the WAGO device definition XML file for reference.

Any further ideas on getting the IO working?

Cheers,

Graeme

[graemekb]

In addition to the above when I manually attempt to change the WAGO controller's state into Safe-Op mode it returns the following error:

Which indicates a Sync Manager error with an error description 'Expected Channel Enable' for Sync Manager 3

[Pete@NY]

I had similar errors when connecting an EtherCAT module from Murr.  When contacting NI for support, it came down to the fact that the current NI-Industrial Communications for EtherCAT driver does not support Module Initial Commands.  So, even though you are able to see the device(s) and have it autopopulate the device tree in the project view you will not be able to get the EtherCAT slave to enter an Operational state out of the box.  

If you're willing and able to spend time digging through device config files and reverse engineer a driver using the WriteSDO method, then it may be possible to use your third party slave.  In short, NI does not seem to support a large variety of third-party EtherCAT slaves despite their claim otherwise.  I've been told a future version of the EtherCAT driver should support the necessary commands, but I haven't seen it yet.  

[graemekb]

NI provided the following cRIO files to allow communications but I'm not sure if it affects operation with other devices after installing these files. 

niecatmaster.out needs to be copied to '/c/ni-rt/system/' (on the controller)
nilvecat_ioplugin.out needs to be copied to '/c/ni-rt/system/ioplugins/' (on the controller)
WAGO_750_354.xml needs to be placed in \Program Files\National Instruments\Shared\IndComECAT\DD for EtherCat Slave discovery within a LabVIEW project.

[Daikus]

For me it worked without special settings. 

lv2012

industrial ethercat driver 2.5

real time 12

On older system with lv2011 and industrial ethercat driver 2.2 and real time 4 it didn't worked.

Greetings.