11-17-2015 01:58 PM
Hello,
32-bit Teststand 2014
32-bit Labview 2015.
VirtualBench Model NI VB-8012
I created a Labview VI using the VirtualBench VIs. This VI is taking a DC voltage measurement with the DMM.
I created a sequence file in Teststand. This Sequence file calls the VI as a Limit Test to see if the measurement is within range.
I created a Labview GUI that calls the sequence file.
I am able to run my VI, Sequence, and GUI. It all works and I am able to achieve my voltage measurement from the VirtualBench.
Now I want to make an executable for the end user. I have trouble with the VirtualBench when making an executable. I created a project in labview and added my GUI with the GUI llb to the project. I built my executable and tried running it. The GUI runs, however, once I click start to run my sequence file I am prompted with an error (See attachment). The VirtualBench VI works normally, but not as an executable... please help.
Thank you
Solved! Go to Solution.
11-18-2015 10:55 AM
Are the functions in the block diagram you provided the entire VI that you are trying to convert to an executable? Or are there other components to your program as well?
11-18-2015 11:02 AM
Did you build an installer? When you create an installer it will tell you what components your application uses and include them in the installer. You are probably missing the VirtualBench drivers/libraries required by the executable.
11-18-2015 11:06 AM
Based on the error message, there is also a Test Stand sequence involved which might complicate the answer we are looking for. And yes, it should be confirmed that all VI's are included in the application build.
12-01-2015 07:33 AM
After working with NI support an answer has been found.
I ended up running my executable in debug mode. While the code was running, I was able to get an error code ERR(-17600) to my attached error message. I was given the link below in an attempt to solve my issue and it worked.
http://digital.ni.com/public.nsf/allkb/9C9EE3A6F7695AB9862578F0006CBF0E
Solution:
Follow these steps to correct error -17600 (sometimes error -18002)
Thank you all for your time and help