View Single Post
  #7   Spotlight this post!  
Unread 20-02-2010, 21:49
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Built in distance calculations?

In reality, all of these methods are pretty imprecise. Encoders on drive wheels cannot account for slip or sideways motion due to a collision with field or another robot.

The camera method works by knowing the real-world size of the target. At a given distance, the target should measure the same pixel size. Moving closer to the target increases the pixel size, and moving farther decreases. You can think through the symmetric triangles or use trig if you like, but estimating distance based on the perceived size of a known object is a pretty accurate approach. The thing that can cause moderate error is if the vision selects the inner circle rather than the outer error to base the distance computation.

The best way to determine the error is to measure it. Determine if it is accurate enough for what you need and determine if other approaches are more accurate.

Greg McKaskle
Reply With Quote