why VI package is empty???

[ann991]

Hello, I always have this problem with VI package and I don't know why please does any one know how to solve it ?

[Bob_Schor]

If I had to guess, I'd guess that you haven't enabled TCP/IP in LabVIEW 2017.  Did you follow the suggestion to check in the Tools Menu?  The other thing to do is to click the little down-arrow by the Version (2017) and select Configure LabVIEW Versions, which will test the VIPM/LabVIEW Communications setup and alert you if there's a problem.

Bob Schor

[billko]

Is it possible that you upgraded from an earlier version of LabVIEW but forgot to update VIPM?  I thought I read somewhere about VIPM being updated because LV 2017 isn't backward-compatible with earlier versions of VIPM or something like that.

[ann991]

I have the same port tcp/ip in labview and vi package but there is no connectivity i don't know why 

[rolfk]

Another possibility is that when you first started VIPM you got a message from Windows that a program wants to use network communication, and it's very easy to dismiss this dialog when wanting to get the program started to see how it works. However this will Windows consider as refusal to let the app use network communication and this will be stored in the firewall rules for future invocations.

Once the firewall is set to disallow network connections for a process the WinSock functions will all silently fail to not give a troyan or other malicious software module any hints as to the fact that they are actively blocked.

You can review the current firewall rules under Windows Defender Firewall with Advanced Security or similar depending on your Windows version and edition.