Queued State Machine QSM - LabVIEW Design Patterns

[@sunilsgowda210]

Thanks for the video nice explanation

[@armanmanukyan1970]

Why does't we use shift register for dequeuing the next state during the next iteration? Thanks.

[@LabVIEWADVANTAGE]

This is an alternative to SME. There is another video with shift register. Both are same

[@matussedivy4372]

@@LabVIEWADVANTAGE They are not the same, but result is the same or rather similar. Presented QSM has infinite timeout, which means, that if programmer forget to enqueue next state, whole program will freeze. User can try to click on anything, but it will not work. In case of using a shift register, programmer is forced to put something there. The event structure usually placed in "idle state" can prevent from pooling, because it is waiting for event and has timeout functionality as well.

[@bhuvanachandrana5671]

Is there any benefit of using queued state machine rather than using a event driven state machine? because both don't require wait function

[@LabVIEWADVANTAGE]

Queues SM are scalable, they can communicate easily with other loops

[@sunilsgowda210]

In how many ways state machine can be used in LabVIEW Is there specific methods and architecture for state machine

[@usmanasghar2567]

Why queue is used? we can also achieve the state machine functionality without queue as well. Thank you 🙂

[@LabVIEWADVANTAGE]

Classic SM requires delay, this one does not by default

[@usmanasghar2567]

If i understood you correctly, you are referring to the delay inside the main while loop;the delay which prevents the VI from excessive CPU usage? So, if i use the state machine with queue i need not to place the delay inside the main while loop? Is this the rigth interpretation. Thanks a lot. Keep up the good work

[@chandrakanth9552]

What's the advantage of queued state Machine over Normal state Machine....!!

[@LabVIEWADVANTAGE]

Normal state machine polls all the time while QSM does not need to poll