The comment "the division’s leader, Jonathan Rosenberg, said the company needed 'to have a debate on hydraulics.'" is significant. Google also owns Schaft, which has an all-electric humanoid with water-cooled motors that are heavily overdriven for brief periods using ultracapacitors to get a power boost. Boston Dynamics' robots are hydraulic, using proportional valves controlled by high speed servoloops. This works, but it has lots of disadvantages. The energy efficiency is poor when you don't need full power. There's no energy recovery. The system is bulky for a humanoid. For the pony-sized BigDog, it made sense. Early industrial robots were hydraulic, but that's now rarely seen except in very large robots. Electric motors and their controls have improved enormously in recent years.
I was expecting, after the Google acquisition, to see a new humanoid robot about now with Schaft's drive system, Boston Dynamics' balance system, and Google's image understanding system. That was the good outcome. Apparently Boston Dynamics does not play well with others, and that didn't happen.
Notice that Google isn't selling Schaft. I hope that they're doing OK. They're people from Tokyo University and from Honda's ASIMO project who felt things were moving too slowly. But they're in Tokyo, and Google may have problems managing remote teams.
As for "reality is hard", a good humanoid robot is mechanically at least as complicated as a car. Look how much engineering effort it took to develop good cars. Today, small teams can build a car, but that's because the problem and technology are well understood and you can buy many parts off the shelf.
Google has no track record in hardware with moving parts. Their autonomous vehicles have great software, but the hardware is purchased and bolted on. (Really bolted on; they do not bother to integrate the sensors into the vehicle shell, unlike every auto manufacturer that's done self-driving.) They're still using those rotating Velodyne scanners, which are a mechanical system that should have been replaced years ago. Flash LIDARs and MEMS LIDARs exist. Even the Google StreetView cars look clunky, and their backpack StreetView thing needs a redesign from GoPro.
I can see the cultural problems between Google, with no track record in mechanical engineering and a very young workforce, and Boston Dynamics, with good mechanical engineers and a 67 year old CEO. On the other hand, Google should not have bought all those robotics companies and expected them to make money Real Soon Now. Look at automatic driving. It's been 11 years since the DARPA Grand Challenge, when we first saw that it could really work. Nobody has a production vehicle on the road yet. It's a long haul with a big payoff. This isn't like the ad business.
If anybody from Google is reading this: you still have Schaft. Don't fuck that up. Thank you.
I was expecting, after the Google acquisition, to see a new humanoid robot about now with Schaft's drive system, Boston Dynamics' balance system, and Google's image understanding system. That was the good outcome. Apparently Boston Dynamics does not play well with others, and that didn't happen.
Notice that Google isn't selling Schaft. I hope that they're doing OK. They're people from Tokyo University and from Honda's ASIMO project who felt things were moving too slowly. But they're in Tokyo, and Google may have problems managing remote teams.
As for "reality is hard", a good humanoid robot is mechanically at least as complicated as a car. Look how much engineering effort it took to develop good cars. Today, small teams can build a car, but that's because the problem and technology are well understood and you can buy many parts off the shelf.
Google has no track record in hardware with moving parts. Their autonomous vehicles have great software, but the hardware is purchased and bolted on. (Really bolted on; they do not bother to integrate the sensors into the vehicle shell, unlike every auto manufacturer that's done self-driving.) They're still using those rotating Velodyne scanners, which are a mechanical system that should have been replaced years ago. Flash LIDARs and MEMS LIDARs exist. Even the Google StreetView cars look clunky, and their backpack StreetView thing needs a redesign from GoPro.
I can see the cultural problems between Google, with no track record in mechanical engineering and a very young workforce, and Boston Dynamics, with good mechanical engineers and a 67 year old CEO. On the other hand, Google should not have bought all those robotics companies and expected them to make money Real Soon Now. Look at automatic driving. It's been 11 years since the DARPA Grand Challenge, when we first saw that it could really work. Nobody has a production vehicle on the road yet. It's a long haul with a big payoff. This isn't like the ad business.
If anybody from Google is reading this: you still have Schaft. Don't fuck that up. Thank you.