FSM

[Scarr]

Hi,

Is this the right place to ask about FSM's and state tables (I know its not a labview diag but I have had no joy on other forums and daw a few posts on here about them)? I am new to FSM's and have done my first diagram and table (attached), just wanted some advice on if I have made any realy booboo's

If you look at the diag, I have a state called "monitor" this is the main state that siits there and checks things like temp / timeout / vend, if this the correct way to do a FSM diag or should I have tests (temp / timeout / vend) is seperate states?

Also am I correct in having things like "change temps" as a state when really it just changes the temp and returns so it is not a "change temps" state for very long.

Thanks

Steve

[David. B]

Hi Steve,

Thank you for contacting joining the forum.

There is no real right and wrong way to create the diagram. The diagram is easily readable and it can be seen what you wish to do so from that point of view it is fine but the main thing is that you understand it and can see how it works clearly. It is slightly strange that you do not have a 'Shutdown' state after the 'Display Fault' state and this may be something that you would like to consider. I am presuming that you are eventually looking to program this application in LabVIEW and I think that you'll find some of the State Machine Example Architectures found within the NI Example Finder.

I wish you all the best of luck with your project and am happy to answer any more questions you may have.

Kind Regards