02-10-2021 10:28 AM
I am deploying a LLB file to a cRIO. This is a cRIO 9014. The software on the cRIO is supposed to dynamically load the main VI in the LLB. When the Open VI Reference is run with a path to the VI, it fails with a 1003 error code.
The explanation for the error:
LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it.
When I open this VI from the LLB in the LabVIEW environment, it is fine.
The VI calls two FPGA programs. One is to retrieve calibration data. The other is the main FPGA program. The Open FPGA VI Reference that loads the FPGA lvbitx files is configured to use lvbitx files instead of a VI. Maybe these lvbitx files need to be somewhere specific? You can't add them to the LLB apparently. At least the build spec for the Source Distribution won't let you add them.
So I want to know two things.
Do I need to do something special to include the lvbitx file?
How can i determine what is missing given that the error only occurs when I try to run it from the cRIO?
02-10-2021 01:24 PM
More information.
If I use a disable diagram on everything but the OpenFPGA VI Reference, then the driver still fails to load. There may be other problems in the disabled code, but the FPGA code is definitely one.
If I then disable the Open FPGA VI Reference, then the driver loads. (It doesn't do anything, but it loads.)
So what do i need to do to make sure the driver file in the llb can find the lvbitx file?