DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

How does the "Convert DQMH Event" tool work?

Solved!
Go to solution

From the name and what I observe, I assume it works in a way that allows me to select any event from my module and change its type to any other type. However, based on the list of available requests, it seems that I can only convert events into the "Request and Wait for Reply" type, or there is some filter limiting the visibility of other events. Generally, in the list of events available for conversion (dropdown list #2), not all events are listed, and in dropdown list #3, I can only choose one specific type to convert to.

 

How should it actually work?

 

 

bienieck_0-1732788814904.png

 

Michał Bieńkowski
CLA, CTA, CPI

  1. Did someone devote their time to help solve your problem? Appreciate it and give kudos.
  2. Problem solved? Accept as a solution so that others can find it faster in the future.
  3. Contribute to the development of TestStand by voting on the TestStand Idea Exchange.
0 Kudos
Message 1 of 4
(166 Views)
Solution
Accepted by bienieck

You can only convert from a Request to a Request and Wait for Reply event.

 

Ozfarmboy_0-1732830055548.png

 

Converting an Existing DQMH Event :: DQMH Consortium Docs

 

 

Christopher Farmer

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

0 Kudos
Message 2 of 4
(140 Views)

That's a pity 😔

Michał Bieńkowski
CLA, CTA, CPI

  1. Did someone devote their time to help solve your problem? Appreciate it and give kudos.
  2. Problem solved? Accept as a solution so that others can find it faster in the future.
  3. Contribute to the development of TestStand by voting on the TestStand Idea Exchange.
0 Kudos
Message 3 of 4
(127 Views)

Some improvements will be in DQMH 7.1 --> https://documentation.dqmh.org/dqmh/7.1/ConvertinganExistingDQMHEvent.html


Olivier Jourdan

Wovalab founder | DQMH Consortium board member | LinkedIn |

Stop writing your LabVIEW code documentation, use Antidoc!
0 Kudos
Message 4 of 4
(112 Views)