|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Carpet line differences
Cool. Never met a programmer who was autonomous.
Anyway: One possible solution is a combination of line following and odometry - that is, measuring distance traveled. Encoders on your wheels/gearbox/sprockets/gears can tell you how far the robot has traveled. You know you need to travel about xx feet before you'll see the split/end of the line/whatever. Use that in your code to your advantage.... In the past, many autonomous robots worked by 'dead reckoning' - simple odometry - to move to a specific location. e.g., Move forward 13 feet, turn right for 0.7 seconds, then move forward 4 more feet.... Hope this helps. |
|
#2
|
|||
|
|||
|
Re: Carpet line differences
Here's the thing, I started this thread before I actually noticed that the "T" that the program was referring to was actually at the very end of the line. This whole time I thought the "T" was actually the team lines. He he... it was only a couple minutes after I posted this, too.
So just disregard my question. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|