Robotics

Interview: Lockheed Martin's Todd Danko on the DRC Finals and the future of robotics

Interview: Lockheed Martin's Todd Danko on the DRC Finals and the future of robotics
Team Trooper's robot named Leo competed in the recent DARPA Robotic Challenge
Team Trooper's robot named Leo competed in the recent DARPA Robotic Challenge
View 10 Images
Robot Leo getting out of the car – one of several challenges faced by robots during the competition
1/10
Robot Leo getting out of the car – one of several challenges faced by robots during the competition
Leo was based on the General Dynamics Atlas robot
2/10
Leo was based on the General Dynamics Atlas robot
Leo opening the door during the DRC Finals
3/10
Leo opening the door during the DRC Finals
Leo entering the room
4/10
Leo entering the room
Leo at the valve – one of the functions performed by robots in the simulated disaster response scenario
5/10
Leo at the valve – one of the functions performed by robots in the simulated disaster response scenario
Team Trooper leader Todd Danko
6/10
Team Trooper leader Todd Danko
The Team Trooper members
7/10
The Team Trooper members
Leo at the door
8/10
Leo at the door
Team Trooper's robot named Leo competed in the recent DARPA Robotic Challenge
9/10
Team Trooper's robot named Leo competed in the recent DARPA Robotic Challenge
Robot Leo poses for a photo op
10/10
Robot Leo poses for a photo op
View gallery - 10 images

One of the 24 teams competing at the 2015 DARPA Robotics Challenge, and the only team fielded by a large private company, was Lockheed Martin's Team Trooper and its robot Leo. To find out more about what goes into programming a humanoid robot and the future of robotics, we talked to the team leader, Todd Danko.

Gizmag: What is Lockheed Martin, a company associated more with aircraft and defense in the public mind, doing in a robot competition?

Team Trooper leader Todd Danko
Team Trooper leader Todd Danko

Danko: The whole point is to look for new opportunities. We think that investing in mobile manipulation, which is effectively what we're doing, will be very useful in future applications like underwater or space robotics; places where it's very difficult or impossible to get people to do those tasks. You can use our systems to tell robots what to do, and let the robots do those things.

Why did Lockheed opt for using Boston Dynamics's humanoid Atlas robot?

We're in a world that's complementary to the humanoid form. If you have a very constrained task, like in a factory, a humanoid isn't the right answer. You want to optimize your robot to solve those problems. If you don't have a single problem to optimize, and you want a more general robot, then a humanoid robot makes more sense.

Leo opening the door during the DRC Finals
Leo opening the door during the DRC Finals

Does the humanoid robot produce any challenges in creating software?

It produces tremendous challenges. For a humanoid robot just to stay still and not fall over if you touch it. That's a lot of software on its own. You have to have a good dynamic model of the robot and run it constantly at a thousand Hertz, so it's harder for the robot to fall over. Meanwhile, a robot with wheels, if you turn everything off, it will be mechanically stable. It just sits there.

Were there any surprises working on this project?

Generally, one thing that surprised me is the state of the art of robotics and especially humanoid robotics. It's one thing to see them in a movie or some real robots in specific demos, but with those demos you're seeing the best of what could be, so the state of the art is actually a lot more primitive than many people think it is. It's exciting to be able to help grow that.

Leo was based on the General Dynamics Atlas robot
Leo was based on the General Dynamics Atlas robot

It's a poor analogy, but what would you compare a humanoid robot of today to in terms of its development?

I could get into trouble because I don't have much expertise in human development, but one of our goals was to work toward a robot with the capabilities of a two-year old. I can't say that we exceeded that or didn't, but like a two-year old, there's definitely some misbehavior in these robots. They don't always do what we tell them to.

We noticed in the competition that the robots moved very slowly with a lot of starting and stopping while they solved a problem or awaited an order. What hurdles have to be overcome before we see robots are that are fast and articulate enough to be practical?

