Module Elements

Follow these guidelines when working with a DQMH library to ensure full compatibility with the DQMH Scripting Tools:

  1. Do not rename or remove any DQMH-specific files within the module .lvlib.

  2. Do not move any DQMH-specific files on disk. All VIs and typedefs that are part of the template DQMH code should remain in a flat folder structure along with the DQMH module .lvlib, with the exception of various sub-libraries (Clone Registration and VI Reference Management, for example), which should remain in their own subfolders without modification.

  3. Do not move any DQMH-specific files within the module .lvlib in the LabVIEW project window. The existing virtual folder structure within the module .lvlib is required in order for the DQMH scripting tools to work properly. You can create your own virtual folders within the module library in which to store VIs and typedefs related to the business logic of your module.

Minimum Requirements for Scripting Tools

The DQMH scripting tools require several elements to be present in order for an .lvlib to be properly identified as a DQMH Module. Those elements are:

  1. Public API > Requests folder

  2. Public API > Arguments > Request folder

  3. Public API > Arguments > Broadcast folder

  4. Broadcasts folder

  5. Obtain Broadcast

  6. Destroy Broadcast

  7. Obtain Request

  8. Destroy Request

  9. Request Events-–cluster.ctl

  10. Broadcast Events-–cluster.ctl

  11. Module Timeout-–

  12. Module Name-–

  13. Status

  14. Module Not Running-–

  15. Multiple Instances folder (Cloneable modules only)

If any of the items in this list have been moved, removed, or renamed, the DQMH scripting tools will not identify the library as a DQMH module and you will not be able to use those tools.