| | Multitasking Bert Weber
|
| | Hi, I have some questions about usage of multitasking in robotics. I think its necessary, because it simplifies programming. Instead of breaking down actions in small pieces and check sensors in between. For example: driving a square and watching (...) (20 years ago, 9-Jul-04, to lugnet.robotics)
|
| | |
| | | | Re: Multitasking T. Alexander Popiel
|
| | | | (...) Neither is universally better. Both have their uses. It all depends on what you want to do. If the sensor just indicates something that you need to make a small adjustment for (turn away from a bumper push, for instance), then returning to the (...) (20 years ago, 9-Jul-04, to lugnet.robotics)
|
| | | | |
| | | | Re: Multitasking Bert Weber
|
| | | | Hi, how does BrickOS handle the following situation? Its a path follower robot with bumpers to detect an obstacle. When the robot starts it seeks the black path and follows it. When the robot hits an obstcle, he gets back and turns. How do I (...) (20 years ago, 18-Jul-04, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Multitasking Steve Baker
|
| | | | (...) A useful technique (which doesn't really require parallel threads) is called a "State Machine" (also known as a "Finite State Automaton" or FSA for short). The idea is to list all the 'states' the robot can be in and to assign a number to each (...) (20 years ago, 19-Jul-04, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Multitasking Rob Stehlik
|
| | | | (...) Steve, I just want to say thanks for your clear explanation. I have heard the term state machine tossed around a lot, but didn't really know what it was. (Not all of us robotics guys are computer programmers for a living!) I don't need to (...) (20 years ago, 21-Jul-04, to lugnet.robotics)
|
| | | | |