StateMachine coding method

[MogaRaghu]

This is a kind of general question to understand the methods that different programmers  follow.

While coding for statemachines - say to run an Auto cycle of a mchine - one needs to keep track of the various things  : The state of each I/O that is involved; the statemachine state number jumps ; delay routines ... the list is endless. So when coding and wiring it on the PC, is there any specific method that can reduce the number of trial runs that one needs to take on the machine.  I can think of the following :

1. Prepare a general "method" flowchart telling the sequence flow and  then convert it to LV code .
2. Prepare a detailed flow chart with the actual I/O list and inlcudng the proposed states.
3. Use a spread sheet kind of  paper with States in the  row field and I/Os in the column field. Keep ticking each row as the coding progresses.
4. Have it in mind and code. You can always check on the machine with break points set .

As to me I have tried all of the above - but still not reached anywhere.  A combinatrion of 1 and 4 is normally what I end up doing.

I would welcome any ideas from fellow members to improve upon this.

Thanks

raghunathan

[Khalid]

Hi Raghunathan,

There's another option to add to your poll -- the State Diagram Toolkit from NI. 

Ideally, I personally would follow option #2  (and never option #4 by itself).

-Khalid

Message Edited by Khalid on 10-23-2005 08:11 AM