Jump to content

The Not-So-Great Robot Race


Guest imported_El Mamerro

Recommended Posts

Guest imported_El Mamerro

Full Backstory: THE GREAT ROBOT RACE

 

Summary: Sponsored by the Defense Advanced Research Projects Agency, the Pentagon's research arm, the Darpa Grand Challenge presented competitors with a monumental task: to get a robot to drive itself across the desert, when most of the drones the military uses today have a human piloting them from afar. It's a mission that's so far eluded the Defense Department's brightest minds and its biggest contractors.

 

The challenge was in the form of a 210-mile race from Los Angeles to Las Vegas, through a course whose waypoints were revealed to the teams only 2 hours prior to the start of the race. First one to Vegas within 10 hours would win a million bucks in cash courtesy of the Defense Department. The contest was open to anyone who wished to enter (and with enough money to build a robot Darpa deemed viable). The race took place on March 13, 2004...

 

 

 

...and here's what happened:

 

 

BARSTOW, Calif. -- Looks like we won't be seeing any robot driver's licenses issued anytime soon. All 15 self-navigating vehicles in a 150-mile race across the Mojave Desert were knocked out within a few miles of the starting gate Saturday, victims of technical glitches, barbed-wire fences and rugged terrain.

 

None could claim the $1 million prize offered by a military agency seeking to develop autonomous vehicles that could be used in combat.

 

One of the early favorites, a military Humvee converted by Carnegie Mellon University students, managed to travel 7.4 miles before veering off course and snapping an axle during the race.

 

"It was supposed to be challenging," said Jan Walker, a spokeswoman for the Pentagon agency that sponsored the race. "We knew it would be challenging. We're involved because it's a technology we really need to push forward." Officials foresee using computer-run, remote control-free robots to ferry supplies in war zones.

 

The Defense Advanced Research Projects Agency spent $13 million on the Grand Challenge. It estimates competitors laid out a total of four to five times that amount developing their entries, which rely on global positioning satellites as well as a variety of sensors, lasers, radar and cameras to orient themselves and detect and avoid obstacles.

 

Most of the vehicles Saturday made it less than a mile before stalling, overturning or running off course. One six-wheeled robot built by a Louisiana team was disqualified after it became entangled in barbed wire. Others crashed seconds after starting.

 

"It's a tough challenge -- it's a grand challenge -- you can always bet that it's not doable," Ensco engineer Venkatesh Vasudevan said shortly after his company's entry rolled onto its side several hundred yards from the starting gate. "But if you don't push the limits, you can't learn."

 

The Pentagon's research and development agency would have awarded $1 million to the first team whose microcircuit-studded vehicle could cover the course in less than 10 hours, but most involved in the race were skeptical that any vehicle entered would accomplish the mission.

 

The teams were given a map of the course two hours before the start. It included hundreds of waypoints marked by precise coordinates. Team members were not allowed to steer or touch the robots.

 

Carnegie Mellon's Humvee was the first to set out on the brush-and-boulder-dotted course just after dawn. It took off at a fast clip. Within 15 minutes, the vehicle dubbed Sandstorm had covered about seven miles over mostly flat desert, but it stalled near the tiny town of Daggett.

 

The race was over in about four hours after the final competitors were disabled. Competitors suffered a variety of problems, including stuck brakes and malfunctioning satellite-navigation equipment.

 

Virginia Tech's converted golf cart failed within 100 yards of the starting line when its brakes seized up. It was driven off the course by 23-year-old senior Nick Elder.

 

"Our vehicle knew where to go, but our brakes were holding us back," said the disappointed Elder.

 

Twenty-one teams attempted to qualify in trials earlier this week, but just seven completed a flat, 1.36-mile obstacle course at the California Speedway in Fontana, east of Los Angeles. Some teams were allowed to compete Saturday without finishing the obstacle course.

 

The on- and off-road course, which began in Barstow, was to have ended just across the California line in Primm, Nev. With no entries finishing, the agency could host another contest, probably in 2006.

 

One competitor said the goal wasn't necessarily to complete the race.

 

"From my opinion, it's always been a question of how far you can get," said Palos Verdes High School sophomore Kevin Webb, 16. Their entry, a modified Acura SUV, hit a barrier shortly after crossing the starting line.

 

 

 

 

 

 

 

The Failures:

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update1_f.jpg'>

Red Team 1986 Humvee

 

Distance Traveled: 7.4 miles

 

What Went Wrong: Vehicle veered off course in mountainous section, got stuck on berm. Rubber on front wheels caught fire.

 

Lesson Learned: “Code more driving logic into the software.”

 

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update2_f.jpg'>

