03-28-2018 09:42 PM
Hi,
I want to build an executable file for my project which has plug in sub VIs. I have below error when I run the .exe file.
"
Error Code: 7, Error Message: Open VI Reference in mainGUI.vi<APPEND>
VI Path: <b> ************* </b>
Built Application or Shared Library (DLL): Make sure all dynamically loaded VIs were properly included in the build specification for the application or shared library.
LabVIEW Real-Time: VIs built into executables cannot be accessed through VI Server calls. Use Source Distributions to dynamically call VIs on Real-Time targets.
"
In my mainGUI.vi, I use below method to plugin a sub VI. And I had include the folder PlugInVI while building .exe file. What should I do to solve this error?
Thank you!
Solved! Go to Solution.
03-29-2018 05:21 AM
Are you sure that VI is in that location? That is what the error is indicating.
03-29-2018 09:48 AM
If your exe is in ..\builds subfolder, move it to the project folder; or move the PlugInVI folder to ..\builds\PlugInVI.
03-29-2018 10:06 AM
What code/nodes (primitives/non-primitives/driver APIs/DLLs) does your "sub_8743.vi" contain?? Could you post that VI here?!
03-29-2018 10:11 AM
Hi
It seems like the absolute path to your SubVI is different than expected during run time. You can fix this by going to the properties of your build and fix locations for PlugIn VIs. Also try building llb files(select remove block diagrams option) instead of copying your SubVIs into builds folders so that your source code will be protected as well.
04-01-2018 10:26 PM
Dear Zou,
I tried your suggestion, it succeeded. But it also means I need to put my sub vi source together with my exe file. Is there any way that I can only pass this exe file to my end user without giving them the sub vi included?
My structure is I have one mainGUI which is my user interface. sub_xx.vi is the subVI used in main. PlugInVI is the sub vi done by other developer which is inserted into sub panel of mainGUI. Driver folders are vi called by vi in PlugInVI.
04-01-2018 10:50 PM
Dear Freelion8,
I tried to build the llb file which includes all my sub VIs. But during the exe file generation, I cannot find a way to include this llb file. What would be the steps to include llb files into exe file generation instead of using original sub VI files for IP purpose?
04-02-2018 12:24 AM
@Dylan.Zhong wrote:
Is there any way that I can only pass this exe file to my end user without giving them the sub vi included?
No! If you don't (want to) include the SubVI (developed by other developer or whoever) along with the EXE, how would LV know which VI to call dynamically?!
04-03-2018 08:26 AM
Hi
Go to properties of your build, then select Destinations, here, you can add new destination folder for your llb files by clicking "+" sign, give a new destination label for each destination you added, select llb option for each destination. Next, go to source file settings, click on your project file under "Project Files" section, and select a destination for the selected file from "Destination" drop down list. By the way, in order to see your project files under "Project Files" section, you may need to add your SubVIs, Controls and Main VIs to your project as an auto-populating folder or as a .lvlib if you are using libraries. If you do this right, your .llb files will be successfully created along with your .exe file. Also remember, you need to fix your source code in order to find the right path for each dynamically called SubVIs, you can always create a case structure for which environment you are using ,Development System or Run Time System, and create a right path for each dynamically called SubVI, especially for Run Time System, you need to call them from your .llb destination.
04-03-2018 08:59 AM
@Freelion8 wrote:
If you do this right, your .llb files will be successfully created along with your .exe file.
On the contrary, the OP's question was "Is there any way that I can only pass this exe file to my end user without giving them the sub vi included?".
Is there any way, really?!