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!
