 | | Re: Short term memory ablut sensor input??? —David Chen
|
| | | Agreed, LegOS is the way to go. Here is a LegOS program I wrote for a robot that keeps track of its heading in one of 8, increments (45 degrees intervals, numbered 0 to 7 heading clockwise). It keeps track of the last 10 segments in it's travels (...) (24 years ago, 21-Sep-00, to lugnet.robotics.rcx)
|
| | | |
| | | | | Re: Short term memory ablut sensor input??? —Gerry Normandin
|
| | | | Can you remember a touch sensor reading? This way by using only one light sensor as an irpd, I can detect which way to turn to avoid the obstacle. (...) */ (...) turning */ (...) */ (...) travel */ (...) */ (...) ------ (...) */ (...) ------ (...) (...) (24 years ago, 21-Sep-00, to lugnet.robotics.rcx)
|
| | | | |
| | | | | | Re: Short term memory ablut sensor input??? —David Chen
|
| | | | (...) The program doesn't actually record in the Vectors array any information about where it saw an obstacle. It just records which direction the robot went and how far (according to the rotation sensor) during the last leg of the journey. Each (...) (24 years ago, 22-Sep-00, to lugnet.robotics.rcx)
|
| | | | |
