LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

method to build exe with dynamically callable sub-vis

Solved!
Go to solution

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 ...  

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 11 of 21
(1,805 Views)

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.

 

 

 

 

Message 12 of 21
(1,792 Views)

Not contributing, just posting. To get updates.


"Should be" isn't "Is" -Jay
0 Kudos
Message 13 of 21
(1,790 Views)

Me too! Bump!

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 14 of 21
(1,773 Views)

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

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 15 of 21
(1,757 Views)