There are two sides to this. On one side, robots are already practical in many ways. Probably the most successful robots are much more simple than those [at the competition]. On top of that, you have to consider what are the consequences of an error, so if you have a lot of runs or a lot of time, you may give your autonomous system a lot of latitude to make decisions rather than constantly approving it before it proceeds. In a competition like this, there are greater consequences and if a mistake happens that a human can stop, then we should prevent that from happening.

Secondly, there a lots of things that different groups are working on to improve the performance of robots as a whole. You notice that the robots are untethered. Powerwise, they were lasting an hour at least in most cases, but how useful is an hour of robot time? Maybe you want something that lasts a day or a couple of days even. We need better batteries, better power systems, and more efficient actuators, so there's more power and less use of power down the line.

Leo at the valve – one of the functions performed by robots in the simulated disaster response scenario
Leo at the valve – one of the functions performed by robots in the simulated disaster response scenario

I've never met a perception algorithm that couldn't use more processors to be better. Equally with planning and parallelizing, this provides more possibilities to come up with more solutions. Then there's perception. There's still a lot of room for improvement in the state of the art in perception. We're very good at recognizing specific objects, but more needs to be done in recognizing categories of objects, or to recognize something never seen before and how that could be used.

On top of all this, I think there's still a role for the human to help the robot know what it is that needs to be done. It may be best to have a human in a safe place who can communicate the "what" and allow the robot to do the dangerous things. That's something I think we can see in the near future.

It's the cliché question, but how long do you think it will be before we see robots like this as part of people's lives?

It's going to be a long time before we see a robot like this. Look at what [happened in the competition] and how many people it took to keep that robot from destroying itself. There's a lot of work that needs to be done before we're contributing in a way that's not a burden to the operators. That goes back to all those things we talked about that need to be improved, so it's going to be quite some time. On the other hand, simple robots are already being used in applications today. We're just using more complicated robots in more complicated situations as we go in that direction of complexity.

The video below introduces Team Trooper.

For more information about the 2015 DRC Finals see our full coverage of the event or visit the official site.

View gallery - 10 images
1 comment
1 comment
Daishi
I think people tend to adopt a science fiction view of things and have higher expectations of humanoid robots than they are likely to be able to meet any time in the foreseeable future. I think this sums up the interview nicely:
>It's going to be a long time before we see a robot like this. Look at what [happened in the competition] and how many people it took to keep that robot from destroying itself. There's a lot of work that needs to be done before we're contributing in a way that's not a burden to the operators.
Some of the complexity required just to prevent from falling over if someone touches it plays into that 1 hour of untethered battery life. People think I'm crazy for my frustration with humanoid robots but here we have a robotics engineer form Lockheed Martin working on state of the art technology from Boston Dynamics pretty much confirming it will be a long time before humanoid robots are useful.
In my opinion we should invest R&D time in more capable wheeled/tracked platforms because it would take a fraction of the cost and effort as legs and then use the platforms to crate applications that are useful.
Bipeds are holding up progress because it makes the legged mobility problem pretty much a prerequisite to building robots that perform useful applications and it has a long way to go.
I think a more suitable way to handle these types of challenges is to have robotics teams navigate some type of terrain and then solve some sort of problem and let the teams create the best way to do it. If a legged robot is the most suitable solution let the teams make one, if teams want to try solutions like this one ( http://i.imgur.com/5XSo8ya.jpg ) or tracks to climb stairs and obstacles they should be permitted. I could probably list 4 or 5 ideas for a robot that climbs without legs.
Voice recognition has pretty much come around now and the mobility problem is the next major hurdle and it doesn't seem like much effort is being put into solving it comparative to the massive amounts of time and money spent (wasted?) on bipeds.
A robot that maps its environment and understands voice commands (like "go to up stairs to room 5") could be built cheaply today and serve is the starting point for applications people could build on top of it but I don't see anyone trying to build something like that. I think it would be possible to build an autonomous telepresence robot that could climb stairs for under $3k for instance.