04-11-2024 01:35 PM
I created a system that used the Chroma LabVIEW drivers and am now building a 2nd system, but I do not want to install full LabView and only the .exe and runtime engine is installed. Chroma suggests placing the files in a specific file location, but those locations do not exist because of not loading the full version of LabView.
I am struggling figuring this one out and where to get everything loaded.
I tried to create an installer and made sure the exe builds included dependencies, but that hasn't worked either. I did direct the loading when opening the exe to find the .dll it was looking for, but it still appears to be missing the VIs needed. Attached screen shot.
Solved! Go to Solution.
04-11-2024 02:26 PM
The message indicates that you are missing the external function DLL.
Did you place the Chroma driver in the <LabVIEW>\instru.lib folder of your deployment machine?
Reference: LabVIEW Driver Installation Guide < Chroma (chromausa.com)
04-11-2024 02:28 PM
This DLL needs to be placed in the same directory as executable (or in \data subfolder).
But the real problem is that this library depends from CVIRTE:
so you should install LabWindows/CVI Run-Time on the target computer, or bundle it to the installer.
04-11-2024 02:34 PM - edited 04-11-2024 02:39 PM
You say labview.exe but talk about a build application. You should place the according DLL (and all its possible dependencies) in the same directory as your "labview.exe" (which I guess is called something else in your case, at least it would be advisable to not call it labview.exe).
And the program looks for Chr61XXX_*.* which is actually a wildcard name and is translated effectively into Chr61XXX_32.dll for a 32-bit application and Chr61XXX_64.dll for a 64-bit application. So your DLL should have the according name.
The data subfolder will only work if the application was build with the DLL in that folder and is likely already in there in that case. But a DLL is only loadable if all its dependencies are also fullfilled and as Andrey showed you it depends on the CVIRTE. LabWindows/CVI is to complex to copy all necessary DLLs into your application directory. Instead you need to install it on the computer too. The only problem might be that it may have to be a specific LabWindows/CVI runtime version.
04-11-2024 02:45 PM
Yes it is loaded and working correctly on the development system.
04-11-2024 02:46 PM
@rolfk wrote:
...LabWindows/CVI is to complex to copy all necessary DLLs into your application directory. Instead you need to install it on the computer too. The only problem might be that it may have to be a specific LabWindows/CVI runtime version.
Usually CVI Run-Time is backward compatible, so the DLL built with older CVI is usually fine with higher version of Run-Time. But for very old CVIs this may be not true. I would like to recommend to start with latest available, and only if this doesn't work try older versions.
04-11-2024 02:48 PM
Thanks for the suggestion, I will give it a try and load LabWindows/CVI. Sorry, yes I was being generic defining the .exe.
04-11-2024 03:01 PM
Looks like the LabWindows/CVSI run-time solved the issue. Thanks for the suggestion!!