01-22-2010 11:12 PM
Hi Jarrod,
I guess the QSM was close to the solution that I wanted. As you already mentioned the Finite State Machine failed badly when it had to handle a parallel input that called for a State outside the ordered states. In other words it was poor in handling interrupts. And to me this looked a severe limitation when doing machine coding as I also do embedded coding for 8 bit microcontrollers. These small 8 bit devils are great when it comes to handling interrupts. And whats more you could even prioritize 12 or more interrupts to tell which will supersede which !
I am just starting to grasp the contents of the links that you had sent and it appeasr that I will have a solution albeit a little bit more complex than the simple SM. But then in life there is no such thing as a free lunch
01-24-2010 06:14 AM
Hi Jarrod,
I went through the links and should say that the Queued State Machine addresses all my concerns. The JKI template is a nice one if I were passing data along with the commands. But since I don't need that functionality I designed my own template creating the required parallel inputs for items like Interlock failure and Start commands.
The basic design is attached for your comments and to check possible traps if any.. ( It is done in LV2009 )
Thanks