Skip to main content

Science Fair and Texas Torque, FIRST Robotics World Chapmions

I spent today at the a local science fair event. There are more of them spread over the next few weekends. Today's had an elementary school festival and science / math bowl competitions. Next week is the Junior High and, the week after, the Senior High Engineering Design Competition. These both involve building robots.

There was also a robotics demonstration today  and I volunteered for it, naturally. The main activity was the Texas Torque team demonstrating their robot, which won last year's FIRST World Championship. It also was one of the teams leading the Macy's Thanksgiving day parade last November. Last year's challenge was to throw Frisbees through rectangles at one end of the arena.

Not only is the robot impressive but so are the team members. I spoke with Robert and Matthew, mainly, but a couple others approached me to see if I had questions. This competition is for high-school students and, to be blunt, you have to be impressed by their poise and ability to engage with adults and children about their team and robot.

I spoke also with one of the fathers and he related how these young people had to learn to work together. They are all very smart and quite used to having correct answers. Obviously when building a robot like this all their answers cannot be correct so a big learning experience is compromising and considering other ideas.

Participating in this team provided experience in team-work that most students only get through organized sports in high school. Unfortunately in Texas that also comes with adulation that is not always beneficial. This team experience is more beneficial, I believe.

Now on to the robot...

It is 120 lbs of compact engineering, all built in a 6 week period. Each year the challenge is announced early in January and the teams have 6 weeks for construction. Then there are 6 weeks of competition.

The first aspect of the robot you will notice are the two strips of multi-colored LEDs that run up the back, over the top, and back down. You literally cannot miss them. They flash and change colors  to provide the driver with the status of the robot. For instance, is there a Frisbee loaded and ready to shoot?

The next obvious thing is the speed. It fast but maneuverable. The maneuverability was obtained through a design decision to keep the robot short. But this led to another problem. Many teams, especially in Texas, have a strategy of blocking other robots shots. So Torque fixed those other guy's little red wagon by adding an elevator which lifts the shooter above the other robot. Good strategic thinking.

The robot is controlled from joysticks connected to a laptop, although Robert, the driver, uses a modified RC car controller. The laptop sends control signals using 5 GHz WiFi. Again, this was a conscious design decision because (1) some locations block 2.4 GHz ad-hoc WiFi connections and (2) that frequency is less likely to be hacked by another team. (<Sigh> that they need to worry about this.)

The robot is controlled by the driver but they offloaded a number of tasks onto the computer to simplify his job. It is fair to describe the operation as semi-autonomous. For example, there is a camera on the shooter bracketed by very bright LEDs. The rectangular target area is bordered by reflective tape and the LEDs make the outline very clear for the camera. Software detects the rectangle and adjusts the shooter's position automatically.

Twice during the demonstration there were problems. A gear stripped in the shooter mechanism and a wheel came apart. They quickly fixed the problem once the parts were available - they had to send someone for a replacement gear since they could not bring the entire shop to the demonstration. So not only did the robot work well but they attained a certain level of maintainability. Very important if something breaks during a competition.

There are many other impressive features but I will only mention one more. It may not seem like much, but a good design feature was the ease of loading Frisbees. I watched the team members load Frisbees by just tossing them casually into the hopper. There were only few jams and bad loads over the 6 hours they ran the robot, which is not bad. The team even had small children loading Frisbees without any problems. (Yes, it was safe.)

Team Torque is as impressive as their robot and they can rightfully take pride in their accomplishment. Nice job!


Popular posts from this blog

Sensor - Accelerometer & Magnetics

Just as I was finishing my first look at the accelerometer and magnetic field sensors a couple of threads cropped up on the Android Developer's group:

I had the basic code working so dug a little deeper into the rotation routines and the timing. I posted responses on the threads but want here to dig into the details more.

First some observations applicable to my G1:

The sensors report approximetly every 20, 40 and 220 msec for FAST, GAME, and NORMAL.
A sample may be missed for a specific sensor but usually one of them will be generated - but sometimes all can be missed.
The magnetic field sensor is most reliable with only a few drops. The other sensors are dropped considerably more often.

A caveat in all this is the way I setup the sensor handling may make a difference. I have a singl…

Team Waterloo Research Paper on SRR

Team Waterloo published about their work on a robot for the 2012 and 2013 NASA Sample Return Robot Centennial Challenges.
Mapping, Planning, and Sample Detection Strategies for Autonomous Exploration This paper presents algorithmic advances and field trial results for autonomous exploration and proposes a solution to perform simultaneous localization and mapping (SLAM), complete coverage, and object detection without relying on GPS or magnetometer data. We demonstrate an integrated approach to the exploration problem, and we make specific contributions in terms of mapping, planning, and sample detection strategies that run in real-time on our custom platform. Field tests demonstrate reliable performance for each of these three main components of the system individually, and high-fidelity simulation based on recorded data playback demonstrates the viability of the complete solution as applied to the 2013 NASA Sample Return Robot Challenge.  It is the Journal of Field Robotics in the Wil…

Android Activity Analysis

I have been looking at the details of the life cycle of an Android Activity. There are many web sites that discuss this and many examples. But none of the example addressed all the onXXX() methods of Activity. I also found problems with some of the examples. In one case, the GUI update thread could be left running after the Activity supposedly was stopped.

I was trying to determine when the GUI update thread should be created, stopped, paused, etc that initiated this effort. I have a game underway (doesn't everyone?) and figuring out all the Activity infrastructure was giving me fits. Each example did it in a different manner and while there may be no one correct manner most of them seemed a little off. Usually they seemed to omit some of the steps needed to pause, stop, or destroy everything properly.

A number of discussions presented the life cycle as a state machine, as an alternative to the Google flow chart (or here). [I don't mean to single out Eric Burke of StuffThatHappe…