# Pose Estimation

From Team 449 Wiki

This page details the derivation of the algorithm we use to draw profiles. It finds the next position of a 2-sided tank drive given the past position and the distance traveled by each wheel since that position. It assumes velocity was constant on that interval. In this description I'll be referring to each interval as a "tic."

## Contents

## Explanation

For the sake of these calculations, we treat the tank-drive robot as two wheels along an axis (corresponding to the center of the robot). During each tic, we assume the robot can be doing one of three things: driving in a straight line, turning along some circle, or standing still. The approximation of circular movement is convenient; it is easy to calculate and (assuming constant velocity) accurately accounts for robot movement with errors on the order of O(x^3).

If the robot is standing still, the next position is the same as the current position. If it's driving in a straight line, we just move its position in the direction it's facing by the measured distance moved. However, if it's turning, things get a bit more complicated. The robot is turning some angle around some point. We know that point must be in a line with the two wheels, but we don't know how far away it is (it can be between the wheels). The point it's turning around is known as the Instantaneous Center of Curvature, or ICC.

## Variables

is the robot's previous heading (i.e. what angle it was pointed at at the beginning of the tic). Note that for the purpose of this article, all angles will be positive *counterclockwise* from the x-axis. If you are implementing this on a system that follows the opposite convention, simply swap "right" and "left" for all the math that follows.

is the distance between the wheels

is the distance traveled by the left wheel this tic

is the distance traveled by the right wheel this tic

is the radius of the circle the robot is turning on

is the angle the robot is turning around that circle

## Finding the Sector

First, we'll find the and that describe the sector traced out by the robot's path. Theta is easy, it's just radians. To see why this makes sense, try a few examples: 0 and 1, 1 and -1, and, to take a 90 degree (or radian) pivot turn, the right side moves 0 and the left side moves a quarter of the circumference of the circle with a radius of , or . Determining is a bit trickier. Something to note here is that if is 0, the sector is actually just a rectangle so is infinity. We ignore that case because it's easy enough to handle separately (the robot's just driving straight). The formula is

To derive this formula, start with the observation that the ratio between the distances is equal to the ratio between the radii . Think through this, especially with the sample cases above, and you'll see it makes sense. Then, solve for :

## Finding the Vector

Next, we want to turn the sector we found into a change in Cartesian coordinate values. To do this, we'll draw a vector pointing from the center of the where the robot was last tic to where it is now. We'll call this vector , and call the angle between it and the X-axis . To find (the magnitude or length of ) and , we can draw an isosceles triangle with legs of length and a base of length , with a vertex angle of and therefore base angles of , as shown in the diagram. Knowing everything about this triangle, we can then see that because we take the angle between and the line connecting the robot's wheels last tic , and subtract this from the angle between that line and the X-axis , yielding the angle between and the X-axis. Note that this is equivalent to simply taking the average of the current and previous robot headings.

Finding is even easier because we can just use Law of Sines:

- (note that this can also be seen directly by bisecting and considering the resulting right triangle)

Now all we have to do is turn this vector into a change in Cartesian coordinates, which we can do by splitting into it component vectors. In order to find the vectors for the left and right wheels, replace with and respectively.

## Practical Implementation

In practice, encoder measurements are not perfectly reliable indicators of robot movement: wheels can slip, such as during hard acceleration or a collision, de-coupling the measured wheel movement from the actual movement of the robot. For this reason, pose estimation works best when the robot is moving in a smooth, well-controlled manner, such as during autonomous (especially when following motion profiles that have been chosen to limit slip-causing factors such as jerk and acceleration).

Even under relatively ideal conditions, however, tank drives inevitably experience some degree of slippage due to "wheel scrub" during turns. In practical terms, this leads to the calculated value of ending up somewhat larger than actual angular change of the robot.

A "first-order" correction for this problem can be achieved by substituting an inflated, "effective" value of for the actual geometrical value, thus operating under the assumption that the effect of wheel scrub is to decrease by some constant factor relative to the theoretical value. In order to determine a suitable "effective" value of , rather than measuring the robot, one can run a motion-profile that spins the robot in place with each side of the drive moving a known distance, and measure the resulting angular change; can then be back-calculated from the equations above. Repeating the test for a variety of distances and averaging the results may yield a better value.

While this correction works reasonably well given slow, well-controlled conditions, it is still highly imperfect. A better solution involves the use of a gyroscope to directly measure . The simplest implementation is to simply neglect to calculate from the encoders, and instead directly use the measured value from the gyro. The encoders are thus used only to determine the value of ; assuming that wheel scrub contributes only to angular error, and not to translational error, we instead calculate . Note that no value of is needed at all for this method.

More complex solutions may involve fusing gyro and encoder estimates for in more rigorous ways, such as through a Kalman filter.