Labview Ethernet/IP (Implicit) with SoftPLC (Codesys)

[mahmoudhadi]

I was wonderying if Labview Ethernet/IP I/O Data library (ex: EthernetIP  Add Assembly Instance VI) is supported for PLCs other than the Rockwell Logix.

When I setup Labview to do Ethernet/IP Class-1 communication with a ControLogix PLC, it works great, but now I am trying to do the same thing with a SoftPLC from Codesys and it doesn't work.

So I was wondering if the VI's are not supported, or if I am not configuring the communication properly.

I will explain in details my setup. I have Labview running on my Laptop at an IP address of 192.168.100.225 (adapter)

I have Codesys running on a Raspberry Pi at an IP address of 192.168.100.25 (Scanner)

I am using the Labview example: Create Assembly Instance.vi with its default values.

Ethernet/IP scanner is configured to add an adapter as follow:

After a Forward Open command, the connection fails, as shown below from WireShark:

I have tried different settings on Codesys but still doesnt work.

Appreciate it if somebody can direct me to solve this issue.

[karupinwendy]

Hi

Sorry for late response.

I read the Codesys EtherNet/IP Scanner product data sheet on this page. I found this line:

I guess maybe the Codesys scanner requires EDS file of NI LabVIEW adapter.

But NI does not have an official EDS file due to NI product's configurable nature (it's impossible to describe the profile of a changing device). I however made an EDS file in the past for another EIP customer. In this way you have to fixate your EIP VI controls (turn them into constants rather than controls). So you would need to modify this EDS file according to his needs. I use EZEDS to edit it. See the attachment.

Let me know if you have any question.

Wendy

[mahmoudhadi]

Hello Wendy,

Thanks for the EDS file, I will give that a try.

One question, when I opened the EDS file I think there might be a miss match on Assembly numbers

                Param1,,Assem150,       $ O->T RPI, size, format
                Param1,,Assem100,       $ T->O RPI, size, format
                $ if not empty, the connectio nwill be ignored.
                ,,                      $ proxy config size, format
                $ auto if empty.
                $ Config assembly not exposed in VI.
                ,,                      $ target config size, format
                "In and Out",           $ Connection Name
                "",                     $ help string
                $ if a configured ConnectionN entry includes non-empty Target Config
                $ size/format fields, then all other ConnectionN entries, which include a
                $ different Configuration application path and non-empty Target Config
                $ size/format fields, are not available to be added.
                "20 04 24 64 2C 65 2C 66";    $ Path

Hex value for 100 is 64

Hex value for 150 is 96

The path looks like it is using Assemblies 101 and 102.

I am not sure if that affect anything.

Do I need to edit the EDS file before using it?

Mahmoud

[mahmoudhadi]

I believe I can answer myself  🙂

You sent me a template, so I should edit based on my application.

[mahmoudhadi]

Hello,

I have tried to modify the .eds file using EZ-eds software, but still that didnt help.

I have also used the .eds file from a previous post (Ethernet IP toolkit Omron CJ2M PLC)

And that didnt help either.

Is there a working example on how to create the .eds file for NI?

If there is, please send me the link.

Thank you.

Mahmoud

[karupinwendy]

Hi Mahmoud,

Very sorry for late response. It's been kind of crazy these days.

Here is a document that you might refer to: http://www.ni.com/white-paper/13579/en/

Wendy