NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

How to use cloneable DQMH modules in TestStand

Solved!
Go to solution

Hi everyone,

I’m working on a TestStand sequence that needs to exchange messages over multiple serial ports. To handle this, I’m using a cloneable DQMH module that manages the ports.

When running the sequence in TestStand, I encounter the following issue: if I invoke the module’s Start Module request (or a VI that calls Start Module + Synchronize Module Events, similar to the DQMH tester), the module doesn’t start correctly. Any subsequent request sent to that specific Module ID throws an error and the sequence halts.

Important details:

  • The same DQMH module works perfectly when run stand-alone — tested multiple times using the auto-generated DQMH tester.

  • Issue occurs only when the module is started from TestStand.

  • LabVIEW 2021

  • TestStand 2020

  • Latest DQMH version installed

  • Windows 10 PC

  • TestStand LabVIEW adapter is set to “LabVIEW Runtime Engine 2021” (I’m aware running in the Development Environment can change behavior).

Implementation approach:

  • In TestStand, I’m calling the DQMH-generated request VIs directly (just as I would in a normal LabVIEW block diagram).

  • These VIs are referenced directly from the LabVIEW project containing the module.

It seems like the module doesn’t actually initialize in the TestStand context, even though the same code works outside of it. Is there anything specific I should be aware of when starting a cloneable DQMH module from TestStand using the Runtime Engine?

Thanks in advance for any guidance!

0 Kudos
Message 1 of 4
(332 Views)

Which process model are you using?

 

Have you tried calling the VIs without the LabVIEW Project Context?

0 Kudos
Message 2 of 4
(305 Views)
Solution
Accepted by cpiccoli

Hello,

 

I never used it (yet!) but I heard about a package that helps making a DQMH module easy to use from TestStand : TestStandifier for DQMH by Neosoft Technologies

 

I guess it may address some of the problematics you are facing, especially clone ID vs. test socket index handling.

You can find a presentation made at NI Connect here.

 

Hope this may help.

Message 3 of 4
(284 Views)

Not sure if this will solve your issue, but have you looked at the DQMH TestStand examples that are shipped with DQMH?

 

TestStand Example 3: Thermal Chamber Controller Example With Multiple DUTs.seq :: DQMH Consortium Do...

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

Message 4 of 4
(247 Views)