LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Getting started with Ethernet I/P (Industrial Protocol)

I want to control a motor via an interface box which uses Ethernet i/p. I've never used this protocol before.  Confusingly that is 'Industrial Protocol' not 'Internet Protocol'. 

 

  There is a toolkit for this dated 2022, but it says that there is nothing to install. Maybe it is included with 2024? 

 

 Could anyone please point me in the right direction? Either with the toolkit or sample code, in order to get me going? 

 

   Thanks,

 

       Ian 

0 Kudos
Message 1 of 4
(1,304 Views)

NI has a LabVIEW toolkit for this:

https://www.ni.com/en-us/shop/product/ni-industrial-communications-for-ethernet-ip.html

 

It is not free though.  Is that the one you tried to install?

 

If you don't have or won't buy a license for that, I've previously had good luck with EEIP.DLL, a .NET Framework DLL, in LabVIEW.

 

The site that maintained it was http://www.eeip-library.de/ but it appears to have not been renewed.  If you look a year back in the archive.org wayback machine you can still see the site.

 

There are still official-ish places to get it:

https://www.nuget.org/packages/EEIP/

https://github.com/rossmann-engineering/EEIP.NET

0 Kudos
Message 2 of 4
(1,267 Views)

Hi Kyle,

 

I'm using EEIP dll to communicate and seeing an issue; thought i would share in this thread.

 

I'm writing a command signal periodically from labview, and dll function is not generating any error; but on my PLC, it is not receiving my command consistently. Attached screenshot for reference.

 

image1.png

jhareshakella_0-1778594303200.png

 

Is there a known sequence/ placement of using EEIP dll in a continuous read/write use-case?

 

Regards,

Jharesh Akella

0 Kudos
Message 3 of 4
(423 Views)

I've only used the EEIP DLL on two applications, and on neither of those have I seen a time where the DLL sends something that the hardware doesn't acknowledge.  No specific sequencing was needed.  Though both of my applications were on very simple hardware so it could be that the hardware you're communicating with is related somehow.

 

 

0 Kudos
Message 4 of 4
(409 Views)