global stop

[cedhoc]

Hi asnaev,

Given the sequence of actions you have to execute, it seems like the State Machine architecture is well suited here.

If you are new to LabVEW, this is also an architecture which is good to learn given its popularity and so you will encouter it a lot here and there.

The good point with the State Machine is that it is quite easy to implement if the specification of your application is well defined beforehand, which is actually true for every software design. But this is particularly true here thanks to the State Transition Diagram that you will first draw on a piece of paper. If this diagram is properly build, then implementing the LabVIEW code will be much easier.

There is a lot of info available about the State Machine in LabVIEW. To give you just a few links:

Tutorial: Simple State Machine Template Documentation --> http://www.ni.com/white-paper/14120/en

Tutorial: Using a State Machine architecture --> http://www.ni.com/white-paper/2926/en

Example: Simple intruder alarm log --> https://decibel.ni.com/content/docs/DOC-22972

Example: Flexible DAQmx State machine for Automated test --> https://decibel.ni.com/content/docs/DOC-10862

Regards,

[asnaev]

Ok. just one question. Can the state machine be autonomous enougth to select the right process? u were right i need something more organized because the flat sequence is not serving my purpose. The general idea is to run the program and sit back and relax untill its over 😄 not worring with anything.

[cedhoc]

I am not sure what you mean by "select the right process", but if your goal is to execute the different actions you explain previously in a sequential way, then yes, the Sate Machine for sure will let you do that. 

That is what we call automation 🙂