LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

HD Crash Recovery

IMG_3680.jpeg

 Hello,

recently i had a HD crash on a windows XP machine . I had another windows 10 PC and was able to recover the code from old PC which was Windows XP. I am stick with the current issue with a picture attached. I am not able to figure out with the ethernet ip interface why the session in does not match in labview 2017 but it does in labview 2010. Any help would be appreciated.

i do apologize in advance if i missed any information. 

0 Kudos
Message 1 of 9
(193 Views)

Ethernet/IP is a toolkit in LabVIEW, not something built-in.

 

You probably need to download it for 2017:

https://www.ni.com/en/support/downloads/drivers/download.ni-industrial-communications-for-ethernet-i...

 

Note that you need a license for it.  If you can't find it you may need to contact NI.

 

I haven't used this so I am only 80% sure this is your problem.  Please double-check before buying a new $800 license if you can't find an old one.

0 Kudos
Message 2 of 9
(164 Views)

I did install the ethernet ip toolkit, i was able to find the .dll file and point to the right location it cleared some errors . Still in the code i have broken VI call library function, specifically the ethernet session io.

One error is invalid ref number class

Two terminals of different types ( keep in mine i was able to get this to work on 2010 version but no luck on 2017)

 

And last error of course unwired terminal

 

IMG_3681.jpeg

0 Kudos
Message 3 of 9
(146 Views)

Can you post your actual code in LabVIEW 2020 or less? Pictures are hard to troubleshoot.

Thank you

Tim
GHSP
0 Kudos
Message 4 of 9
(118 Views)

I have attached the code; you might have issues opening due to .dll file missing. 

0 Kudos
Message 5 of 9
(108 Views)

Looks like you just need to replace the broken VI with a new version in the palette. See below:

aeastet_0-1747405653119.png

When I use the one from this palette it is not broken.

aeastet_0-1747405769543.png

 

 

Tim
GHSP
0 Kudos
Message 6 of 9
(91 Views)

I must be missing a file or something, i even tried creating a new Vi with just the messaging read and once i open the front panel of the VI it is still broken. Somehow i need to find the difference between the two machines one has labview 2010 and one has labview 2017.

 

2010 works, now i am trying to create a .EXE and to run it on the 2017 machine 

0 Kudos
Message 7 of 9
(78 Views)

When I followed the DLL path in your attached VI it was to a user folder. Someone must have copied the dll into the project or folder. I would start by deleting the dll in the folder and finding the one in the vilib folder. 

aeastet_0-1747411935986.png


Use this one:

aeastet_1-1747411971096.png


The block diagram for this one is password protected. Delete the old one and restart your program or open the project manager.

Tim
GHSP
0 Kudos
Message 8 of 9
(69 Views)

i have tried this several times, and i still dont have the option for "INDUSTRIAL COMMUNICATION" in my functions pallet . And i have downloaded the package for the industrial/ethernet communication through NI Package Manager. I think if i finally have this option and replace the old Vis with the new Vis it will work. I appreciate everyone support and comments, I will keep trying !!

0 Kudos
Message 9 of 9
(39 Views)