A description of how to get started with DQMH can be found on the video "DQMH Getting Started" found at: bit.ly/DelacorQMH

The video is embedded below, followed by a description of what can be seen at different times in the video:

Getting Started with DQMH video

This video shows where to find the documentation for the Delacor Queued Message Handler toolkit, how to create a project from the template and where to find the shipping examples. The video explains what a Singleton vs Cloneable module is and how to run the testers and the individual modules.

0:00 Where to find Documentation

0:30 Create a DQMH from Project Template

1:20 Add a new DQMH Module to an existing project

1:40 Where to find the DQMH shipping examples

2:05 DQMH Project Template structure

3:40 Nomenclature: Request, Broadcast events and DQMH Module design pattern

5:12 DQMH as a stand alone module or part of a larger application

5:28 Steps to add a new DQMH Module

6:43 Module structure

8:30 Request event

8:58 Broadcast event

16:56 Shipping examples: Simple VIs calling DQMH public API (singleton)

19:50 Shipping examples: Thermal chamber with DUT (singleton & cloneable)

20:25 Shipping examples: Thermal Chamber with Multiple DUTs (singleton & cloneables)

21:30 Cloneable DQMH Module

24:20 How to create a DQMH Event

31:18 API tester tests errors when module is not running

An application that uses the DQMH will have one or more DQMH modules. Each DQMH module will have a Main.vi that is a version of the Producer/Consumer design pattern, where the user interface (producer) produces messages and the tasks (consumers) consume them. However, in the DQMH template, you can also produce messages from other DQMH modules or other VIs.

This template includes the following:

  • 1 singleton DQMH module (can have only one instance of its Main.vi running at any given time)
  • 1 cloneable DQMH module (can have one or multiple instances of its Main.vi running in parallel)
  • 2 API testers, one for each DQMH module
  • 1 sample application implemented using a State Machine to show that the code that calls a DQMH module does not have to be a DQMH module itself.

If you would like to add modules to an existing project, then use the Tools>DQMH Consortium>Add DQMH Module utility in your existing project.