DQMH Queued Message Handler

The Future of Team-Based LabVIEW Development

User Tools

Site Tools


dqmh:release-notes:dqmh_6.1

This is an old revision of the document!


DQMH 6.1

January 2022

Package Versions (DQMH 6.1)

  • Delacor QMH 6.1.0.88
  • Delacor QMH Palette 6.1.0.16
  • Delacor QMH Project Template 6.1.0.93
  • Delacor QMH Event Scripter 6.1.0.126
  • Delacor QMH Thermal Chamber Example 6.1.0.50

This is the first DQMH release that drops support for LabVIEW 2014.

Major new features

  • #744 Validate tests for broken VIs. Return a validate failure if the Main VI and/or Tester VI for a module are broken.
  • #733 More custom fields in Module Template. When creating a DQMH Module Template, the user can now specify default values for Tester virtual folder, Module virtual folder, and relative path location for the new module. Then, whenever that template is used in the New DQMH Module dialog, those fields are pre-populated with the values from the module template and can be changed by the user. The last used virtual folder for tester, virtual folder for module, and relative path on disk for module are stored in the LabVIEW INI file. These will then be used when creating the next module with the Add New Module UI. Additionally, there is now a 'Reset path and folder fields to default' button in the UI so the user can see what the default paths for different module types are if he doesn't want to use his last-used path.
  • #734 New Scripting API for DQMH. VIs currently implemented are:
    • Get all modules in a project
    • Get all events in a module library
    • Get all callers of a request VI in the project
    • Get all VIs registered for a broadcast in the project
  • #735 Quick Drop plugin for calling DQMH tools. The Ctrl-E quick drop shortcut will now launch all DQMH scripting tools. Read the description of the plugin (Quick Drop > Configure > Ctrl-Key Shortcuts > Launch DQMH Tool) to see the commands for launching each tool.
  • #732 Ignore individual validation results. The Validation Results UI now allows you to right-click any validation failure and choose to ignore it for future validation runs. There is also a button in the results UI that lets you manage the validation failures for your modules. Note that this information is currently stored in a (human-readable) tag in the module .lvlib XML. The headless validator will fire a Validation Finished event even if the validation didn't start due to an error. Validation tests that can flag individual VIs will check for the Issue Text in the VI description and if so, will not return a failure.
  • #729 New 'Show Diagram on Init' data member All our shipping modules (Project Template, CML Template, Module Template, and shipping example) have been updated to have a new 'show main VI diagram on init' checkbox on their testers. This parameter is wired to the “Start Module” VI for those modules and implements the new functionality where, on startup, the module main VI diagram is displayed and Retain Wire Values is enabled. A validate+fixer has been added to update old modules to include this new functionality.
  • #737 New progress VI for headless validation. The 'Obtain Progress Events.vi' will be on the DQMH Scripting palette and will allow the user to monitor the progress of a headless validation via events.
  • #741 Rename 'Delacor' menu to 'DQMH Consortium'. Rename the Tools > Delacor menu to Tools > DQMH Consortium.

DQMH Palette

  • #734 New Scripting API for DQMH. VIs currently implemented are:
    • Get all modules in a project
    • Get all events in a module library
    • Get all callers of a request VI in the project
    • Get all VIs registered for a broadcast in the project
  • #735 Quick Drop plugin for calling DQMH tools. The Ctrl-E quick drop shortcut will now launch all DQMH scripting tools. Read the description of the plugin (Quick Drop > Configure > Ctrl-Key Shortcuts > Launch DQMH Tool) to see the commands for launching each tool.
  • #729 New 'Show Diagram on Init' data member All our shipping modules (Project Template, CML Template, Module Template, and shipping example) have been updated to have a new 'show main VI diagram on init' checkbox on their testers. This parameter is wired to the “Start Module” VI for those modules and implements the new functionality where, on startup, the module main VI diagram is displayed and Retain Wire Values is enabled. A validate+fixer has been added to update old modules to include this new functionality.
  • #737 New progress VI for headless validation. The 'Obtain Progress Events.vi' will be on the DQMH Scripting palette and will allow the user to monitor the progress of a headless validation via events.
  • #723 About VI. There is now an 'About DQMH' VI in the DQMH palette. The Project Template, CML Template, Module Template, and Shipping Example have all been updated with a button in various UIs to launch the About box.