SciAutonics II Dune Buggy

 

Distance Traveled: 6.7 miles

 

What Went Wrong: Lost GPS signal. Forgot there was a mountain between it and next checkpoint. Tried to drive through mountain.

 

Lesson Learned: “Go around mountains, not through them.”

 

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update3_f.jpg'>

Digital Auto Drive 2003 Toyota Tundra

 

Distance Traveled: 6.0 miles

 

What Went Wrong: Vehicle stopped for traffic before crossing road. Small rock became wedged beneath tire. Vehicle wouldn’t accelerate hard enough to roll over it.

 

Lesson Learned: “It’ll take us about an hour to teach the truck to step on it next time.”

 

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update4_f.jpg'>

Golem Group 1994 Ford F-150

 

Distance Traveled: 5.2 miles

 

What Went Wrong: Stalled while climbing its first major hill. Onboard computer didn’t give it enough gas.

 

Lesson Learned: “Get the debugging done before we show up in the desert.”

 

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update5_f.jpg'>

Team Caltech 1996 Chevy Tahoe SUV

 

Distance Traveled: 1.3 miles

 

What Went Wrong: Vehicle sensors may have mistaken shadow for boulder. Veered off road to avoid, broke through barbed-wire fence.

 

Lesson Learned: “If no forward motion is achieved, back up and try something else.”

 

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update6_f.jpg'>

Team TerraMax Six-wheel truck

 

Distance Traveled: 1.2 miles

 

What Went Wrong: Interpreted small bushes as enormous rocks and repeatedly backed away from them.

 

Lesson Learned: “Get new sensors that can distinguish between bush and rock.”

 

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update7_f.jpg'>

SciAutonics I Four-wheel ATV

 

Distance Traveled: 0.8 miles

 

What Went Wrong: Hit bump and hard drive failed, causing vehicle to stop making turns.

 

Lesson Learned: “Get solid state hard drives with no moving parts.”

 

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update8_f.jpg'>

Team Cimar 1993 Isuzu Trooper

 

Distance Traveled: 0.5 miles

 

What Went Wrong: Ran into some wire and got totally wrapped up in it.

 

Lesson Learned: “The computer will plan the route next time.”

 

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update9_f.jpg'>

Team Ensco Honda ATV

 

Distance Traveled: 0.2 miles

 

What Went Wrong: Sped too fast along course. Flipped at second turn.

 

Lesson Learned: “Go slower.”

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update10_f.jpg'>

Axion Racing 1994 Jeep Grand Cherokee

 

Distance Traveled: 0.0 miles

 

What Went Wrong: GPS went on fritz. Vehicle drove in circles in start area.

 

Lesson Learned: “Get a new GPS.”

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update11_f.jpg'>

Team CajunBot Six-wheel ATV

 

Distance Traveled: 0.0 miles

 

What Went Wrong: On-off switch located on side of vehicle. Bumped into a wall on way out of start area. Turned self off.

 

Lesson Learned: “Put the on-off switch somewhere else.”

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update12_f.jpg'>

Virginia Tech Modified golf cart

 

Distance Traveled: 0.0 miles

 

What Went Wrong: Brakes locked up in start area, forcing cart to rev engine. Vehicle started smoking and was removed from course.

 

Lesson Learned: “Wake up earlier and test the machine before the race starts.”

 

 

 

 

http://www.wired.com/wired/archive/12.05/images/ST_62_update13_f.jpg'>

Palos Verdes High School 2003 Acura MDX SUV

 

Distance Traveled: 0.0 miles

 

What Went Wrong: Software contained decimal point error. Slammed into 2-foot-tall cement barrier at 22 mph. During qualifying rounds, this vehicle nearly killed the school principal, who was watching from the sidelines.

 

Lesson Learned: “Just like NASA. Even the best make mistakes.”

 

 

 

 

 

 

 

 

 

 

 

 

 

______________

Link to comment
Share on other sites

This forum is supported by the 12ozProphet Shop, so go buy a shirt and help support!
This forum is brought to you by the 12ozProphet Shop.
This forum is brought to you by the 12oz Shop.
Originally posted by El Mamerro

http://www.wired.com/wired/archive/12.05/images/ST_62_update11_f.jpg'>

Team CajunBot Six-wheel ATV

 

Distance Traveled: 0.0 miles

 

What Went Wrong: On-off switch located on side of vehicle. Bumped into a wall on way out of start area. Turned self off.

 

Lesson Learned: “Put the on-off switch somewhere else.”

 

bwa-ha-ha...all that brain power and it turned itself off. ha-ha

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...