
If
tag
sends out a tag message but doesn't receive a reply, it doesn't do anything. The lack of a reply can mean two things: either the other robot did not receive the IR tag message, or the robot
bumped into an obstacle, not the other robot. In the original RoboTag by Matthew Miller, the arena contained no obstacles, so it was safe to assume that the other robot didn't "hear" the tag
message. The tagging robot would then spin in place shouting "Tag!" repeatedly, hoping to get in range of the other robot's IR port.
Page 183
In our design,
tag
doesn't do anything if a reply is not received. This opens up the possibility of adding physical obstacles to the arena. If the robot bounces into something that doesn't respond to
the tag message, it must be an obstacle.
The next behavior is
avoid
, which helps the robot to avoid the edge of the playing arena. It is triggered by the light sensor. This behavior backs up and turns to move away from the edge, much
like
tag
.
int avoidCommand;
task avoid() {
while(true) {
if (LIGHT_SENSOR < averageLight - 3) {
// Back away from the border.
avoidCommand = COMMAND_FLOAT;
Wait(20);
avoidCommand = COMMAND_REVERSE;
Wait(50);
// Turn left or right for a random duration.
if (Random(1) == 0) avoidCommand = COMMAND_LEFT;
else avoidCommand = COMMAND_RIGHT;
Wait(Random(200));
avoidCommand = COMMAND_NONE;
}
}
}
The highest-level behavior is
tagged
, which is triggered when the IR port receives notification that the robot has been tagged. This behavior tells the robot to send an IR acknowledgement, play
a sad sound, and sit still for eight seconds.
int taggedCommand;
task tagged() {
while(true) {
if (Message() == MESSAGE_TAG) {
taggedCommand = COMMAND_STOP;
SendMessage(MESSAGE_ACKNOWLEDGE);
PlaySound(4);
Wait(800);
ClearMessage();
taggedCommand = COMMAND_NONE;
}
}
}
Arbitration
As mentioned earlier, an additional task is needed to link the robot's behaviors to its motors. In this implementation, a task called
arbitrate
examines the output command variable of each
behavior. If it is not
COMMAND_NONE
, it is used to set the current motor command.
Summary of Contents for MINDSTORMS Robots
Page 22: ...Page 18 The back tread wheels are anchored to the shafts with the 16t gears ...
Page 23: ...Page 19 Page 20 Next start building support for the drive motors ...
Page 26: ...Page 23 The touch sensors are attached only by the shaft that runs through them ...
Page 41: ...Page 41 ...
Page 43: ...Next build the support for the light sensor ...
Page 80: ...Page 85 Make sure the bump on the long pin is up against the 4u beam ...
Page 82: ......
Page 84: ...Page 89 ...
Page 85: ...Step 14 is similar to Step 11 take a deep breath and go slowly ...
Page 87: ...Page 91 ...
Page 88: ...Page 92 Make sure that the two sides are at the same angle They should mirror each other ...
Page 89: ...Page 93 Page 94 ...
Page 90: ...Structural Support Page 95 ...
Page 91: ...Idler Wheel Page 96 ...
Page 92: ...Page 97 Drive Motor ...
Page 93: ...While you re putting the motor in hold on to the worm gear so it doesn t slip off Page 98 ...
Page 94: ...Grabber Arm Motor ...
Page 95: ...Page 99 ...
Page 96: ...Page 100 RCX Attach the RCX on both sides as shown Page 101 ...
Page 158: ......
Page 159: ...Page 175 The 16t gears are nestled inside the tread wheels ...
Page 160: ...Page 176 ...
Page 161: ...Page 177 Attach the motors to output A and output C as shown Page 178 ...