Module Template

  • #733 More custom fields in Module Template. When creating a DQMH Module Template, the user can now specify default values for Tester virtual folder, Module virtual folder, and relative path location for the new module. Then, whenever that template is used in the New DQMH Module dialog, those fields are pre-populated with the values from the module template and can be changed by the user. The last used virtual folder for tester, virtual folder for module, and relative path on disk for module are stored in the LabVIEW INI file. These will then be used when creating the next module with the Add New Module UI. Additionally, there is now a 'Reset path and folder fields to default' button in the UI so the user can see what the default paths for different module types are if he doesn't want to use his last-used path.

DQMH Scripter

  • #747 Don't list modules with RT testers already. When running the Create RT Tester utility, don't list modules in the module list that already have an RT tester.
  • #728 Module description field. When running the Create New Module utility, there is now an optional description field for specifying a module description (which will populate the Description field of the module library file).
  • #748 Improve scripting for 'event only' modules. The New Event scripting tool now works properly for scripting the new event in the main VI even if the EHL does not have a Delacor Message Queue tunnel input
  • #734 New Scripting API for DQMH. VIs currently implemented are:
    • Get all modules in a project
    • Get all events in a module library
    • Get all callers of a request VI in the project
    • Get all VIs registered for a broadcast in the project
  • #722 Don't try to parse PPLs. When parsing the project to find DQMH modules, ignore modules inside PPLs (as they can't be modified or inspected with our scripting tools).
  • #727 Remove extraneous text from error labels. Renamed the Reply Payload error cluster to just “error” instead of “[request name] error”. Updated the scripting code to create new reply payload error clusters with the simple label “error”.
  • #746 Improve Error Reported error reporting. Improved the code in the Error Reported broadcast of the tester VIs to return more useful error information. This change was made to the testers in the module template, project template, and CML template. There is also a validate+fixer to fix the issue in the existing code.
  • #749 New Null Broadcast Events--constant VI. Added the new 'Null Broadcast Events–constant.vi' to all template DQMH modules. Also added a new validate+fixer to add this VI to old modules that don't have it.
  • #741 Rename 'Delacor' menu to 'DQMH Consortium'. Rename the Tools > Delacor menu to Tools > DQMH Consortium.

DQMH Validation Tool

  • #744 Validate tests for broken VIs. Return a validate failure if the Main VI and/or Tester VI for a module are broken.
  • #745 Wired Start Async Call output. New validate module test that returns a failure if the user has wired the VI Reference output of the Start Asynchronous Call function in the Start Module VI of a cloneable module.
  • #743 Improve namespace handling in timeout fixer. The fixer that adds the Timeout Error subVI to a Request and Wait for Reply VI now does a better job with only parsing VIs that are directly part of the module namespace (and ignores sublibraries that may have identically-named VIs)
  • #732 Ignore individual validation results. The Validation Results UI now allows you to right-click any validation failure and choose to ignore it for future validation runs. There is also a button in the results UI that lets you manage the validation failures for your modules. Note that this information is currently stored in a (human-readable) tag in the module .lvlib XML. The headless validator will fire a Validation Finished event even if the validation didn't start due to an error. Validation tests that can flag individual VIs will check for the Issue Text in the VI description and if so, will not return a failure.
  • #746 Improve Error Reported error reporting. Improved the code in the Error Reported broadcast of the tester VIs to return more useful error information. This change was made to the testers in the module template, project template, and CML template. There is also a validate+fixer to fix the issue in the existing code.
  • #749 New Null Broadcast Events--constant VI. Added the new 'Null Broadcast Events–constant.vi' to all template DQMH modules. Also added a new validate+fixer to add this VI to old modules that don't have it.
  • #752 Validate+fixer for Stop Module event ordering. The new fixer will update the Wait on Stop Sync VI to use the new mechanism to register for Module Did Stop before firing the Stop Module event. The fixer also fixes up the two callers of Wait on Stop Sync (Stop Module.vi and Close Module.vi).
  • #752 Add semaphores to singleton modules. Project Template, CML Template, and Module Template updated to include semaphore synchronization in all their semaphore modules. There is also a validate+fixer to detect this issue in older modules and update them.
  • #729 New 'Show Diagram on Init' data member All our shipping modules (Project Template, CML Template, Module Template, and shipping example) have been updated to have a new 'show main VI diagram on init' checkbox on their testers. This parameter is wired to the “Start Module” VI for those modules and implements the new functionality where, on startup, the module main VI diagram is displayed and Retain Wire Values is enabled. A validate+fixer has been added to update old modules to include this new functionality.
  • #737 New progress VI for headless validation. The 'Obtain Progress Events.vi' will be on the DQMH Scripting palette and will allow the user to monitor the progress of a headless validation via events.

