Designing a DQMH-based Sequencer

[Tenru]

Hi Delacor team!

I’m building a LabVIEW application using the DQMH framework. The app acquires data (NI-DAQmx, VISA, TCP/IP) and controls power supplies and relays via the same protocols. I’m now working on the Sequencer module.

In the legacy app, each operation was an element of an array of clusters with: operation duration, setpoints (currents/voltages, relay on/off), transition conditions, monitored parameters with limits, repeat count, and a “goto line N”. This became hard to read and extend. For example, current was set in the step, while voltage/power were global pre-run limiters only. I’d appreciate advice on how to design the new sequencer algorithm.

I also need cyclic execution of step groups. Example: there are 36 steps in total; run steps 0–5 three times; then run steps 0–12 twice; then execute the remaining steps (12–36).

I’d appreciate guidance on:

1. Step data model.

2. Conditional transitions: best practices for “if parameter X goes out of limits → turn off relays/PSU or jump to step Y”.

3. Existing examples: open DQMH-based “sequencer” examples (UI + engine). When would NI TestStand be a better fit?

4. Storage: preferred profile format (CSV/JSON/XML).

5. Safety/interlocks: where to keep global limits, and how to implement atomic PSU+relay shutdown on out-of-limit conditions.

Old sequencer: