28.01.2013 Views

Build Your Own Combat Robot

Build Your Own Combat Robot

Build Your Own Combat Robot

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

176 <strong>Build</strong> <strong>Your</strong> <strong>Own</strong> <strong>Combat</strong> <strong>Robot</strong><br />

The “PWM” outputs are the same type of 1- to 2-millisecond signals that R/C<br />

servos and electronic speed controllers such as the Victor 883, Vantec, and traditional<br />

R/C car ESCs, understand. With this system, you could control 16 different<br />

high-powered motors—double the number of motors you could control with<br />

top-of-the-line traditional R/C systems. Then you can add up to 16 additional relay<br />

controls for weapons, actuators, lights, or just about anything else you would<br />

like to control.<br />

What makes this system different from traditional R/C systems is its ability to<br />

analyze digital and analog inputs. In your robot, you could include tachometers<br />

on the motors to monitor actual rotational speed to implement closed-loop speed<br />

control. You could add thermocouples or resistive temperature sensors to the motor<br />

housing to monitor the temperature of the motors and help prevent them from<br />

overheating. In the robot controller is a Basic Stamp that can be programmed to<br />

read in the input values and send signals out to control the corresponding actions<br />

of the robot. Not only can the robot perform some semiautonomous actions, but<br />

the robot controller can send back information to the main operator interface so<br />

that the operator can be notified what the robot is doing internally. One set of data<br />

could be a self-diagnosis to monitor the health of the robot during a combat<br />

match, and you could even monitor the charge on the batteries in real time.<br />

Table 8-4 shows a list of input and output features of the operator interface. The<br />

operator interface for the Isaac system is different from traditional R/C transmitters.<br />

With the traditional R/C transmitter, the radio frequency (RF) transmitter,<br />

joysticks, knobs, switches, and all the electronics are enclosed in one single<br />

hand-held package. The Isaac operator interface consists of a general electronics<br />

module and a separate RF transmitter/receiver module. All the joysticks, switches,<br />

knobs, and displays have to be added. The drawback to this system is that the entire<br />

operator interface has to be built. The advantage to this type of setup is that you<br />

could build an interface that has all the control features you want in the robot, and<br />

the features can be located where you want them. So, for example, the same joystick<br />

used with computer games can be used, or a simple potentiometer joystick found in<br />

traditional R/C transmitters can be used. The light emitting diode (LED) indicators<br />

Input/Output Device Quantity<br />

Joystick ports 4<br />

Digital inputs 16<br />

Analog Inputs (0–5 volt, 8-bit A/D) 16<br />

LED indicators, user defined 8<br />

LED output drivers 8<br />

TABLE 8-4 IFI <strong>Robot</strong>ics Isaac Operator Interface �

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!