28.01.2013 Views

Build Your Own Combat Robot

Build Your Own Combat Robot

Build Your Own Combat Robot

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 8: Remotely Controlling <strong>Your</strong> <strong>Robot</strong> 179<br />

every microcontroller can receive and transmit serial communications data. Because<br />

of this, operator interfaces and robot controllers can be designed to transmit<br />

and receive serial communications, and the radio modems can be used to transmit the<br />

data between them.<br />

A simple operator interface can be a microcontroller, such as the Basic Stamp or<br />

the Motorola 68HC11, to read in analog data from a joystick and digital data from a<br />

weapons switch, and to convert that data into serial communications data that<br />

can be transmitted. The robot controller can also use the same type of<br />

microcontrollers to convert incoming serial data to output digital signals for turning<br />

on and off solid-state relays for weapons and generate the 1- to 2-millisecond<br />

pulse modulation that motor controllers use to drive the robot’s motors. The details<br />

of how to create the specific subsystems is outside the scope of this book, but<br />

in Appendix B you’ll find several references to books that will explain how to<br />

build the various components that can be used in your own custom combat robot<br />

R/C system.<br />

It is recommended that beginning robot builders use either a traditional R/C<br />

system or the IFI <strong>Robot</strong>ics Isaac system. If you try to build your own R/C system,<br />

you will eventually end up with something that is functionally similar to the Isaac<br />

system, and you might end up spending most of your time building the remote<br />

control system.<br />

For those of you who really want to build you own custom remote-control systems,<br />

research FCC rules on radio communications, seriously consider using radio<br />

modems, and remember safety is the number-one consideration that must be<br />

built into controllers. You must have failsafe and interference-handling features<br />

built into the control system, or you will not pass safety inspections. In addition,<br />

some competitions require noncommercial custom radio systems be separately<br />

pre-approved, far in advance of the actual event.<br />

Failsafe Compliance<br />

Whichever radio setup you use, most competitions have strict rules on failsafe<br />

compliance that must be met for your robot to pass safety inspection. <strong>Your</strong> robot<br />

must stop moving and deactivate all its weapons when it loses radio contact. This<br />

shutdown must occur even if the robot was in motion or had its weapon running<br />

at the time it lost radio contact.<br />

Radio systems respond differently when a loss-of-signal condition occurs. AM<br />

and low-cost FM receivers simply stop transmitting servo pulses when they stop receiving<br />

a valid radio signal. Most electronic speed controllers shut down when they<br />

stop receiving a valid servo pulse, and R/C servos will simply freeze in place. The<br />

ESCs that shut off when a loss-of-signal condition occurs will fulfill the failsafe requirement<br />

with nearly any non-PCM radio. Mechanical speed controllers that use a<br />

servo to trigger relays to run motors will not pass a failsafe requirement test, as the<br />

servo will remain in its last commanded position when the radio shuts down.

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

Saved successfully!

Ooh no, something went wrong!