Third-Party EtherCAT Device

[TTRD]

Hello,

I want to use a Beckhoff EK1100 EtherCAT-Slave in VeriStand. Unfortunately, I have absolutely no idea how to do this. As far as I understand Scan Engine and EtherCAT works only for cRIO-Chassis.

I have already tried a little bit with LabVIEW and I am able to use the Beckhoff I/O modules in a LabVIEW vi. However, I don't know how to proceed.

Regards,

TTRD

[LarsR]

Hello TTRD,

You should build a custom device like described in the following link.

Building Custom Devices for NI VeriStand

http://www.ni.com/white-paper/9348/en/

Regards,

Lars

[TTRD]

Hello Lars,

thanks for the answer. In the meantime, I read about building custom devices. However, that seems really difficult. In the attachment, you can find my attempt. (I use LabVIEW 2012, but I saved it for 2009, so maybe more members are able to open it.)

I am trying to build a custom device for an Beckhoff EK1100 with one EL1002 (two DI) and one EL2004 (four DO). I think the Initialization VI is fairly correct, but the RT driver VI probably is not correct. When I try to use the custom device in VeriStand, I get an error (-307832): "Dependent File Property: 'Driver VI Path_0' does not have a valid path." However, I could not find where this path was referenced.

Maybe, someone who has experience with building custom devices can help me?

Regards,

TTRD

[TTRD]

I don't know why, but now the following error appears when I try to deploy the VeriStand Project:

Does anyone know what could be the reason for this message?

[TTRD · Accepted solution]

In the meantime, I figured out, what was going wrong. The reason of the first error was that I just built the Configuration and not the Engine. The second error (screenshot from the last post) could be fixed by connecting via ftp to the real-time target and deleting the folder /ni-rt/VeriStand/Custom Devices/Beckhoff EK1100. Now everything works fine. Bizarrely, my LabVIEW code wasn't the problem.