stacked sequence

[Chazzzmd]

Greetings,

I have a test script that operates 3 axis. It's intended purpose is for RF measurement. Basically there is azimuth rotation, azimuth roll, and source roll. I've gotten most of it done, but am finding difficulty in correct sequence execution of the code.

Goal:
1. All 3 axis go to start position
2. azimuth roll rotates as needed (measured during each step angle)
3. source roll rotates to next angle
    REPEAT STEPS 2 & 3 UNTIL SOURCE ROLL REACHES STOP ANGLE
4. azimuth rotation moves to next angle
    REPEAT STEPS 2 & 3 UNTIL SOURCE ROLL REACHES STOP ANGLE

    REPEAT STEPS 2, 3, & 4 UNTIL AZIMUTH ROTATION REACHES STOP ANGLE

Is there an example that somebody knows of to paint me a picture? Any help would be greatly appreciated.

Thanks in advance,

Chazzzmd

   

[falkpl]

Look at a state machine or wueued state machine architecture instead of a sequence much more flexable.

[smercurio_fc]

See Application Design Patterns: State Machine.

[Chazzzmd]

Hey Guys,

Thanks for the information. I had been studying up a little on state machines (it didn't really stick after NI classes) and found it was very easy to make the necessary changes. I've made all the necessary changes and will be doing a dry run later today.

Thanks again for your help, and confirming my thought process of the state machine.

Can you confirm 1 thing? Each Enum constant variable I inputted has a numeric value (0-9). As long as after my transition code in each case,  it's a numeric value it should go to the correct corresponding case?

Thanks in advance.

Chazzzmd

[JeffOverton]

The enum is manipulated like an integer, yes.  I would recommend making your enum case selector into a strict type def, that way wiring errors (probably) won't get you into an undefined state.  Plus, then you can use the super-handy "add case for every value" to make sure you didn't forget any.  Also, you can then add or delete states and automatically propagate your changes through the state machine.