Toyota Software Development for Partner Robots

Posted on February 15, 2009  Comments (1)

Toyota Discusses Software Development for Partner Robots

Yamada: What was unique about the software development for the partner robots exhibited at Aichi Expo was the fact that Toyota entirely disposed of its assets from the past.

Toyota owned some software assets because it had been developing partner robots for some time before developing the robots for the exposition. But those assets were all one-offs. No one but the developers themselves could comprehend their architectures.

As Toyota was developing more than one partner robot for the exposition, the number of developers involved increased. Considering that we can never complete any development if we use the past assets that rely on an individual developer’s skill, we made everything, including the platform, from scratch again.

Toyota developed the platform focusing on promoting design review by visualizing the control logic. Therefore, the company thoroughly separated control sequences and algorithms. To be more specific, it used state transition diagrams.

Each algorithm is stored in a different block in a state transition diagram. With such diagrams, developers can easily comprehend the flow of the control and review the design even if they do not understand each algorithm. The company employed this method because each algorithm such as a bipedal walking algorithm is too complicated for anyone but their developers to understand it.

Related: Toyota Partner Robots (2006)Toyota Cultivating Engineering TalentToyota iUnit

One Response to “Toyota Software Development for Partner Robots”

  1. Anonymous
    September 8th, 2009 @ 6:52 pm

    The bipedal walking algorithm would be very interesting. I have worked with some robotics involving the lego mindstorms and the Java programming language. I’m sure that Toyota could provide some nice ideas for enhancing the code.

Leave a Reply