 | | Re: Positioning —David Leeper
|
| | | Hi Pete, Well, here's what I had in mind. I think it can find landmarks beyond the visible horizon. First, instructions are stored in the map. =-= BEGIN INSTRUCTIONS =-= Go until you see a red brick Turn left Go until you see a green brick Rurn (...) (25 years ago, 26-Jan-00, to lugnet.robotics)
|
| | | |
| | | | | Re: Positioning —Pete Hardie
|
| | | | (...) My point is more basic - you can find those traffic lights because you are using additional info - that they are all located along the 'grid' of roads, and that if you veer left, you correct when you reach the edge of the pavement (or gravel, (...) (25 years ago, 26-Jan-00, to lugnet.robotics)
|
| | | | |
| | | | | | RE: Positioning —Ralph Hempel
|
| | | | | (...) And all we get is the footage from the little CCD camera it was carrying.... Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for LEGO Mindstorms at: (URL) ---...--- Reply to: rhempel at bmts dot com ---...--- (25 years ago, 26-Jan-00, to lugnet.robotics)
|
| | | | | |
| | | | | | Re: Positioning —David Leeper
|
| | | | Hi Pete, Those are good points. But I believe they apply to other types of mapping as well. For example, when testing SoftBricks I built a robot that travels a map and if it gets to the desired destination, sends the map to another robot with the (...) (25 years ago, 26-Jan-00, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Positioning —Pete Hardie
|
| | | | (...) Some questions I have - what are you using for 'landmark'? How far away can the legobot detect a landmark? When giving directions including a landmark, what are the steps leading up to "...when you get to the X..."? And how does a bot (...) (25 years ago, 26-Jan-00, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Positioning —David Leeper
|
| | | | | Hi Pete, The direct answer to what I've used for landmarks is colored marks, like those found on the RCX test pad. If the robot is a few inches to the left or right of the exact path, it'll still find the mark, assuming it's a few inches wide. But (...) (25 years ago, 26-Jan-00, to lugnet.robotics)
|
| | | | | |
| | | | | | Re: Positioning —David Leeper
|
| | | | | Hi Pete, I was looking back over you post and realized I didn't answer a couple of your questions. (...) In the program I wrote there are only a few commands. Go forward. Turn left at landmark X. Turn right at landmark X. (...) To be honest, I (...) (25 years ago, 27-Jan-00, to lugnet.robotics)
|
| | | | | |
| | | | | | | Re: Positioning —Pete Hardie
|
| | | | | | (...) The main problem I'm seeing is that the legobot has very short sight, and so it can only travel a certain distance before it is nearly sure to miss a landmark, and then be lost. Also, in the Real World (tm), creatures with the limited senses (...) (25 years ago, 27-Jan-00, to lugnet.robotics)
|
| | | | | | |
| | | | | | | | Re: Positioning —David Leeper
|
| | | | | | Hi Pete, I agree that the short sight is a problem. In my tests, I used wide strips. Three times as wide as the RCX. And they were no more than a foot apart. So missing them would have been difficult. In real life, you could use similar tricks. For (...) (25 years ago, 28-Jan-00, to lugnet.robotics)
|
| | | | | | |
| | | | | | | | Re: Positioning —Mauro Vianna
|
| | | | | | I have been watching this discussion with great interest. I was looking for a solution for this problem since I wanted to program a robot to find his way inside my apartment. The problem I found in the landmark system was that you don't have a (...) (25 years ago, 29-Jan-00, to lugnet.robotics)
|
| | | | | | |
| | | | | | | | Re: Positioning —David Leeper
|
| | | | | | Hi Mauro, Maybe I'm misunderstanding, but it seems to me that if you can't tell your robot how to turn correctly, no mapping system would work. The system I used contained a simple TURN LEFT, TURN RIGHT method. Each turn is 45 degrees. I didn't (...) (25 years ago, 29-Jan-00, to lugnet.robotics)
|
| | | | | | |
| | | | | | | | Re: Positioning —Andy Gombos
|
| | | | | | | Well, it seems that you all want this to be flexible. How I understand it is that you will have to do at least some preperation to use this landmark system. Now I was thinking about Marco's idea-put a grid of IR beams on the floor, and use the (...) (25 years ago, 30-Jan-00, to lugnet.robotics)
|
| | | | | | | |
| | | | | | | | | Re: Positioning —Roger Hamlett
|
| | | | | | | | In lugnet.robotics, Andy Gombos <gombos@ne.infi.net> writes: How about a completely different approach?. Two 'beacons'. Each radiates a pulse of IR, and simultaneously, a pulse of ultrasonic tone. With each beacon firing alternately. The receiver (...) (25 years ago, 30-Jan-00, to lugnet.robotics)
|
| | | | | | | | |
| | | | | | | | | | Re: Positioning —David Leeper
|
| | | | | | | | Hi Roger, This sounds interesting. Unfortunately, I don't have any experience with Beacon mapping, though I hope to explore it some time in the future. Perhaps someone else on this list has experience in this area? David Leeper (would love to find (...) (25 years ago, 31-Jan-00, to lugnet.robotics)
|
| | | | | | | | |
| | | | | | | | | | Re: Positioning —Roger Hamlett
|
| | | | | | | | (...) The real problem, would be how to return the data to the RCX. The sensor would either have to return the two 'distance' values, and use two sensor inputs, or do the arithmetic itself, and return an X/Y co-ordinate pair on two inputs. Either (...) (25 years ago, 31-Jan-00, to lugnet.robotics)
|
| | | | | | | | |
| | | | | | | | Re: Positioning —Mauro Vianna
|
| | | | | | Well, I can tell the robot to turn 45 degrees using timing but it's not precise enough. It would be something about 43-47 degrees. I could use a rotation sensor (but I don't have one) to increase accuracy but there will always be a smal error. After (...) (25 years ago, 30-Jan-00, to lugnet.robotics)
|
| | | | | | |
| | | | | | | | Re: Positioning —David Leeper
|
| | | | | | Hi Mauro, I understand now, and you're right, it is a concern. I think the way to deal with it is to make landmarks big and hard to miss. This is the way landmarks work in real like. They are big. In this case, I'd say this means using a wide strip (...) (25 years ago, 31-Jan-00, to lugnet.robotics)
|
| | | | | | |
| | | | | | Re: Positioning —Marco C.
|
| | | | | (...) come (...) That's one of the reasons why a programmer goes to all the trouble (and fun?) of building a physical model of a bot instead of dealing with over-acurate 3D CG simulations. Ok, now for the Positioning system debate. Just one word: (...) (25 years ago, 27-Jan-00, to lugnet.robotics)
|
| | | | | |
| | | | | | | Re: Positioning —David Leeper
|
| | | | | | | Hi Marco, Building the robot is definitly fun. But I was really suprised when I built two robots from the same design, ran the same "GO" program in them and they moved differently! 8^o I'm glad to find another ant lover here! I try to check all my (...) (25 years ago, 27-Jan-00, to lugnet.robotics)
|
| | | | | | | |
| | | | | | | Re: Positioning —Ian Warfield
|
| | | | | | (...) Ooh ooh - idea! (Piggybacked, of course.) Somebody make an ant robot with a black paintbrush (1) on its back. Wherever the robot goes, it paints a line behind it that it can follow later. Anyone designing a control system could save a lot of (...) (25 years ago, 27-Jan-00, to lugnet.robotics)
|
| | | | | | |
| | | | | | | | Re: Positioning (sort of off-topic) —Mike Clemens
|
| | | | | | In lugnet.robotics, Ian Warfield writes: [...] (...) My 2am-brain free-associated this with the (classic?) "Langston's Ant" simulation. See: (URL) behavior is Very Cool Indeed. - Mike (25 years ago, 28-Jan-00, to lugnet.robotics)
|
| | | | | | |
| | | | | | Re: Positioning —Marco C.
|
| | | | (...) realtime, (...) Nothing I hadn't thought of myself, after sending that msg :D er... is there any human-eye-invisible IR-Ink ? :> ...so I sould have my flood painted with an invisible grid, all over the place, without the knowledge of my wife (...) (25 years ago, 28-Jan-00, to lugnet.robotics)
|
| | | | |
