DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Announcing DQMH 5.0

Hello DQMHers (still looking for a good name;) ), 

 

We have been busy implementing several of the requests you have sent to us either by direct contact or via this DQMH forum. We also continue to eat our own dog food as we use DQMH in our own internal projects. We have been using DQMH 5.0 internally for a while and even shared the Beta version with some of you already. If you have the LabVIEW Graphical Programming 5th edition book, you probably noticed that the chapter on Frameworks already had pictures of DQMH 5.0. The feedback from our Beta testers has made DQMH 5.0 even better and ensures that we continue to honor the quest for the best Developer Experience (DX). By the way, thanks for the 200+ downloads of the DQMH 5.0 beta!

 

We believe DQMH 5.0 is the best version yet!

 

Keep the feedback coming, and you can always add your DQMH feature request via the DQMH feature requests document on this DQMH forum.

Main new features:

  1. Singleton and Cloneable Module templates updated to use Start Async Call instead of Run VI method for launching Main VI. More details at the bottom of this documentation page
  2. Added support for scripting an RT tester for Singleton modules (DQMH 4.2 only supported LabVIEW Real-Time for Cloneable modules). DQMH 5.0 supports all DQMH modules in LabVIEW Real-Time
  3. DQMH Validate Tool improvements
    1. Prompt the user to run the validate module tool after upgrading DQMH via VIPM
    2. Added the ability to validate all modules in the project. We also added a VI (Validate DQMH Module (Headless).vi) that you can pass in a project path and it will programmatically validate all modules in the project and return a result. This VI could be used as part of a CI/CD process to validate DQMH modules
    3. Added a button to the Validation Results UI that allows you to analyze another module after you are done viewing the results for the current module. We also added a button to the ‘all tests passed’ dialog to allow you to validate another module as well
  4. Improved API Tester developer experience: The API Tester does not stop the module on exit if it was already running when the API Tester started running. This is useful when using the API Tester as a sniffer
  5. Request and Wait for Reply now returns an error if the reply times-out –> as requested here
  6. If your custom DQMH template requires a different enqueue (for example for a DQMH Queue child or if the DQMH libraries were built into a PPL), we added the ability to specify a custom enqueue message VI to be scripted into the MHL when creating request events Singleton and Cloneable Module templates updated to use Start Async Call instead of Run VI method for launching Main VI

The online documentation now includes a section on What is New in DQMH

You can find the complete release notes here

Download DQMH 5.0 via VIPM or the LabVIEW Tools Network. Watch this video for a quick tour of the changes and how to upgrade your existing DQMH modules to 5.0.

 

 

Thanks again for your trust in DQMH and in our team!

 

Happy wiring!

Fab and the Delacor Team

For an opportunity to learn from experienced developers / entrepeneurs (Steve, Joerg, and Brian amongst them):
Check out DSH Pragmatic Software Development Workshop!

DQMH Lead Architect * DQMH Trusted Advisor * Certified LabVIEW Architect * Certified LabVIEW Embedded Developer * Certified Professional Instructor * LabVIEW Champion * Code Janitor

Have you been nice to future you?
Message 1 of 4
(3,308 Views)

@FabiolaDelaCueva wrote:

Hello DQMHers (still looking for a good name;) ), 

 

 



May be the DQers?

Sam Taggart
CLA, CPI, CTD, LabVIEW Champion
DQMH Trusted Advisor
Read about my thoughts on Software Development at sasworkshops.com/blog
GCentral
0 Kudos
Message 2 of 4
(3,257 Views)

@Taggart wrote:

@FabiolaDelaCueva wrote:

Hello DQMHers (still looking for a good name;) ), 

 



May be the DQers?


Legends?

 

Hey Fab,

I've been using v5 and it's all going well.

 

The only tiny issue I've found is that the validator doesn't copy Master Reference Not Closed--error.vi if the validator can't update Start Module.vi. Not much of an issue - and it's not one I'll have again as I've updated all my templates, but it would be a 'quick-win' for your next patch.

Message 3 of 4
(3,007 Views)

Thanks for the heads up. 

 

I have been removing the extra inputs I had added to my Start Module.vi and let the fixer fix my start module,  then I go back and add the inputs. 

 

I will create a case to look into this for the next release. 

 

Thanks, 

Fab

For an opportunity to learn from experienced developers / entrepeneurs (Steve, Joerg, and Brian amongst them):
Check out DSH Pragmatic Software Development Workshop!

DQMH Lead Architect * DQMH Trusted Advisor * Certified LabVIEW Architect * Certified LabVIEW Embedded Developer * Certified Professional Instructor * LabVIEW Champion * Code Janitor

Have you been nice to future you?
0 Kudos
Message 4 of 4
(2,991 Views)