 | | Implementing Finite State Machines
|
|
Hi all! I have been struggling with a fairly large FSM implementation in NQC and came to realize that maybe most of the more advanced NQC applications might be actually FSMs (or could become)... Because I think it is a little awkward to handle a FSM (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Implementing Finite State Machines
|
|
Vlad, The Finite State Machine is a good subject for people to consider in robotics, especially in coding the typical 'looping forever' Rcx applications. Lots of regular 'C' FSM's are implemented with a State variable and "switch" statements, or (...) (25 years ago, 11-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Implementing Finite State Machines
|
|
(...) Adding a switch statement to NQC would certainly help make implementation easier...I'll see if I can work it into the next release. Actually, I've been somewhat surprised by the general lack of needing FSMs in my own Mindstorms programming. I (...) (25 years ago, 11-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Implementing Finite State Machines
|
|
(...) [snip] (...) FSMs are a boon in our behavioural robotics projects. If you have read the Rod Brooks papers, he uses them to implement subsumptive architectures in his "radical" robots. I have used them a LOT in my Stamp II robots as the only (...) (25 years ago, 11-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Implementing Finite State Machines
|
|
Dave, I like the idea of teaching how to solve certain problems both with multiple threads and with a Finite State Machine. Adding "switch" would be great! Personally I think that a plain 'C' FSM using switch can be made to look very clear if (...) (25 years ago, 12-Dec-99, to lugnet.robotics.rcx.nqc)
|
