Lol! I really should have started with the one with the DAQ sub-vis built in to confirm that the target would play nice, lesson reminded (I’m pretty sure I “knew” it a long time ago!). Was too focused on making the plugin work, and figuring if it didn’t that was the problem. As I mentioned on Friday, I tried running my exe with the "plugin" vis actually as part of the main, rather than plugins, which showed me that at least one problem was the target computer (hmmm, Windows VISTA and a stale version of DAQmx). Today I got a Toughbook with Windows 7 and the "combined version" of the EXE showed the same problem as previously, missing DAQ vis. I was able to run the DAQmx 17.1 update (this machine has Win7!) and (sound of trumpets and cheering) my ORIGINAL attempt at using PPL's worked, the one from early last week!
Thanks to all for their helpful suggestions, the DAQmx was called into question pretty early in this thread but I chose to be overly optimistic, "knowing" that the laptop has been frequently used for DAQ stuff, immediately suspecting my code, and focusing on the fact that PPL's don't give a lot of information in their errors, other than "I'm broken and can't get up". On the other hand, the "standard" main exe, with the vis built in, did say "I'm broken and here is what I don't like", pointing me in the right direction.
PutnamCertified LabVIEW Developer
Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5
LabVIEW Champion