LabVIEW Run-Time Engine 2015 SP1 compatibility with Windows 10

[ZoltanMTS]

Hi,

We have a Compact RIO connected to a PC, which has on Windows 7 and a Labview compiled / stand-alone application running on LabVIEW Run-Time Engine 2015 SP1 (if I remember correctly, 32-bit) without any problems. The cRIO has a TCP link from the PC, which sends commands to the cRIO and it has a UDP link to the PC, which is basically a data stream.

We have migrated it to a Windows 10 laptop and the software does not work. The TCP link is OK, but the UDP link does not get through. Just in case, we switched off the firewall and the virus checker, but still the same. I am aware of that it is typically a computer security related issue, but as I was checking NI’s Windows 10 compatibility information (https://www.ni.com/en/shop/software-portfolio/national-instruments-product-compatibility-for-microso...), I spotted that, there is nothing about LabVIEW Run-Time Engine 2015 SP1.

As a start, I have two questions:

1. Is LabVIEW Run-Time Engine 2015 SP1 Windows 10 compatible?

I have not find LabVIEW Run-Time Engine 2015 on the compatibility list.

NI LabVIEW 32-bit is compatible and using the same engine, so I expect it to be compatible, but it uses NI LabVIEW FPGA Module, etc and in those cases, only 2017 is compatible.

2. Do I have to build the stand-alone application on the same OS version I want to run or do I have to re-build it for each OS version?

Apparently, lvanlys.dll in the data folder is key to run the stand-alone application.

So if I just copy over the built folder with the stand-alone application and data folder with lvanlys.dll, it may be not compatible with the different version of Windows (built on 7, run on 10).

Thanks,

Zoltan

[ZoltanMTS · Accepted solution]

The answer is yes, it is compatible, at least it worked for me on VirtualBox.

Th issue was with Windows security, which blocked the communication link, as usual.

Zoltan

[billko]

I'm sorry this went ten days without a response; this is actually the first time I even saw this post.  Thank you for following up with a solution to your own problem - this will give someone else a chance at fixing their issue in the future.  🙂

[Justin.Cho]

Hello.
I'm trying to install LabView 2018 SP1 version RT on virtualbox 7.0.18 version of Windows 11 pro.
It went well from installation to execution.

However, there is a problem with network communication.
I can't ping.

After installation 169.254.IP is assigned and the network method is used
Host only, bridge, nat, nat network No matter how you change it, it does not ping from host to guest.

If you have any experience, please help me.
Thank you.

[rolfk]

Network configuration of virtual machines is a bit of magic and it is always difficult to give generic advice. Things to consider: 

- Bridged configuration directly connects the (virtual) network adapter to the physical one. Your host computer or other virtual machines can’t connect to this directly only if the data is routed over the external network.

- 169.254.x.x addresses are auto assigned for DHCP configured network  adapters when no DHCP server could be found. They are NOT routed across subnet borders.

Read the last sentence in both points above and draw your conclusions!