Prev: NI PCI-1588 Windows XP Accurate Timing Device
Next: pulse oximeter
From: smercurio_fc on 6 May 2008 11:40
In that case, I would strongly suggest using a different design paradigm, such as a state machine. Your implementation is confusing and prone to errors (as you've already experienced), not to mention difficult to change.
From: exo on 6 May 2008 12:10
I looked up a state machine. There seems to be a lack of documentation. This seems to be the extent of it. Standard State Machine?Use this template to build a standard state machine design pattern. Each state executes code and determines which state to transition to. Contrast this design pattern with the user interface event pattern, in which code executes in response to user actions. Contrast this design pattern also with the queued message handler pattern, in which each message handling code can queue any number of messages.The code needs to execute user actions as well as a portion in the example
From: craigc on 6 May 2008 12:10
State Machines are used in all types of Design, Software and Hardware (FPGA's ASIC's etc).  Would probably be worth looking outside of the LabVIEW community for a more general Introduction to them.  There are different variations on them too (Moore / Mealy / Queed).  However i have found them an Invaluable tool in Engineering and they are not too difficult to get your head round.
Craig
btw i have no idea how to spell Quee'd !
First  |  Prev  | 
Pages: 1 2
Prev: NI PCI-1588 Windows XP Accurate Timing Device
Next: pulse oximeter