LabVIEW
1abvi3w
Solved!
0. Yes, my OS is win10 64bit.
1. Run this EXE normally without any error on other PC installed only LabVIEW2014 runtime.
2. I have another version LV2021-bit64,the VISA Version in the following screenshot from my PC should be installed when I install LV2021.
3. So I must install at least two OS to install these different LV version and drivers?Maybe I can uninstall LV2016 and 2018, but I must keep 2012,2014 and 2021.
4. How about the error with Intialize keyboard.vi? This problem presents frequently.Sometimes, I copy the lvinput.dll from LV2018 and replaced the same dll in LV2014, the error is solved, but mostly it's not work.
The VISA version difference is most likely a red herring . VISA is the one driver from NI that has almost 0 chance to cause problems if you use the latest VISA version with a very old LabVIEW version. For other software drivers from.NI it is very important to make the driver installation not newer than 4 years after the LabVIEW version on the development PC, since you otherwise miss all the driver VIs in your LabVIEW installation. Those VIs are installed by the driver installer and that installer only supports the last 4 LabVIEW versions at the time it was released.
For a built executable it is often possible to install a newer driver BUT that is unsupported since you effectively develop against a different driver version than what you finally use. If NI changed anything on the driver API in terms of parameters between versions, the installed VIs by a particular driver installer are adapted to work with that new driver but will of course possibly not match the driver interface of a different version. The chance for that is small as NI usually does not change driver API signatures just like that, BUT NI reserves the right to do that and explicitly does not guarantee that such changes never will happen and that a particular built application only is fully compatible with the driver version it was built with. Most times it works just fine with a newer driver but if it doesn’t NI can wash their hands in innocence and say: “We never claimed you could do that!”
The lvinput.dll crash is a different albeit related problem..This interfaces to Windows API functions and while Microsoft usually is even more obsessed with backwards compatibility of APIs, for graphics and sound APIs they tend to not only invent a new one every few years but also make modifications to the existing ones sometimes. LvInput in LabVIEW 2015 was modified to work with newer Windows 10 systems but your 2014 version doesn’t know about Windows 10. So the limitations on what Windows version specific LabVIEW versions are compatible with are not always empty fearmongering but have some real substance. Without using the sound VIs your application quite likely would not have such a version problem but with them it has!
.png){kind=link}
