DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Problems running executable with DQMH made into PPL

I did what Brett_Percy advised but you still have an issue.

 

I create a new blank project and add the two PPLs.

  • Main module vi is not broken
  • But you some strange unloaded VI's in the dependencies (that have no callers)

Olivier-JOURDAN_0-1622621574510.png

 

 

If I run the main VI, it becomes broken.

 

Olivier-JOURDAN_1-1622621615346.png

 

I think that the 4 vi's listed in the dependencies are called in diagram disable structure in your common PPL. If it's the case remove them and rebuild your common PPL.


Olivier Jourdan

Wovalab founder | DQMH Consortium board member | LinkedIn

Stop writing your LabVIEW code documentation, use Antidoc!
0 Kudos
Message 11 of 15
(1,945 Views)

Claude suggested solution in another thread: https://forums.ni.com/t5/DQMH-Consortium-Toolkits/Trouble-with-DQMH-module-using-OPC-UA-in-a-packed-...

Everything is working like it should now !!!

 

Thanks.

Message 12 of 15
(1,927 Views)

I guess it would be worth starting a new post (sticked?) on DQMH-PPL best practices. My style guide list for PPL is getting longer and longer but it is still worth to work with PPL!

Claude

CLA / CTD
Message 13 of 15
(1,901 Views)

That would be super useful I think

 

Cheers

Brett

Senior Software Development Engineer
Certified LabVIEW Architect and LabVIEW Champion
https://theLonelyAnt.com
https://GDevConANZ.org.au


0 Kudos
Message 14 of 15
(1,895 Views)

If any of you wants to provide the content, I'll happily create the thread and set it to sticky.




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )


Message 15 of 15
(1,883 Views)