DQMH Thermal Chamber Examples

  • #752 Add semaphores to singleton modules. Project Template, CML Template, and Module Template updated to include semaphore synchronization in all their semaphore modules. There is also a validate+fixer to detect this issue in older modules and update them.
  • #729 New 'Show Diagram on Init' data member All our shipping modules (Project Template, CML Template, Module Template, and shipping example) have been updated to have a new 'show main VI diagram on init' checkbox on their testers. This parameter is wired to the “Start Module” VI for those modules and implements the new functionality where, on startup, the module main VI diagram is displayed and Retain Wire Values is enabled. A validate+fixer has been added to update old modules to include this new functionality.
  • #723 About VI. There is now an 'About DQMH' VI in the DQMH palette. The Project Template, CML Template, Module Template, and Shipping Example have all been updated with a button in various UIs to launch the About box.

DQMH CML Project Template

  • #752 Add semaphores to singleton modules. Project Template, CML Template, and Module Template updated to include semaphore synchronization in all their semaphore modules. There is also a validate+fixer to detect this issue in older modules and update them.
  • #729 New 'Show Diagram on Init' data member All our shipping modules (Project Template, CML Template, Module Template, and shipping example) have been updated to have a new 'show main VI diagram on init' checkbox on their testers. This parameter is wired to the “Start Module” VI for those modules and implements the new functionality where, on startup, the module main VI diagram is displayed and Retain Wire Values is enabled. A validate+fixer has been added to update old modules to include this new functionality.
  • #723 About VI. There is now an 'About DQMH' VI in the DQMH palette. The Project Template, CML Template, Module Template, and Shipping Example have all been updated with a button in various UIs to launch the About box.

Help

  • Updated link to obtain DQMH Framework Badge
  • Replaced all the instructions to go to Tools>Delacor> to Tools>DQMH Consortium>DQMH to use DQMH Toolkit
  • Updated video link to Validating an Existing DQMH Module that shows the new features for DQMH 6.1 and how to validate an existing DQMH 6.0 project to match DQMH 6.1
  • Updated New Module Dialog Image showing the new fields on DQMH 6.1 release.
  • Added Using Quick Drop Section.
  • Added “DQMH New… Menu” to the list of Third Party Products
  • Updated DQMH in LabVIEW Real-Time section
  • Updated URLs from delacor.com to the equivalent content on dqmh.org
  • Changed the footer to have clickable text elements instead of showing URLs
  • Updated Release Notes URLs in What is New in DQMH? section
  • Added link to https://dqmh.org/training from How to Learn DQMH section
  • Removed build number from DQMH Versions 4.0 and greater in the Change History section
  • Published documentation at https://documentation.dqmh.org
/home/dqmh/www/wiki/data/attic/dqmh/release-notes/dqmh_6.1.1645197803.txt.gz · Last modified: 2022/02/18 10:23 by matthiasbaudot

Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
Public Domain Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki