|
|
Start of Tutorial |
The leJOS Navigator API provides a convenient set of methods to control a robot. There are methods for moving to any location and controlling the direction of movement. A Navigator object will automatically keep track of the current angle and x, y coordinates after every movement. The great part about this class is that it can be used by any robot with differential steering, regardless of the construction of the robot.
Differential steering has one requirement: the robot must be able to turn within its own footprint. That is, it must be able to change direction without changing its x and y coordinates. The robot can have wheels with a diameter of eight centimeters or three centimeters, or no wheels at all (treads, legs), or it can be fast or slow - it doesn’t matter!
These types of physical parameters are addressed by the constructor of the Navigator class. Once these parameters are set, the Navigator class works the same for all differential robots. Let’s examine the actual interface.
distance - The positive or negative distance to move the robot.
angle - Angle to rotate in degrees. A positive value rotates left, a negative value right.
angle - The angle to rotate to, in degrees.
x - The x coordinate to move to.y - The y coordinate to move to.
The Navigator interface is used for two classes in the josx.robotics package: TimingNavigator and RotationNavigator. This tutorial will use TimingNavigator exclusively because it is the easiest to use and requires no additional Lego parts.
TimingNavigator relies on keeping track of coordinates by measuring movement in terms of the number of seconds it has travelled or rotated. Robots have different wheel radii, different gearing, different motor strengths and different axle lengths so the timing constants for a particular robot will differ. In order to accomodate this, the TimingNavigator class requires values for the time it takes for the robot to move any given distance, and the time it takes to rotate any given angle.
Both of these values could be given in the form of speeds, but to make things easier the constructor just asks for the time it takes to travel one-hundred units (inches or centimeters - whatever you prefer to use), and the time it takes to complete one full rotation. The constructor also requires two Motor objects - one for the left wheel and one for the right. This is to let it know which output ports are being used to drive the movement.
right - The motor used to drive the right wheel e.g. Motor.C.left - The motor used to drive the left wheel e.g. Motor.A.timeOneMeter - The number of seconds it takes your robot to drive one meter (e.g. 2.0 seconds is normal for a fast robot, 5 seconds for a slower robot).timeRotate - The number of seconds it takes your robot to rotate 360 degrees. (e.g. 0.646 is normal for a small axle length, 2.2 for a larger axle length)For this part of the tutorial you will need to build a robot that can rotate in its own footprint. Once it is completed you can give it some intelligent navigation abilities.
The TimingNavigator requires us to figure out how long it takes to travel one meter, and how long it takes to rotate 360 degrees. The first part is easy; all we need to do is make a simple program to get it moving forward and then time it:
import josx.platform.rcx.*;
class TravelTest {
public static void main(String [] args) {
Motor.A.setPower(7); // Change to equalize motors
Motor.C.setPower(7); // Change to equalize motors
Motor.A.forward();
Motor.C.forward();
}
}
The above code has two lines for setting the power to each motor. Generally the motors do not produce the same torque, which can cause your robot to veer off in one direction. When I first tested Trilobot, it veered off significantly to the left indicating motor C is turning faster than motor A. By playing around with the aPower argument in the setPower() method, I came up with the following revised code:
import josx.platform.rcx.*;
class TravelTest {
public static void main(String [] args) {
Motor.A.setPower(7);
Motor.C.setPower(4); // Decreases power
Motor.A.forward();
Motor.C.forward();
}
}
It is very important to balance the two motors! If they are not balanced the robot will be thrown off course. Now we need to create a small track for Trilobot by measuring out a meter (100 centimeters) on the floor. If you want, you can measure out 100 inches if you are more comfortable using the imperial system of measurements, but just make sure you consistently use inches with all measurements. If you use inches in the constructor, the TimingNavigator class will use inches for the x and y coordinates.
For better accuracy, instead of measuring 100 units, you can measure out 400 units, and then divide the final result by four to get the average. My test is on carpet, which will produce different times than if it was on a hard surface. The total four meter trip took 21.9 seconds, so we will use the value of 5.475 seconds per meter. Next, we need to measure the time it takes to rotate 360 degrees. For this, I’m going to make it rotate four times and average them out. The code is the same as above, only one of the motors will move backwards:
import josx.platform.rcx.*;
class RotateTest {
public static void main(String [] args) {
Motor.A.setPower(7);
Motor.C.setPower(4); // Decreases power
Motor.A.forward();
Motor.C.backward();
}
}
Four complete rotations took 16.00 seconds, so one rotation is about 4.0 seconds. I also tried rotating counter-clockwise to see if it produced a different result, but it was quite similar at 16.27 seconds, or 4.0675 seconds. I’ll use a final average of 4.03 seconds. Now that we have our two required values we can create a TimingNavigator object and try out some simple functions.
Our first test will make your robot spin 360 degrees (so we can see how accurate we were with the calibrations), then trace out the shape of a square. The path will look similar to Figure 7-8. In order to trace the square, we will make it go to the following coordinates: (100,0) (100,100) (0,100) (0,0).
import josx.platform.rcx.*;
import josx.robotics.*;
class Testbot {
public static void main(String [] args) {
Motor.A.setPower(7);
Motor.C.setPower(5);
TimingNavigator n = new TimingNavigator(Motor.C, Motor.A, 5.475f, 4.03f);
n.rotate(360);
n.gotoPoint(100,0);
n.gotoPoint(100,100);
n.gotoPoint(0,100);
n.gotoPoint(0,0);
}
}
Note: The third and fourth parameters in the above constructor will likely be different for you than the values above (5.475 and 4.03). These values are dependent on the motor strengths and battery charge of your robot. If your robot uses lithium batteries the wheels will probably turn faster, so the parameters in the constructor will likely be smaller than a robot that uses rechargable batteries.
In the above code we have retained the method calls to setPower() in order to equalize the motors. If all goes well the robot should complete a full square and then stop. If you notice your robot rotates more than 360 degrees, you might want to consider lowering the rotate argument in the TimingNavigator constructor, and likewise if it doesn’t rotate enough it should be increased. Once this is straightened out as close as possible (it will never be perfect) you can move on to some more serious uses of the Navigator class.
|
|
Start of Tutorial |