method to build exe with dynamically callable sub-vis

[LV_Pro]

Not sure if DAQmx installed, but as this machine has been regularly used for other LV2015 DAQ programs I'm guessing it is. The main program launches and performs correctly, until I try and launch the plugin from a PPL. It does work in the dev mode, and the paths, as mentioned, point correctly at the PPL on both machines (I have them in .\data folders on both machines, it works in dev mode, exe on the dev machine, but not on the LVRT machine. Not sure how to go about troubleshooting any missing components, not familiar with using PPL. As I am supposed to be "the pro from Dover" at this company ...  

[550nm]

Re: Resource not found".  If I understand correctly, the error is occurring only on the LVRT station(?)

If your plugin uses DAQmx, then DAQmx Runtime must be installed on the target/LVRT station.  For that matter, if VISA is used then VISA Runtime also needs to be installed. (These should be listed in MAX under "Software".)

When I build plugin's, the NI DLL "lvanlys.dll" is often required to accompany the DLL.

Also, when opening the plugin/VI (located in an LLB) if it's broken, the VI can be "mined" for broken sub-VIs to further characterize the problem.  If you experiment with the LLB-deployment method, the attached VI may be useful for debugging.

[JÞB]

Not contributing, just posting. To get updates.

[LV_Pro]

Me too! Bump!

[LV_Pro]

I'll have to retry the LLB method, have been trying to get the PPL method working so far this week. I'm pretty sure DAQ, VISA, etc., are installed, this is a Toughbook used in the lab for other LabVIEW based tests, utilizing all kinds of NI hardware, including CAN, cDAQ. Just read somewhere (too many locations on the interWeb looked at, having a hard time retracing my steps) of a PPL build setting that might let me look at the internal VIs. Really trying to find a relatively easy (I have to, once successful, show others how it works) means to load vis not present when the Main was built.

P

[550nm]

(I'm probably dating myself, but) when you say "DAQ" I think "NI-DAQ"...

Assuming DAQmx runtime is installed...

I'm still suspecting that the "Resource not found" refers to a missing VI or other dependency such as a required DLL.  A brute-force approach to identifying the offending code is to use the diagram disable structure to eliminate large sections of code (starting with the entire diagram to prove that the "Resource not found" is under your logic). Compile the code, so disabled; if the missing-resource problem goes away when entire diagram is disabled, then selectively disable smaller sections of code until the problem reappears.

I did a bit of experimenting with building a packed library and noticed that (as with Installers, EXEs and LLBs) a "support directory" is specified under Properties\Destinations".  If your "plugin" VI refers to a DLL, the DLL may be copied there during compile.  Make sure any such "support" DLLs are included with the PPL on the LVRT/target!

One more thing...

You might experiment with de-selecting "Remove polymorphic VI instances" (Properties\Additional Exclusions").