Using Telnet in LV2016

[ahmedkochbati92]

Hi all,

i'm upgrading VIs form LV2011 to LV 2016 and i have some errors with Telnet VIs ( i was using internet toolkit for LV 2011 ) any suggestions Please 

Thanks 

[jay0909]

Hi,

 From Capture telnet.PNG

  The "typedef" is missing. May be you have the folder or deleted it . Some of your subvi's are also connected to this typedef. 

[GerdW]

Hi Ahmed,

which problems?

This has been discussed 5 years ago…

[crossrulz · Accepted solution]

The Network toolkit was deprecated and the Telnet library was never added into the base LabVIEW.  You will need to copy the library from an older version in order to use them.

[ahmedkochbati92]

i have the labview internet toolkit 2011 , so where exactly i need to copy this file ?

thanks  

[pincpanter]

C:\Program Files (x86)\National Instruments\LabVIEW 2011\vi.lib\addons\internet

Copy the whole directory.

[ahmedkochbati92]

yes it works thanks a lot 

[ahmedkochbati92]

Hi crossrulz, 

your solution work only if i have LV 2011 installed in my PC because without it ican't install the internet toolkit but my gaol from upgrading to LV 2016 is to be able to run these VIs in Windows 10.

so any suggestions please 

thanks 

[pincpanter]

If you copy the directory C:\Program Files (x86)\National Instruments\LabVIEW 2011\vi.lib\addons\internet into

C:\Program Files (x86)\National Instruments\LabVIEW 2016\vi.lib\addons, you should be able to reuse your project, simply recompiling the internet toolkit code with the newer LV version

I don't use Telnet VIs, but this way I succeeded in using other toolkit VIs in my LV 2017, upgrading from LV 2011.

[crossrulz]

---

@ahmedkochbati92 wrote:

your solution work only if i have LV 2011 installed in my PC because without it ican't install the internet toolkit but my gaol from upgrading to LV 2016 is to be able to run these VIs in Windows 10.

---

That's why you should copy it and keep a copy in a safe place.

Personally, I just use the TCP library since a large majority of Telnet interfaces I have needed never used all of the special coding; turns it into a straight ASCII protocol.