 | | 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
|
|
(...) 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
|
|
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: "No reply from RCX" with nqc...
|
|
(...) thank you (and bob fay) for your two responses. i have a sneaking suspicion that bob was right on with the curious battery problem. i opened my tower battery case and "re-seated" the battery. (and i confirmed it *was* in the proper (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: "No reply from RCX" with nqc...
|
|
(...) Try this: nqc -v -raw 10 and then also this (substituting the right filename) nqc -v -firmware <filename> and post the results. The "-v" option turns on some logging that may help us figure out what is wrong. (...) The firmware file is (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.nqc)
|
