State machine architecture in VS?

[Lysandros]

Recently I started migrating with a HiL-Project from Labview onto Veristand. Deployment of a first simplistic Veristand project for interfacing with Hardware works fine.

But how about a state machine architecture in Veristand...In Labview one can use hardware/software conditions for transitioning from one operating state (e.g. "Test" or "Initialization") to another (e.g. "Running"). And in each state variables can be set for the GUI (e.g. a string indicator showing the active state name)...but how is this logic implemented here? Are the Procedures the answer or do I need to import VI's from Labview somehow?

Thanks in advance

[Lysandros]

After finding out that, yes, Procedures allow for a state machine architecture 🙂 How can I monitor in runtime, which procedure is active at a given time?

BEst wishes

[okubik · Accepted solution]

Hi,

I would keep procedures as simple as possible as they might became hard go maintain for more complex logic. Instead I would think of incorporating your decision-making logic in the stimulus profile respectively in the real-time sequence.

If you would need more complex state machine, you can also consider to implement it as LabVIEW model and compile it for NI VeriStand.