LabWindows/CVI
Ethernet/IP in LabWindows?
This is a very rough start from some code that I had done in LabVIEW to communicate with a Keyence sensor that offered an Ethernt/IP interface as one of the possible options. The LabVIEW code did work but this here was never finished! So beware, it will require some more debugging for sure and looking at other implementations like https://github.com/EIPStackGroup/OpENer/tree/master/source/src/cip (which is an example device implementation in C, so the other side of what you want to do here, but it can still help to understand the actual protocol) or https://eipnet.codeplex.com/ (which is another server implementation but in C# so not directly applicable for CVI either).
One thing that put me off is the callback handling of the data that the CVI TCP library requires. That makes everything kind of tricky, although as long as you don't execute this code in a seperate thread it should probably be fine. Otherwise you will quite likely run into trouble with the callback and the EthernetIP_Read() function accessing the data in the connection resource in parallel and possibly conflicting.
This is very simplicistic! Ethernet/IP consists of many more messages, quite a bit is devoted to cyclic messaging and setting up periodic update messages by the device itself. This library only implements the RegisterSession, UnregisterSession for establishing and tearing down of a session and the RequestResponse command for acyclic command/response messages. This should be enough for simple IO based devices but will fail for many other classes of Ethernet/IP devices.
And the most important thing, just like with Modbus you do have to have documentation about what serviceCode, classID, instanceID and attributteID you need to use to access a specific item (register) in the device and what datatype the possible data value is supposed to be. So while the Ethernet/IP part is basically handled (albeit never fully tested in the CVI case) you will need to implement something along the lines of what is shown in example.c for your own device. And that means your device will need to come with documentation for this. If you can't get that documentation or you do not know how to apply the information from it, this library will still do absolutely nothing for you.
