 | | Re: Rover Programming —Simon Brooke
|
| | | (...) That's one solution, but it isn't essential. The other solution is to assume every square is empty until you've explored it. Obviously, if you get a 'goto' instruction before you've completely mapped the domain, then there's a possibility that (...) (22 years ago, 26-Jun-02, to lugnet.robotics)
|
| | | |
| | | | | Re: Rover Programming —Steve Baker
|
| | | | | (...) So how do you remember what you've already explored? I think you *need* three states if you want your robot to curiously explore it's environment without continually re-exploring areas that it's already visited but which proved to be empty. If (...) (22 years ago, 27-Jun-02, to lugnet.robotics)
|
| | | | | |
| | | | | | | Dead reckoning (was Re: Rover Programming) —Simon Brooke
|
| | | | | | (...) A systematic search pattern is one solution. Not being too anal about it is another - random walking the domain will eventually explore the whole of it, although increasingly inefficiently as time goes on. (...) It's killing me. My first (...) (22 years ago, 27-Jun-02, to lugnet.robotics)
|
| | | | | | |
| | | | | | | | Re: Dead reckoning (was Re: Rover Programming) —Gareth Bestor
|
| | | | | | | (...) If you haven't already, check out (URL) was able to get quite precise dead-reckoning w/ a Lego bot by programming a PID-type controller. - Gareth (22 years ago, 27-Jun-02, to lugnet.robotics)
|
| | | | | | | |
| | | | | | | | | Re: Dead reckoning (was Re: Rover Programming) —Steve Baker
|
| | | | | | | | (...) WOW! That's impressive - but I can't help but get the impression that it's heavily optimised to going around that particular track. Getting that good positioning on the straight sections is impressive - but I wonder how it would have fared in (...) (22 years ago, 28-Jun-02, to lugnet.robotics)
|
| | | | | | | | |
| | | | | | | | Re: Dead reckoning (was Re: Rover Programming) —Steve Baker
|
| | | | | | (...) Yes - managing accelleration is a 'must'...both in speeding up and slowing down - and easing into turns. An abrupt change of speed will generally result in wheel slip. (...) It was good in a straight line - but *hopeless* in a turn because the (...) (22 years ago, 28-Jun-02, to lugnet.robotics)
|
| | | | | | |
| | | | | | | | Re: Dead reckoning (was Re: Rover Programming) —Simon Brooke
|
| | | | | | (...) Well, I did the code changes to do acceleration and deceleration yesterday and it's amazingly successful. I'm not yet quite as good as the Seattle robot, but I suspect that's at least partly because mine has a narrower track. I now believe (...) (22 years ago, 28-Jun-02, to lugnet.robotics)
|
| | | | | | |
| | | | | | | | Re: Dead reckoning (was Re: Rover Programming) —Jona
|
| | | | | | Hi Simon, In my experience casters can introduce errors in the navigation since they tend to not be in the correct position following a turn. Over time this small error can add up. I have had some success by rebuilding my bot to center as much of (...) (22 years ago, 28-Jun-02, to lugnet.robotics)
|
| | | | | | |
| | | | | Re: Rover Programming —David Martineau
|
| | | | (...) While we're talking about programming rovers, could someone give me an example of a 'spiral drive around behavior' in either RCX Code (v1.5) or Gordon's Brick Programmer? Or how about code with two rotation sensors attached to the (...) (22 years ago, 27-Jun-02, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Rover Programming —Simon Brooke
|
| | | | (...) Try this (leJos): import josx.platform.rcx.*; import josx.util.*; import josx.robotics.Navigator; public class Test { public static void main (String[] arg) throws Exception { int size = 100; Navigator nav = new RotationNavigator( ( float)8.5, (...) (22 years ago, 27-Jun-02, to lugnet.robotics)
|
| | | | |
