Issues building an executable

[ben64]

I'm having problem building an application with DQMH modules using VIs from a PPL. At first I identified the source as the Module Start.vi (error 1003 at the output), then narrow it to Get VI Main Information.vi returning a bad executation state. I then tried to make an executable from a single DQMH module with most of the VIs disabled and finally identified what seems to be the source of the problem: a class object from a PPL in the Module Data -- cluster.ctl. When replaced with a string control the built works (note that I disabled all the module VIs that use this object).

I also tried replacing this object with the default LabVIEW object and got the same problem.

Any idea, suggestion how this can be solved? I tried a lot of combinations for the built specifications be never got a working executable.

The module is a power supply module that implement an HAL. The supply class object in the module data cluster is an interface parent class to be overridden at runtime by a plugin (also a ppl).

Ben

[ben64]

Got an idea, probably related to the private scope of the module data cluster. Will try adding the supply object outside of the module data cluster and come back with the result.

edit: No doesn't work even if the class object is not in the module data cluster.

Ben

[ChrisFarmerWIS]

Hi ben64,

This might be completely unrelated, but have you run the DQMH Validation tool.

I mention this because I recently had an issue where it was all running fine in the dev env, but when I tried the exe I had issues. 

I ran the validation tool, and turns out I had an old DQMH module (from a previous version of DQMH).  I ran the validation "Fix Issues", and then rebuilt the exe and it ran fine.

Might not be your exact issue, but just a reminder to run the Validation tool to catch any issues like this.

Regards

[Cloedu72 · Accepted solution]

This sounds like a problem with these causes:

• Missing items in the project
• Sub-PPL has missing items 
• PPL has a problem with private controls
• Sub-PPL has a problem with private controls
  => switch all controls from Main.vi and Public VI's to "public access scope"
• Renamed project file of a Sub-PPL 
  => You need'to recreate the PPL build specs!

See also:

https://forums.ni.com/t5/DQMH-Consortium-Toolkits/my-DQMH-PPL-and-VILIB-PPL-best-practices/td-p/4155...

Greetings

Claude

[ben64]

Thanks Christopher and Claude,

I ran the validation tool and found minor issues an unrelated module (non-reentrant subVIs in clonable module) but there were no issues found in the module I'm trying to build an executable.

Claude, I will take a look at the post you linked. Note that the PPL used only includes interface VIs, so basically just connectors on front panel, no subVIs.

There is no issues running the code in the development environment (LV2019, DQMH 5)

Ben

[ben64]

Finally got it to work by following Claude best practices (follow the link in his post). Disconnect dependant packed libraries, Enable debugging and recompile did the trick.

Thank you all.

Ben

edit: Building DQMH executable would be a nice presentation subject!

[ChrisFarmerWIS]

That is great to hear Claude's best practises post has already provided value to the community!

[Cloedu72]

Glad to hear it is working for you. My best practices list is not complete yet, there are still some issues I can't explain yet. PPL are still the way to go though!

=> It is annoying that we have to create the PPL for the NI libraries (VILIB) ourselves.