WEBVTT - The Boston Dynamics Story

0:00:04.160 --> 0:00:07.480
<v Speaker 1>Get in text with technology with tech Stuff from staff

0:00:07.520 --> 0:00:13.800
<v Speaker 1>works dot com. Hey there, and welcome to tech Stuff.

0:00:13.840 --> 0:00:16.840
<v Speaker 1>I am your host, Jonathan Strickland. I'm an executive producer

0:00:16.880 --> 0:00:19.079
<v Speaker 1>here at how Stuff Works, and I love all things tech,

0:00:19.600 --> 0:00:22.760
<v Speaker 1>and today I thought I would look into a pretty

0:00:22.840 --> 0:00:27.120
<v Speaker 1>cool company, one that's been around longer than I realized,

0:00:27.640 --> 0:00:29.880
<v Speaker 1>and one that has created a lot of interesting stuff

0:00:29.920 --> 0:00:32.639
<v Speaker 1>and yet nothing that you can actually buy. So when

0:00:32.640 --> 0:00:35.080
<v Speaker 1>am I talking about? Well, a few years ago, there

0:00:35.080 --> 0:00:38.080
<v Speaker 1>were some videos that came out of a company called

0:00:38.120 --> 0:00:42.720
<v Speaker 1>Boston Dynamics that went absolutely viral, and those videos showed

0:00:42.880 --> 0:00:47.280
<v Speaker 1>four legged robots traversing various types of terrain, sometimes while

0:00:47.360 --> 0:00:52.120
<v Speaker 1>enduring some rather abusive behavior courtesy of some humans, and

0:00:52.400 --> 0:00:55.120
<v Speaker 1>that kind of served as an introduction for a lot

0:00:55.160 --> 0:00:57.880
<v Speaker 1>of people to this company, Boston Dynamics. But as it

0:00:57.920 --> 0:01:01.440
<v Speaker 1>turns out, it had been around a lot longer than

0:01:01.600 --> 0:01:04.479
<v Speaker 1>you might have anticipated based on those videos. In fact,

0:01:04.520 --> 0:01:08.480
<v Speaker 1>it turned twenty five years old in seventeen. So what

0:01:08.760 --> 0:01:12.959
<v Speaker 1>is the story behind the company and its robots. Well,

0:01:13.000 --> 0:01:17.080
<v Speaker 1>the founder of Boston Dynamics is Mark rayber. Raber was

0:01:17.120 --> 0:01:20.679
<v Speaker 1>born in nineteen forty nine and he was a studious Fellow.

0:01:21.160 --> 0:01:25.720
<v Speaker 1>He attended Northeastern University from nineteen sixty eight to nineteen

0:01:25.840 --> 0:01:29.120
<v Speaker 1>seventy three and earned a degree in electrical engineering. He

0:01:29.200 --> 0:01:32.479
<v Speaker 1>then went on to pursue his PhD at the Massachusetts

0:01:32.520 --> 0:01:36.959
<v Speaker 1>Institute of Technology better known as m i T, and

0:01:37.040 --> 0:01:40.240
<v Speaker 1>upon graduating, Dr Rayber got a job at the NASA

0:01:40.319 --> 0:01:43.880
<v Speaker 1>Jet Propulsion Laboratory as a member of the technacal staff.

0:01:43.959 --> 0:01:47.600
<v Speaker 1>So you could say that he was a rocket scientist,

0:01:47.880 --> 0:01:51.480
<v Speaker 1>although really he worked with rocket scientists. His main focus

0:01:51.520 --> 0:01:53.919
<v Speaker 1>was obviously on robotics, and he worked there for about

0:01:53.920 --> 0:01:58.200
<v Speaker 1>three years, leaving in nineteen eighty. His next gig was

0:01:58.680 --> 0:02:01.480
<v Speaker 1>a pretty just went as well. He was an associate

0:02:01.480 --> 0:02:05.040
<v Speaker 1>professor at Carnegie Melon University's Computer science department and the

0:02:05.160 --> 0:02:08.920
<v Speaker 1>Robotics Institute. Now, if you've been listening to tech stuff recently,

0:02:09.000 --> 0:02:11.840
<v Speaker 1>you may remember I mentioned this particular group in a

0:02:11.880 --> 0:02:17.360
<v Speaker 1>recent episode about Uber, because Uber rated Carnegie Melon and

0:02:17.480 --> 0:02:21.680
<v Speaker 1>hired about forty of their robotics experts over to help

0:02:21.760 --> 0:02:26.920
<v Speaker 1>them with their efforts in developing autonomous car programs. Of course,

0:02:26.960 --> 0:02:30.520
<v Speaker 1>by that time Dr Raber was long gone from Carnegie Melon.

0:02:30.600 --> 0:02:33.440
<v Speaker 1>But I just I mentioned it because it's another link

0:02:33.520 --> 0:02:37.320
<v Speaker 1>to a recent episode. In nine six, Dr rayber took

0:02:37.360 --> 0:02:41.120
<v Speaker 1>a position of Professor of Electrical Engineering and Computer Science

0:02:41.160 --> 0:02:43.360
<v Speaker 1>over at m I T, and there he founded the

0:02:43.480 --> 0:02:46.639
<v Speaker 1>m I T Leg Lab, which sounds a bit weird,

0:02:47.480 --> 0:02:50.160
<v Speaker 1>but stick with me. So this was a lab specifically

0:02:50.200 --> 0:02:55.280
<v Speaker 1>dedicated to researching and designing legged robots, not leg lamps,

0:02:55.320 --> 0:02:58.560
<v Speaker 1>as I was first led to believe. It was a

0:02:58.680 --> 0:03:02.920
<v Speaker 1>very difficult realization to say that it wasn't a major reward.

0:03:03.000 --> 0:03:05.280
<v Speaker 1>But it turns out building robots that use legs for

0:03:05.360 --> 0:03:10.679
<v Speaker 1>locomotion it's really really hard. Now why is that? Why

0:03:10.720 --> 0:03:13.280
<v Speaker 1>is it so difficult to build a robot that uses

0:03:13.400 --> 0:03:17.680
<v Speaker 1>legs to get around? Well, first, let's consider the wheel. Now,

0:03:18.360 --> 0:03:22.760
<v Speaker 1>wheels aren't really found in organisms. There are some microscopic

0:03:22.840 --> 0:03:26.680
<v Speaker 1>critters that have components that are vaguely wheel and axle like,

0:03:27.480 --> 0:03:32.240
<v Speaker 1>but they're not really wheels the way are various inventions

0:03:32.280 --> 0:03:35.640
<v Speaker 1>have wheels. A wheel as a limb is not likely

0:03:36.120 --> 0:03:39.480
<v Speaker 1>to ever evolve in nature for several reasons. For one,

0:03:39.960 --> 0:03:43.040
<v Speaker 1>any mutation that would set an organism on the path

0:03:43.760 --> 0:03:47.840
<v Speaker 1>figuratively speaking to developing wheels would likely at first be

0:03:47.920 --> 0:03:51.520
<v Speaker 1>a negative rather than a positive mutation. So in other words,

0:03:51.720 --> 0:03:54.680
<v Speaker 1>an animal with some sort of pro to wheel limb,

0:03:54.880 --> 0:03:57.560
<v Speaker 1>something that's maybe like part of a wheel but not

0:03:57.640 --> 0:04:01.240
<v Speaker 1>a complete wheel, probably wouldn't have very many advantages and

0:04:01.280 --> 0:04:06.240
<v Speaker 1>perhaps have distinct disadvantages with regards to survival, and thus

0:04:06.360 --> 0:04:09.200
<v Speaker 1>it would be unlikely that such a mutation would be

0:04:09.200 --> 0:04:13.760
<v Speaker 1>passed down to future generations to evolve. So that's one thing,

0:04:13.840 --> 0:04:17.560
<v Speaker 1>is that the pathway for evolution is complicated, and if

0:04:17.760 --> 0:04:21.279
<v Speaker 1>you have a mutation that is more likely to get

0:04:21.320 --> 0:04:24.960
<v Speaker 1>you eaten by predators, probably not going to get passed

0:04:24.960 --> 0:04:27.840
<v Speaker 1>down to a lot of offspring. For another reason, the

0:04:27.960 --> 0:04:31.200
<v Speaker 1>rotation of a wheel, if not due to gravity, has

0:04:31.240 --> 0:04:34.680
<v Speaker 1>to come from some source of torque, that rotational power.

0:04:34.760 --> 0:04:37.120
<v Speaker 1>You have to be able to provide power to a

0:04:37.120 --> 0:04:41.000
<v Speaker 1>wheel to make it turn. So locomotion for multicellular organisms

0:04:41.040 --> 0:04:44.520
<v Speaker 1>typically comes from muscles, right, we have our muscles that

0:04:44.560 --> 0:04:48.200
<v Speaker 1>allow us to move our limbs. But there's not really

0:04:48.240 --> 0:04:51.479
<v Speaker 1>a way you could affix muscles to a wheel and

0:04:51.520 --> 0:04:55.160
<v Speaker 1>allow it to turn freely indefinitely. You know, just think

0:04:55.200 --> 0:04:57.760
<v Speaker 1>about how your wrist turns. Like even if you had

0:04:58.360 --> 0:05:01.960
<v Speaker 1>the ability to turn your wrist completely around with no

0:05:02.080 --> 0:05:05.000
<v Speaker 1>pain or anything like that, you couldn't do it indefinitely.

0:05:05.040 --> 0:05:08.240
<v Speaker 1>Your muscles would continuously twist until eventually they would have

0:05:08.279 --> 0:05:10.960
<v Speaker 1>to untwist like a rubber band. You couldn't just keep ongoing,

0:05:11.080 --> 0:05:15.680
<v Speaker 1>so that's another problem. Wheels are almost exclusively in the

0:05:15.720 --> 0:05:21.000
<v Speaker 1>domain of manufactured objects. Now that being said, they're darn't efficient.

0:05:21.279 --> 0:05:25.039
<v Speaker 1>They're the easiest way to create locomotion for vehicles. It

0:05:25.120 --> 0:05:27.960
<v Speaker 1>is also the most energy efficient way to travel relative

0:05:28.040 --> 0:05:32.120
<v Speaker 1>to speed. So it requires a relatively simple implementation to

0:05:32.200 --> 0:05:34.839
<v Speaker 1>create a wheeled robot. You don't have to worry so

0:05:34.920 --> 0:05:37.039
<v Speaker 1>much about degrees of freedom. You don't have to worry

0:05:37.040 --> 0:05:41.040
<v Speaker 1>about pivot points, or vector controllers or balance. I mean,

0:05:41.080 --> 0:05:43.080
<v Speaker 1>as long as you've designed the robot in such a

0:05:43.120 --> 0:05:46.359
<v Speaker 1>way that's relatively stable on its wheels, balance is not

0:05:46.440 --> 0:05:48.080
<v Speaker 1>that big of an issue. So if you're talking about

0:05:48.120 --> 0:05:51.720
<v Speaker 1>the three wheeled or four wheeled robot, balance is pretty easy.

0:05:51.760 --> 0:05:53.880
<v Speaker 1>Once you get down to two wheels, then things get

0:05:53.880 --> 0:05:55.920
<v Speaker 1>a little more tricky. You have to build in other

0:05:56.000 --> 0:05:58.279
<v Speaker 1>systems in order for it to maintain balance, but in

0:05:58.320 --> 0:06:02.279
<v Speaker 1>general it's not that hard to do. They also typically

0:06:02.279 --> 0:06:05.919
<v Speaker 1>cost less to develop and less to build than a

0:06:06.000 --> 0:06:09.839
<v Speaker 1>legged robot. A simple three wheel robot is stable on

0:06:09.839 --> 0:06:12.560
<v Speaker 1>its own. If you've got that basic sort of triangle shape,

0:06:12.760 --> 0:06:14.960
<v Speaker 1>it does not require a lot of high end technology

0:06:15.000 --> 0:06:17.960
<v Speaker 1>to work, just some motors and then whatever sensors and

0:06:18.080 --> 0:06:21.920
<v Speaker 1>processors you need to actually control the robot. Uh. Four

0:06:21.920 --> 0:06:25.240
<v Speaker 1>wheeled robots are are even more stable than three wheeled robots,

0:06:25.279 --> 0:06:27.680
<v Speaker 1>and they can excel in applications that a three wheeled

0:06:27.720 --> 0:06:30.719
<v Speaker 1>robot might find difficult. For example, if you plan for

0:06:30.760 --> 0:06:33.200
<v Speaker 1>your robot to lift things, you could have a three

0:06:33.200 --> 0:06:36.839
<v Speaker 1>wheeled robot that would become unbalanced depending upon where you

0:06:36.920 --> 0:06:39.560
<v Speaker 1>put the load on top of the robot right If

0:06:39.600 --> 0:06:42.080
<v Speaker 1>it's too far off to one side of its center

0:06:42.120 --> 0:06:44.360
<v Speaker 1>of gravity, it can make the robots sort of tip over.

0:06:45.040 --> 0:06:47.320
<v Speaker 1>Our four wheeled robot tends to be more stable in

0:06:47.320 --> 0:06:50.520
<v Speaker 1>those cases. You can also design a wheeled robot to

0:06:50.520 --> 0:06:54.120
<v Speaker 1>operate even if it's been flipped upside down. So if

0:06:54.160 --> 0:06:56.800
<v Speaker 1>the robot is such that the wheels can make contact,

0:06:56.880 --> 0:06:59.760
<v Speaker 1>whether it's right side up or upside down, you could

0:07:00.000 --> 0:07:03.360
<v Speaker 1>of the option of continuously operating that robot even if

0:07:03.360 --> 0:07:05.320
<v Speaker 1>it were to flip over. In fact, I remember some

0:07:05.480 --> 0:07:07.800
<v Speaker 1>remote controlled cars that were designed this way. They were

0:07:07.839 --> 0:07:11.320
<v Speaker 1>marketed as that you would purposefully drive your car and

0:07:11.360 --> 0:07:13.320
<v Speaker 1>to say a wall, make it flip over, and then

0:07:13.320 --> 0:07:16.000
<v Speaker 1>you could keep on driving the car just kind of fun.

0:07:16.520 --> 0:07:19.400
<v Speaker 1>That's the same basic idea, but wheels are not ideal

0:07:19.440 --> 0:07:22.880
<v Speaker 1>across all different types of terrain. They work best on

0:07:23.000 --> 0:07:26.239
<v Speaker 1>tracks if you have them, but if you don't have tracks,

0:07:26.280 --> 0:07:30.480
<v Speaker 1>they work best on smooth even ground. Depending upon the

0:07:30.520 --> 0:07:33.400
<v Speaker 1>wheel design and the torque available, they may be able

0:07:33.480 --> 0:07:37.280
<v Speaker 1>to travel over semi rough terrain too fairly rough terrain,

0:07:37.360 --> 0:07:39.640
<v Speaker 1>but they aren't great for everything, and if the ground

0:07:39.680 --> 0:07:42.720
<v Speaker 1>is really challenging, they can prove to be ineffective. So

0:07:42.760 --> 0:07:44.760
<v Speaker 1>that challenge could be that the ground is just too

0:07:44.840 --> 0:07:48.200
<v Speaker 1>rocky or covered in debris, or it's composed of loose

0:07:48.240 --> 0:07:51.640
<v Speaker 1>elements like sand, and in those situations, legs might be

0:07:51.640 --> 0:07:56.400
<v Speaker 1>more effective. Your wheels might otherwise spin needlessly, just completely

0:07:56.720 --> 0:08:00.000
<v Speaker 1>without motion. You're just turning around and you're digging yourself

0:07:59.840 --> 0:08:03.440
<v Speaker 1>into a hole. Or they could end up catching on

0:08:03.560 --> 0:08:06.320
<v Speaker 1>debris and pulling them into the works of the robot,

0:08:06.520 --> 0:08:10.480
<v Speaker 1>gumming everything up. A legged robot with the right control

0:08:10.520 --> 0:08:14.520
<v Speaker 1>system or programming can step over obstacles and move smoothly

0:08:14.600 --> 0:08:17.400
<v Speaker 1>over different types of terrain, robots can use legs to

0:08:17.440 --> 0:08:19.960
<v Speaker 1>select a precise spot on the ground to place its

0:08:20.000 --> 0:08:23.600
<v Speaker 1>weight and then shift to move. A wheel has little

0:08:23.680 --> 0:08:26.480
<v Speaker 1>choice but to just roll ahead, but a legged robot

0:08:26.520 --> 0:08:28.720
<v Speaker 1>can place its legs and then shift its weight in

0:08:28.760 --> 0:08:31.800
<v Speaker 1>a very specific way, which is helpful on uneven ground

0:08:31.920 --> 0:08:33.920
<v Speaker 1>or going up and down the stairs. And depending upon

0:08:33.920 --> 0:08:36.319
<v Speaker 1>the design of the robot, you can make it where

0:08:36.880 --> 0:08:39.440
<v Speaker 1>the way it places its leg down, the way it

0:08:39.480 --> 0:08:42.559
<v Speaker 1>shifts its weight, it can maintain its relative position over

0:08:42.600 --> 0:08:44.320
<v Speaker 1>the ground. So it looks like if you if you

0:08:44.360 --> 0:08:47.640
<v Speaker 1>were to remove the legs magically from the image, like

0:08:47.679 --> 0:08:51.600
<v Speaker 1>it's just floating over the landscape. But it's all because

0:08:51.679 --> 0:08:53.679
<v Speaker 1>the way it's able to place its legs and move

0:08:53.720 --> 0:08:57.360
<v Speaker 1>its weight around. But legs, as it turns out, are

0:08:57.400 --> 0:09:01.559
<v Speaker 1>super hard to design. They require joints and points of articulation,

0:09:01.920 --> 0:09:04.000
<v Speaker 1>and you have to have power to move everything and

0:09:04.040 --> 0:09:07.760
<v Speaker 1>figure out how you're going to create the force necessary

0:09:07.800 --> 0:09:10.840
<v Speaker 1>to open and close those various joints, and you have

0:09:10.880 --> 0:09:13.680
<v Speaker 1>to have lots of precise directions to work effectively. So

0:09:13.720 --> 0:09:16.840
<v Speaker 1>you need a very efficient computer and you need really

0:09:16.840 --> 0:09:20.240
<v Speaker 1>good programming so that it can actually maneuver over these

0:09:20.280 --> 0:09:23.679
<v Speaker 1>different terrain. A leg needs to have more moving parts

0:09:23.720 --> 0:09:26.040
<v Speaker 1>than a wheel, with at least three actuators to make

0:09:26.080 --> 0:09:28.440
<v Speaker 1>the leg more useful than a wheel. You can have

0:09:28.520 --> 0:09:30.959
<v Speaker 1>fewer than three actuators and have a leg, but it's

0:09:30.960 --> 0:09:32.679
<v Speaker 1>not going to be more useful than a wheel unless

0:09:32.679 --> 0:09:36.000
<v Speaker 1>you have at least three actuators. So a lot of

0:09:36.000 --> 0:09:39.880
<v Speaker 1>the work in legged robots concentrates on how to move

0:09:40.000 --> 0:09:44.040
<v Speaker 1>those legs. So, for example, you might use artificial muscles

0:09:44.080 --> 0:09:48.280
<v Speaker 1>with stuff like electroactive polymers. Now, those are materials made

0:09:48.280 --> 0:09:51.040
<v Speaker 1>out of long chain molecules that change their shape when

0:09:51.080 --> 0:09:54.240
<v Speaker 1>they encounter an electric field. So here's an example, and

0:09:54.240 --> 0:09:56.000
<v Speaker 1>this is just one I pulled off the top of

0:09:56.040 --> 0:09:58.600
<v Speaker 1>my head, and it's not really indicative of how they

0:09:58.600 --> 0:10:01.280
<v Speaker 1>all work, but it's way they at work. Let's say

0:10:01.280 --> 0:10:03.760
<v Speaker 1>that you build a structure and it's made off of

0:10:03.760 --> 0:10:08.000
<v Speaker 1>this material, and that structure is elongated, it's extended, but

0:10:08.040 --> 0:10:11.400
<v Speaker 1>if it encounters an electric field, it contracts, it pulls together.

0:10:11.880 --> 0:10:14.040
<v Speaker 1>This would make it work in a way similar to

0:10:14.080 --> 0:10:18.480
<v Speaker 1>the way our muscles work. Now, there's not just that

0:10:18.600 --> 0:10:21.160
<v Speaker 1>kind of method to power legs. In fact, that's a

0:10:21.160 --> 0:10:25.280
<v Speaker 1>pretty rare one. You're more likely to find electric actuators

0:10:25.360 --> 0:10:29.319
<v Speaker 1>or hydraulic actuators. But that's another challenge is how do

0:10:29.360 --> 0:10:32.160
<v Speaker 1>you actually get the legs to move. Then there's a

0:10:32.200 --> 0:10:34.680
<v Speaker 1>ton of work on that processing side to calculate things

0:10:34.679 --> 0:10:38.959
<v Speaker 1>like balanced momentum, weight distribution, path finding, all of these

0:10:39.000 --> 0:10:42.640
<v Speaker 1>different things that we take for granted we learn it intuitively,

0:10:43.120 --> 0:10:47.080
<v Speaker 1>but that doesn't work with robots necessarily. And there's a

0:10:47.120 --> 0:10:50.199
<v Speaker 1>long history of studies that happened before robotics were even

0:10:50.240 --> 0:10:54.360
<v Speaker 1>a thing that would eventually inform the design of legged robots,

0:10:54.360 --> 0:10:57.600
<v Speaker 1>and some of those studies which went on to help

0:10:57.720 --> 0:11:00.960
<v Speaker 1>future engineers when they were building out these robot legs

0:11:01.000 --> 0:11:04.360
<v Speaker 1>for the first time. We're pretty grim, as it turns out.

0:11:04.760 --> 0:11:09.439
<v Speaker 1>So get ready for a gross story that I'm about

0:11:09.440 --> 0:11:13.320
<v Speaker 1>to tell you. One study that the Leg Lab cites

0:11:13.400 --> 0:11:16.720
<v Speaker 1>as being an important milestone in the development of legged

0:11:16.840 --> 0:11:21.960
<v Speaker 1>robots comes from an eighteen thirty six journal and it

0:11:22.000 --> 0:11:27.040
<v Speaker 1>involves dead people. The title of this study was Mechanic

0:11:27.360 --> 0:11:33.079
<v Speaker 1>derminsch lichen I and a Thomish physiologic unter schung fondap

0:11:33.120 --> 0:11:38.040
<v Speaker 1>rudin Wilhelm Weber w Edward web Webber. All right, so

0:11:38.120 --> 0:11:40.280
<v Speaker 1>translated to English because that was a terrible German, I know,

0:11:40.360 --> 0:11:44.840
<v Speaker 1>my German's awful kind of Deutsches. It turns out it

0:11:44.920 --> 0:11:49.040
<v Speaker 1>actually means the mechanics of the human and anatomical physiological

0:11:49.080 --> 0:11:53.120
<v Speaker 1>examination of the brothers Wilhelm and Edward Webber. Now their

0:11:53.120 --> 0:11:58.040
<v Speaker 1>work is available to read if you read German. But

0:11:58.200 --> 0:11:59.760
<v Speaker 1>they found that if you took the leg of a

0:12:00.000 --> 0:12:04.360
<v Speaker 1>corps and you swung the leg of the corpse, so

0:12:04.440 --> 0:12:08.920
<v Speaker 1>it acted like a compound pendulum. The swinging motion was

0:12:09.040 --> 0:12:10.959
<v Speaker 1>very similar to the cadence of a leg with a

0:12:10.960 --> 0:12:16.880
<v Speaker 1>live person is walking around. That's cheerful. But as it

0:12:16.920 --> 0:12:19.640
<v Speaker 1>turns out, that would actually be one of those fundamental

0:12:19.720 --> 0:12:22.800
<v Speaker 1>studies that would go on to inform people who were

0:12:22.840 --> 0:12:27.120
<v Speaker 1>trying to build artificial legs and mechanical legs. Most of

0:12:27.120 --> 0:12:30.560
<v Speaker 1>the studies the lab sites aren't nearly so grim and

0:12:30.640 --> 0:12:35.040
<v Speaker 1>don't involve nearly as many corpses. So for example, another

0:12:35.080 --> 0:12:38.800
<v Speaker 1>important contribution came from a guy named Edward Moybridge. Now

0:12:38.840 --> 0:12:42.400
<v Speaker 1>this was an English photographer who developed stop motion photography.

0:12:42.720 --> 0:12:46.199
<v Speaker 1>Moybridge was hired by a fat cat named Leland Stanford.

0:12:46.200 --> 0:12:49.600
<v Speaker 1>He was a former governor and a railroad tycoon and

0:12:49.640 --> 0:12:53.040
<v Speaker 1>Stanford had this idea, and he needed evidence to support

0:12:53.080 --> 0:12:56.760
<v Speaker 1>his idea. His idea was that when a horse is

0:12:56.800 --> 0:13:00.800
<v Speaker 1>in full gallop, at some point during its gait, it

0:13:00.840 --> 0:13:05.120
<v Speaker 1>will have all four hoofs off the ground simultaneously, and

0:13:05.240 --> 0:13:10.480
<v Speaker 1>moy Bridge was essentially contracted to prove that Stanford had

0:13:10.520 --> 0:13:13.320
<v Speaker 1>a leg to stand on as it were. So Moybridge

0:13:13.360 --> 0:13:16.320
<v Speaker 1>invented away to use a series of twelve cameras to

0:13:16.400 --> 0:13:19.200
<v Speaker 1>take photos with an exposure lasting only a fraction of

0:13:19.200 --> 0:13:21.800
<v Speaker 1>a second, which at the time it was pretty remarkable.

0:13:21.880 --> 0:13:26.280
<v Speaker 1>Most photo photography. Early photography had very long exposure time

0:13:26.400 --> 0:13:29.320
<v Speaker 1>in order to get enough light to actually create the effect,

0:13:29.640 --> 0:13:32.280
<v Speaker 1>which is why you have lots of portraits of very

0:13:32.400 --> 0:13:35.720
<v Speaker 1>dour looking people in early photography, because it meant they

0:13:35.760 --> 0:13:39.319
<v Speaker 1>had to sit still for several minutes at a time,

0:13:39.440 --> 0:13:41.440
<v Speaker 1>and you know, if you're trying to hold a smile,

0:13:42.360 --> 0:13:44.320
<v Speaker 1>pretty soon you hate the world and everything in it,

0:13:44.400 --> 0:13:47.200
<v Speaker 1>so you typically have these very kind of neutral or

0:13:47.240 --> 0:13:51.120
<v Speaker 1>dour expressions in those early photographs. Well, Moybridge wanted to

0:13:51.120 --> 0:13:53.000
<v Speaker 1>find a way of doing this much faster, so he

0:13:53.080 --> 0:13:55.839
<v Speaker 1>created this camera system where in a fraction of a

0:13:55.880 --> 0:13:58.400
<v Speaker 1>second it could expose film to enough light to create

0:13:58.400 --> 0:14:01.319
<v Speaker 1>an image. He said, twelve of these cameras in a row,

0:14:01.880 --> 0:14:04.680
<v Speaker 1>and then he used little trip wires not to trip

0:14:04.760 --> 0:14:07.000
<v Speaker 1>up the horses, but rather the wires themselves would trip

0:14:07.040 --> 0:14:09.880
<v Speaker 1>when a horse ran through them, and it would cause

0:14:09.920 --> 0:14:13.520
<v Speaker 1>the cameras to take these photos in sequence, and then

0:14:13.559 --> 0:14:16.480
<v Speaker 1>you could look at them and see a horse's gallop

0:14:16.760 --> 0:14:20.480
<v Speaker 1>in progress. The photos showed that Stanford was in fact correct.

0:14:20.600 --> 0:14:22.680
<v Speaker 1>There was a brief moment in the horse's stride in

0:14:22.720 --> 0:14:25.760
<v Speaker 1>which all four legs were off the ground, and Moybridge's

0:14:25.800 --> 0:14:29.520
<v Speaker 1>innovation became valuable for scientists who wanted to study animal movement,

0:14:29.960 --> 0:14:33.240
<v Speaker 1>and later for engineers and roboticists who wished to mimic

0:14:33.480 --> 0:14:38.040
<v Speaker 1>those movements when they were developing robotic legs. Uh, Moybridge

0:14:38.080 --> 0:14:41.160
<v Speaker 1>and stop motion animation and stop motion photography, I should say,

0:14:41.200 --> 0:14:44.000
<v Speaker 1>are really fascinating subjects, and I'm sure I'll cover them

0:14:44.000 --> 0:14:47.160
<v Speaker 1>in another episode of tech Stuff at some point. Back

0:14:47.200 --> 0:14:50.240
<v Speaker 1>to milestones, Well, there are a lot of others that

0:14:50.280 --> 0:14:52.760
<v Speaker 1>the lab acknowledgeist as being really important moments in the

0:14:52.760 --> 0:14:55.880
<v Speaker 1>development of robotic legs, and they even include a few

0:14:55.920 --> 0:14:59.280
<v Speaker 1>of Dr Rabur's contributions to the fields, such as three.

0:14:59.280 --> 0:15:03.400
<v Speaker 1>When Rayber build a one legged hopping machine, it could

0:15:03.440 --> 0:15:06.000
<v Speaker 1>keep its own balance and travel at a specified rate.

0:15:06.040 --> 0:15:08.920
<v Speaker 1>It kind of looks like a UFO on a pogo stick.

0:15:09.000 --> 0:15:13.520
<v Speaker 1>It's constantly bouncing around. The main trick here was just

0:15:13.600 --> 0:15:17.160
<v Speaker 1>getting that balance right. So Rayber was able to create

0:15:17.240 --> 0:15:20.840
<v Speaker 1>this robot that uses a computer that calculates where that

0:15:21.040 --> 0:15:23.960
<v Speaker 1>one foot needs to come down in order to keep

0:15:24.000 --> 0:15:27.680
<v Speaker 1>the overall robot balanced while still traveling in the desired direction.

0:15:28.560 --> 0:15:31.120
<v Speaker 1>Those calculations had to be done fast enough so that

0:15:31.200 --> 0:15:33.760
<v Speaker 1>they were complete before the robot would come crashing down

0:15:33.840 --> 0:15:36.400
<v Speaker 1>after its last hops. So as it hops up in

0:15:36.400 --> 0:15:38.720
<v Speaker 1>the air, the computer has to figure out the trajectory,

0:15:38.840 --> 0:15:42.320
<v Speaker 1>the momentum, all of these different elements that the robot

0:15:42.400 --> 0:15:46.680
<v Speaker 1>is experiencing in order to compensate with the leg so

0:15:46.760 --> 0:15:48.600
<v Speaker 1>that it can hit the ground at just the right

0:15:48.640 --> 0:15:50.720
<v Speaker 1>spot with just the right amount of force to propel

0:15:50.760 --> 0:15:53.720
<v Speaker 1>the robot up again and continue moving it in whatever

0:15:53.760 --> 0:15:57.080
<v Speaker 1>direction you wanted to go in. So it's actually pretty complicated,

0:15:57.120 --> 0:15:59.720
<v Speaker 1>It took a lot of work and it's pretty fascinating

0:15:59.720 --> 0:16:03.560
<v Speaker 1>stuff off. That basic principle would then later be adapted

0:16:03.560 --> 0:16:07.160
<v Speaker 1>and applied into multi legged robots with a computer determining

0:16:07.200 --> 0:16:09.720
<v Speaker 1>where each leg needs to go, how it needs to

0:16:09.760 --> 0:16:13.120
<v Speaker 1>make contact with the ground, how much force, all just

0:16:13.160 --> 0:16:16.920
<v Speaker 1>so that the robot doesn't fall over. Rayber would end

0:16:16.960 --> 0:16:20.760
<v Speaker 1>up writing a book about his research. In the book

0:16:20.800 --> 0:16:25.520
<v Speaker 1>has the title legged robots that Balance. Pretty much sums

0:16:25.600 --> 0:16:28.240
<v Speaker 1>up the whole thing, doesn't it. It sounds like it's

0:16:28.240 --> 0:16:30.960
<v Speaker 1>a trivial thing. But again, it was really tricky to

0:16:31.040 --> 0:16:35.200
<v Speaker 1>do because while we're growing up, most of us, you know,

0:16:35.240 --> 0:16:38.680
<v Speaker 1>as kids, we learned to walk, and we kind of

0:16:39.000 --> 0:16:42.040
<v Speaker 1>have an kind of intuitive grasp of what we need

0:16:42.080 --> 0:16:45.240
<v Speaker 1>to do in order to keep our balance barring any

0:16:45.920 --> 0:16:50.400
<v Speaker 1>unforeseen circumstances like stepping on something that is on uh

0:16:50.840 --> 0:16:54.040
<v Speaker 1>it's like uncertain ground without even realizing it, or getting

0:16:54.080 --> 0:16:57.240
<v Speaker 1>shoved by someone. We're pretty good at keeping our balance

0:16:57.360 --> 0:17:01.600
<v Speaker 1>generally speaking, assuming all things are you know, normal, But

0:17:01.640 --> 0:17:06.360
<v Speaker 1>a robot has to think air quotes, think about how

0:17:06.400 --> 0:17:09.080
<v Speaker 1>to do this. Intuition isn't an option, at least not

0:17:09.160 --> 0:17:13.080
<v Speaker 1>without some really advanced machine learning algorithms, which honestly, we're

0:17:13.119 --> 0:17:14.960
<v Speaker 1>not that far along. In the nineteen eighties, this was

0:17:15.000 --> 0:17:17.879
<v Speaker 1>all stuff that had to be worked out by human engineers.

0:17:18.359 --> 0:17:21.880
<v Speaker 1>These days if you created a really advanced machine learning algorithm,

0:17:22.000 --> 0:17:25.080
<v Speaker 1>I suppose it won't be long before we start seeing

0:17:25.160 --> 0:17:27.720
<v Speaker 1>robots that teach themselves how they need to walk. And

0:17:27.800 --> 0:17:31.000
<v Speaker 1>we've seen some examples of that, and they look really weird,

0:17:32.119 --> 0:17:35.159
<v Speaker 1>but these are mostly simulations, like we've seen computer simulations

0:17:35.160 --> 0:17:37.760
<v Speaker 1>of what it would look like, where there's a virtual

0:17:37.880 --> 0:17:43.199
<v Speaker 1>robot that has virtual statistics including its virtual weight and

0:17:43.359 --> 0:17:45.359
<v Speaker 1>height and all these sort of things that have real

0:17:45.440 --> 0:17:49.200
<v Speaker 1>world impact if you were to create an actual robot,

0:17:49.560 --> 0:17:51.960
<v Speaker 1>And then there are simulations that show how a computer

0:17:52.040 --> 0:17:54.320
<v Speaker 1>works out how this robot needs to move in order

0:17:54.359 --> 0:17:57.640
<v Speaker 1>to actually walk without falling over, and in some cases

0:17:57.960 --> 0:18:02.280
<v Speaker 1>the animations are hysterical and also nightmare inducing. But as

0:18:02.320 --> 0:18:04.680
<v Speaker 1>far as I know, we don't have any actual physical

0:18:04.800 --> 0:18:07.359
<v Speaker 1>robots that follow that model. I could be wrong about that.

0:18:07.400 --> 0:18:10.160
<v Speaker 1>By the way, there's advances in robotics all the time,

0:18:10.280 --> 0:18:13.040
<v Speaker 1>and they're very well. Maybe a project out there that's

0:18:13.119 --> 0:18:15.840
<v Speaker 1>much further along than what I'm suggesting, but the ones

0:18:16.000 --> 0:18:20.159
<v Speaker 1>I have seen of all been virtual representations rabs. Robots.

0:18:20.160 --> 0:18:24.440
<v Speaker 1>By the way, we're mostly dynamic robots, meaning they were

0:18:24.520 --> 0:18:27.120
<v Speaker 1>dynamic in the sense they needed to move in order

0:18:27.200 --> 0:18:32.760
<v Speaker 1>to remain stable. You could have static stable robots, but

0:18:32.800 --> 0:18:34.960
<v Speaker 1>these were ones that needed to move in order to

0:18:35.200 --> 0:18:39.240
<v Speaker 1>maintain that upright position and not just fall over. And

0:18:39.280 --> 0:18:42.680
<v Speaker 1>even some of those early robots, which often were tethered

0:18:42.920 --> 0:18:47.159
<v Speaker 1>to control and power systems, could do really amazing things.

0:18:47.280 --> 0:18:51.280
<v Speaker 1>So most of the early robots, if you see the

0:18:51.320 --> 0:18:54.480
<v Speaker 1>footage from Boston Dynamics, they have all these different cables

0:18:54.480 --> 0:18:57.360
<v Speaker 1>and stuff coming off of them. Those cables are frequently

0:18:57.400 --> 0:19:00.880
<v Speaker 1>going to power systems and to controls the dumbs. Because

0:19:00.920 --> 0:19:04.840
<v Speaker 1>the robots were meant to demonstrate specific types of locomotion,

0:19:04.880 --> 0:19:07.520
<v Speaker 1>they weren't going to be used as a finished product.

0:19:08.040 --> 0:19:10.679
<v Speaker 1>It was more about studying the way to build the

0:19:10.760 --> 0:19:14.639
<v Speaker 1>best systems, and so you didn't have to worry about

0:19:14.680 --> 0:19:16.920
<v Speaker 1>making something that was all self contained. You were studying

0:19:16.920 --> 0:19:19.199
<v Speaker 1>all of this in the lab anyway. So a lot

0:19:19.240 --> 0:19:21.480
<v Speaker 1>of those videos you'll see just have the this like

0:19:21.680 --> 0:19:26.040
<v Speaker 1>nest of chords that are grouped up over the robot

0:19:26.119 --> 0:19:29.040
<v Speaker 1>and go into some or you know, system or other

0:19:29.240 --> 0:19:34.000
<v Speaker 1>multiple systems in some cases. But even in those early robots,

0:19:34.040 --> 0:19:38.440
<v Speaker 1>there's some video clips of phenomenal robotic gymnastics, Like there's

0:19:38.440 --> 0:19:40.879
<v Speaker 1>somewhere engineers are controlling the robots and making them do

0:19:40.960 --> 0:19:44.160
<v Speaker 1>things like forward flips while traveling a path. I'm talking

0:19:44.160 --> 0:19:46.639
<v Speaker 1>about like hopping robots. They'll be hopping in a circle

0:19:47.119 --> 0:19:50.520
<v Speaker 1>and then they'll do an extra tall hop and do

0:19:50.600 --> 0:19:53.800
<v Speaker 1>a full forward flip and land on their foot and

0:19:53.920 --> 0:19:57.120
<v Speaker 1>catch their balance and continue going in the circle. This

0:19:57.160 --> 0:19:59.920
<v Speaker 1>is decades before we saw the viral clips of youtu

0:20:00.160 --> 0:20:03.879
<v Speaker 1>both Big Dog and the other famous robots from Boston Dynamics.

0:20:03.880 --> 0:20:07.239
<v Speaker 1>So if you get a chance, do some digging on

0:20:07.280 --> 0:20:09.840
<v Speaker 1>YouTube for Boston Dynamics and take a look at some

0:20:09.880 --> 0:20:13.440
<v Speaker 1>of those early videos, because they're really really impressive and

0:20:13.560 --> 0:20:18.439
<v Speaker 1>in some cases extremely creepy. Another Raybors contributions on the

0:20:18.480 --> 0:20:22.480
<v Speaker 1>list dates from when he and his team developed quadruped

0:20:22.600 --> 0:20:26.480
<v Speaker 1>robots that can move at different speeds like trotting, pacing,

0:20:26.560 --> 0:20:29.639
<v Speaker 1>and bounding, and they could switch between those different modes

0:20:29.720 --> 0:20:31.240
<v Speaker 1>so you didn't just have to turn it on and

0:20:31.240 --> 0:20:33.640
<v Speaker 1>then put it down on the ground. You could actually

0:20:33.800 --> 0:20:36.879
<v Speaker 1>go from one speed to the other and you know,

0:20:36.960 --> 0:20:39.520
<v Speaker 1>knock up a notch or down a notch. If you

0:20:39.560 --> 0:20:42.479
<v Speaker 1>watch slow motion footage of animals moving at different speeds,

0:20:42.480 --> 0:20:45.720
<v Speaker 1>you'll see that their legs move differently at each rate

0:20:45.720 --> 0:20:48.440
<v Speaker 1>of travel. So like a horse at a trot and

0:20:48.440 --> 0:20:50.679
<v Speaker 1>a horse at a gallop, their legs are behaving in

0:20:50.720 --> 0:20:53.200
<v Speaker 1>different ways. Well, Raybor was working very hard to create

0:20:53.280 --> 0:20:56.120
<v Speaker 1>the same sort of thing in his robots. So Rayber

0:20:56.200 --> 0:20:58.800
<v Speaker 1>and his team worked to push the envelope in the

0:20:58.800 --> 0:21:02.440
<v Speaker 1>field of robotic low emotion. They experimented with different designs

0:21:02.520 --> 0:21:05.440
<v Speaker 1>create more stable, capable robots, and many of those early

0:21:05.480 --> 0:21:09.040
<v Speaker 1>designs used humans to guide the path of the robots,

0:21:09.480 --> 0:21:13.440
<v Speaker 1>so it was kind of a partly human controlled, partly

0:21:13.560 --> 0:21:19.040
<v Speaker 1>robotic controlled system. Frequently, the robots themselves had computers, either

0:21:19.160 --> 0:21:21.600
<v Speaker 1>on board or just off board that did all the

0:21:21.640 --> 0:21:24.800
<v Speaker 1>actual work to determine the particulars like where does the

0:21:24.880 --> 0:21:28.080
<v Speaker 1>leg go and how would it need to shift its

0:21:28.119 --> 0:21:30.560
<v Speaker 1>weight in order to obey the commands. So the human

0:21:30.640 --> 0:21:32.960
<v Speaker 1>is essentially giving commands like I want you to move

0:21:33.040 --> 0:21:36.960
<v Speaker 1>over forward five feet, but it was the robots computer

0:21:37.080 --> 0:21:38.960
<v Speaker 1>that was actually doing the work of how does it

0:21:39.119 --> 0:21:43.399
<v Speaker 1>achieve that goal. In n Rayber founded a company to

0:21:43.440 --> 0:21:47.119
<v Speaker 1>continue this work and find commercial applications for the technologies

0:21:47.119 --> 0:21:51.639
<v Speaker 1>he was developing, and that company was Boston Dynamics. So

0:21:51.680 --> 0:21:54.800
<v Speaker 1>we're finally at the point where Boston Dynamics is its

0:21:54.840 --> 0:21:58.200
<v Speaker 1>own company, which means it's time to take a quick

0:21:58.200 --> 0:22:07.600
<v Speaker 1>break and thank our sponsor. All right, So it's the

0:22:07.600 --> 0:22:10.679
<v Speaker 1>early nine nineties and bust and Dynamics as a new company.

0:22:10.760 --> 0:22:14.760
<v Speaker 1>So do they start turning out commercial robots right away? Nope.

0:22:14.960 --> 0:22:16.600
<v Speaker 1>As a matter of fact, as of the recording of

0:22:16.640 --> 0:22:19.400
<v Speaker 1>this podcast, none of the company's work has ever been

0:22:19.400 --> 0:22:23.280
<v Speaker 1>turned into a commercial product. Directly, you cannot go out

0:22:23.320 --> 0:22:26.399
<v Speaker 1>and buy a Boston Dynamics robot for yourself. But the

0:22:26.400 --> 0:22:29.159
<v Speaker 1>company's work has been extremely important to push forward the

0:22:29.200 --> 0:22:32.560
<v Speaker 1>evolution of robotics, and there are some really big organizations

0:22:32.560 --> 0:22:35.760
<v Speaker 1>that have been extremely interested in that, such as the

0:22:35.800 --> 0:22:39.720
<v Speaker 1>Department of Defense. Now, much of Buston Dynamics funding has

0:22:39.760 --> 0:22:43.000
<v Speaker 1>come from really big contracts awarded to the company by

0:22:43.040 --> 0:22:47.760
<v Speaker 1>the Defense Advanced Research Projects Agency, also known as DARPA.

0:22:47.920 --> 0:22:50.160
<v Speaker 1>And you might remember DARPA as being the group responsible

0:22:50.200 --> 0:22:53.040
<v Speaker 1>for the Grand Challenge, in which self driving cars raced

0:22:53.080 --> 0:22:56.159
<v Speaker 1>through courses ranging from desert landscapes to a mock up

0:22:56.200 --> 0:22:58.400
<v Speaker 1>of a working city to see who could come out

0:22:58.440 --> 0:23:00.760
<v Speaker 1>on top. Or maybe you remember brit DARPA as the

0:23:00.800 --> 0:23:03.760
<v Speaker 1>agency which at the time was known as ARPA that

0:23:03.920 --> 0:23:06.879
<v Speaker 1>funded the development of technology that became the backbone of

0:23:06.920 --> 0:23:09.640
<v Speaker 1>the Internet. We wouldn't have the Internet as it stands

0:23:09.640 --> 0:23:11.760
<v Speaker 1>today without the R and D arm of the Department

0:23:11.760 --> 0:23:15.280
<v Speaker 1>of Defense. As it turns out, DARPA has been very

0:23:15.359 --> 0:23:18.919
<v Speaker 1>much interested in robotics, and the US Army, Navy, and

0:23:19.000 --> 0:23:22.639
<v Speaker 1>Marine Corps have similarly been interested in potential applications of

0:23:22.760 --> 0:23:26.199
<v Speaker 1>robots that are either inspired by man or beasts. So

0:23:26.280 --> 0:23:30.439
<v Speaker 1>Boston Dynamics has frequently operated as a research facility on

0:23:30.560 --> 0:23:35.119
<v Speaker 1>behalf of these organizations. Now. One of the earliest projects

0:23:35.119 --> 0:23:37.399
<v Speaker 1>that we ever got to hear about from Boston Dynamics

0:23:37.520 --> 0:23:42.000
<v Speaker 1>was Big Dog, dynamically stable four legged robot that debuted

0:23:42.040 --> 0:23:45.000
<v Speaker 1>in two thousand five. It was a predecessor of a

0:23:45.080 --> 0:23:49.760
<v Speaker 1>larger project titled Legged Squad Support System or LS three.

0:23:50.520 --> 0:23:54.480
<v Speaker 1>Boston Dynamics partnered with the Jet Propulsion Laboratory, the Concord

0:23:54.840 --> 0:23:58.080
<v Speaker 1>Field Station at Harvard University, and a robotics company called

0:23:58.119 --> 0:24:02.719
<v Speaker 1>Foster Miller on this The concept behind the design was

0:24:02.800 --> 0:24:05.240
<v Speaker 1>a robot that would be able to carry field equipment

0:24:05.280 --> 0:24:08.679
<v Speaker 1>in support of deployed military squads. So rather than load

0:24:08.720 --> 0:24:12.600
<v Speaker 1>down soldiers with dozens of pounds of gear, the robot

0:24:12.640 --> 0:24:14.600
<v Speaker 1>would be able to carry those loads and free up

0:24:14.640 --> 0:24:17.000
<v Speaker 1>the humans so they didn't have to tire so quickly

0:24:17.040 --> 0:24:21.120
<v Speaker 1>and they can move around with fewer restrictions. Dr Martin Bueller,

0:24:21.320 --> 0:24:25.080
<v Speaker 1>formerly of McGill University, led the Big Dog project. Dr

0:24:25.119 --> 0:24:28.040
<v Speaker 1>Bueller would be the Director of robotics Research at Boston

0:24:28.119 --> 0:24:30.960
<v Speaker 1>Dynamics from two thousand three to two thousand eight, but

0:24:31.000 --> 0:24:33.840
<v Speaker 1>would eventually move on to work for another corporation, one

0:24:33.880 --> 0:24:36.560
<v Speaker 1>called I Robot in two thousand and eight, and then

0:24:36.640 --> 0:24:39.520
<v Speaker 1>later on would move on to other projects. Big Dog

0:24:39.680 --> 0:24:44.479
<v Speaker 1>could carry forty or more than ninety pounds. The robot

0:24:44.520 --> 0:24:47.560
<v Speaker 1>itself weighed in at a hundred nine ms. It was

0:24:47.600 --> 0:24:52.040
<v Speaker 1>a meter tall, and it wasn't some battery operated robot. Instead,

0:24:52.119 --> 0:24:56.080
<v Speaker 1>it actually used a gasoline fueled engine. The joints used

0:24:56.160 --> 0:25:00.000
<v Speaker 1>hydraulic actuators, meaning the robot would use liquids under press

0:25:00.040 --> 0:25:03.080
<v Speaker 1>sure to extend limbs or reduce pressure to allow limbs

0:25:03.119 --> 0:25:07.720
<v Speaker 1>to contract to bend backward. For sensing its environment, Big

0:25:07.760 --> 0:25:11.000
<v Speaker 1>Dog also had stereo cameras so it could perceive depth,

0:25:11.400 --> 0:25:13.240
<v Speaker 1>and a light oar system to get an idea of

0:25:13.240 --> 0:25:16.560
<v Speaker 1>the orientation of various elements in an environment. Now, a

0:25:16.640 --> 0:25:19.480
<v Speaker 1>light OAR stands where light detection and ranging. Here's how

0:25:19.480 --> 0:25:22.720
<v Speaker 1>it works in a nutshell, a light ar detector has

0:25:22.800 --> 0:25:25.800
<v Speaker 1>two main components. First is an emitter or a light

0:25:25.800 --> 0:25:28.720
<v Speaker 1>gun of some sort, which shoots out light, typically in

0:25:28.760 --> 0:25:31.520
<v Speaker 1>the infrared range. The light shoots out from the emitter

0:25:31.640 --> 0:25:34.439
<v Speaker 1>until it hits some sort of object, and then some

0:25:34.560 --> 0:25:37.639
<v Speaker 1>of that light bounces back, and that's when light ars.

0:25:37.640 --> 0:25:41.000
<v Speaker 1>Second big component, a detector picks up the returning signals.

0:25:41.840 --> 0:25:44.760
<v Speaker 1>By doing some quick math, the lightar system can determine

0:25:44.800 --> 0:25:47.000
<v Speaker 1>how far away the object was based on the delay

0:25:47.080 --> 0:25:51.000
<v Speaker 1>between the emitted infrared light and then the detection of

0:25:51.000 --> 0:25:53.359
<v Speaker 1>the infrared light when it comes back. This is the

0:25:53.440 --> 0:25:56.800
<v Speaker 1>system used in modern speed guns. Oh and in a

0:25:56.840 --> 0:25:59.040
<v Speaker 1>speed gun, the emitter typically shoots out a burst of

0:25:59.080 --> 0:26:01.359
<v Speaker 1>these infrared way wives. So when the emitter picks up

0:26:01.400 --> 0:26:03.800
<v Speaker 1>the returning waves, it can look at the difference in

0:26:03.880 --> 0:26:07.720
<v Speaker 1>distances from the emitter and thus and for the speed

0:26:07.800 --> 0:26:10.000
<v Speaker 1>of the object that the gun was pointed at, such

0:26:10.000 --> 0:26:12.760
<v Speaker 1>as a super sweet red sports car, because we all

0:26:12.800 --> 0:26:15.959
<v Speaker 1>know the red ones go faster. This is also the

0:26:16.080 --> 0:26:20.199
<v Speaker 1>robot that could keep kicking and keep on ticking. I

0:26:20.240 --> 0:26:24.040
<v Speaker 1>guess anyway, there are many videos showing people giving big

0:26:24.080 --> 0:26:27.520
<v Speaker 1>Dog a let's call it a healthy shove with a

0:26:27.560 --> 0:26:30.760
<v Speaker 1>foot to throw the robot off balance. You've probably seen

0:26:30.800 --> 0:26:33.160
<v Speaker 1>one of these videos at least where there's this four

0:26:33.240 --> 0:26:37.399
<v Speaker 1>legged robot and some dude comes up, puts his foot

0:26:37.560 --> 0:26:39.200
<v Speaker 1>right up against the robot and gives us a big

0:26:39.200 --> 0:26:41.280
<v Speaker 1>old shove, and the robot just stumbles around for a

0:26:41.280 --> 0:26:43.720
<v Speaker 1>bit before picking itself back up. Now, the purpose of

0:26:43.720 --> 0:26:46.600
<v Speaker 1>those videos isn't a show that robots, hey, we're still

0:26:46.640 --> 0:26:49.480
<v Speaker 1>the boss of you, but rather to demonstrate the ability

0:26:49.480 --> 0:26:52.359
<v Speaker 1>of the robots to catch themselves even after they've been shoved,

0:26:52.359 --> 0:26:56.200
<v Speaker 1>and to regain their balance through careful, though sometimes seemingly

0:26:56.280 --> 0:27:00.679
<v Speaker 1>haphazard placement of their legs. Now doesn't work every time, no,

0:27:01.200 --> 0:27:04.560
<v Speaker 1>because terrain can be really unpredictable. Sometimes the robots best

0:27:04.560 --> 0:27:06.960
<v Speaker 1>efforts just aren't enough to keep it from toppling over.

0:27:07.400 --> 0:27:10.040
<v Speaker 1>But there are plenty of video examples of those robots,

0:27:10.320 --> 0:27:14.320
<v Speaker 1>which look fairly lifelike in their locomotion getting kicked before

0:27:14.320 --> 0:27:17.280
<v Speaker 1>regaining their footing. And it shouldn't come as any surprise

0:27:17.320 --> 0:27:20.120
<v Speaker 1>that the robots movements look lifelike since the engineers were

0:27:20.119 --> 0:27:23.919
<v Speaker 1>frequently relying upon animal movement as a model for robotic movement.

0:27:24.800 --> 0:27:27.280
<v Speaker 1>As for the l S three project, it added some

0:27:27.320 --> 0:27:30.600
<v Speaker 1>more requirements. This is the bigger version of Big Dog.

0:27:31.280 --> 0:27:34.200
<v Speaker 1>Sometimes they would call this Alpha Dog, and it could

0:27:34.240 --> 0:27:37.320
<v Speaker 1>carry up to a hundred two of gear for a

0:27:37.359 --> 0:27:40.880
<v Speaker 1>distance of thirty two kilometers or duration of twenty four hours.

0:27:41.359 --> 0:27:44.240
<v Speaker 1>According to Boston Dynamics, during one control test, it was

0:27:44.280 --> 0:27:49.160
<v Speaker 1>actually able to carry five hundreds of mass it's more

0:27:49.160 --> 0:27:53.280
<v Speaker 1>than a thousand pounds. It also could recognize a designated leader,

0:27:53.440 --> 0:27:56.359
<v Speaker 1>so an actual human being, and then follow behind that

0:27:56.480 --> 0:28:00.560
<v Speaker 1>specific person that leader without needing any other operators. On

0:28:00.680 --> 0:28:03.119
<v Speaker 1>top of the sensors that it had from its a

0:28:03.160 --> 0:28:07.199
<v Speaker 1>smaller cousin Big Dog, it also had GPS, so it

0:28:07.280 --> 0:28:11.040
<v Speaker 1>had some additional sensors inside of it. And ultimately, though

0:28:11.520 --> 0:28:14.000
<v Speaker 1>it wouldn't go very far beyond a few test missions

0:28:14.000 --> 0:28:18.679
<v Speaker 1>with the military. So the advances in robotics locomotion were considerable,

0:28:19.320 --> 0:28:21.959
<v Speaker 1>and there are many videos showing how impressive this robot

0:28:22.160 --> 0:28:24.520
<v Speaker 1>is and how it maneuvers across different types of terrain.

0:28:24.640 --> 0:28:27.480
<v Speaker 1>But it had a big, big problem, and that was

0:28:27.520 --> 0:28:31.439
<v Speaker 1>it was noisy. The robots gasoline engine created a huge

0:28:31.440 --> 0:28:34.119
<v Speaker 1>amount of noise, which meant that if you were a

0:28:34.160 --> 0:28:37.000
<v Speaker 1>military squad and you had one of these in your group,

0:28:38.200 --> 0:28:40.920
<v Speaker 1>your position would immediately be given away. There was nothing

0:28:40.960 --> 0:28:45.040
<v Speaker 1>stealthy about it. Boston Dynamics would create a smaller, battery

0:28:45.080 --> 0:28:49.400
<v Speaker 1>operated version of that robot called Spot, But spots problem

0:28:49.840 --> 0:28:53.600
<v Speaker 1>was not noise, it was just carrying capacity. It wasn't

0:28:53.640 --> 0:28:57.720
<v Speaker 1>as hefty, It wasn't as strong as Big Dog or

0:28:57.720 --> 0:29:00.240
<v Speaker 1>Alpha Dog. It could only carry forty pounds or about

0:29:00.240 --> 0:29:04.440
<v Speaker 1>eighteen kims, which wasn't really considered to be enough to

0:29:04.520 --> 0:29:07.600
<v Speaker 1>be useful to the military, so it was much more

0:29:07.680 --> 0:29:11.040
<v Speaker 1>quiet but had less utility. Both Big Dog and Spot

0:29:11.320 --> 0:29:14.560
<v Speaker 1>would come to an end. Their projects would end, sometimes

0:29:14.560 --> 0:29:17.560
<v Speaker 1>around two thousand and fifteen, but the progress made during

0:29:17.560 --> 0:29:19.720
<v Speaker 1>the design and build out of the robots would inform

0:29:19.800 --> 0:29:22.400
<v Speaker 1>future efforts at Boston Dynamics, So it wasn't like it

0:29:22.440 --> 0:29:26.080
<v Speaker 1>was a total loss or anything. The value was really

0:29:26.240 --> 0:29:30.280
<v Speaker 1>in the actual design and build out of these robots,

0:29:30.640 --> 0:29:33.840
<v Speaker 1>and that becomes a story, kind of exploratory research, kind

0:29:33.840 --> 0:29:38.160
<v Speaker 1>of story for Boston Dynamics throughout its entire existence. Another

0:29:38.280 --> 0:29:40.800
<v Speaker 1>robot that would come out of this effort would be

0:29:40.880 --> 0:29:44.560
<v Speaker 1>spot Many. This is a much more recent robot. It's

0:29:44.560 --> 0:29:48.400
<v Speaker 1>a smaller variation on that four legged design spot Many

0:29:48.440 --> 0:29:52.480
<v Speaker 1>debuted in two thousand seventeen, and it has a much

0:29:52.520 --> 0:29:54.840
<v Speaker 1>more friendly looking appearance. A lot of the you know,

0:29:54.880 --> 0:30:00.120
<v Speaker 1>Big Dog and Spot were kind of industrial and in

0:30:00.560 --> 0:30:02.920
<v Speaker 1>looks like they weren't they weren't meant to be pretty.

0:30:03.120 --> 0:30:05.480
<v Speaker 1>Spot Many has a little bit of a friendlier look

0:30:05.520 --> 0:30:08.640
<v Speaker 1>with some three D printed parts, and it makes a

0:30:08.640 --> 0:30:11.280
<v Speaker 1>little more sleek and it also has a nice bright

0:30:11.360 --> 0:30:15.920
<v Speaker 1>yellow color to the ones that are on the videos anyway, um,

0:30:15.960 --> 0:30:19.400
<v Speaker 1>and it's also smaller. Buston Dynamics called it their quietest

0:30:19.480 --> 0:30:22.000
<v Speaker 1>robot to date, and of course it operates on battery

0:30:22.040 --> 0:30:25.880
<v Speaker 1>power because hydraulics would be very loud and also unnecessarily

0:30:25.920 --> 0:30:28.800
<v Speaker 1>strong for such a small form factor. The robot moves

0:30:28.800 --> 0:30:31.760
<v Speaker 1>in a very fluid, organic way, and certain motions kind

0:30:31.760 --> 0:30:34.280
<v Speaker 1>of give off the illusion that it is actually alive,

0:30:34.720 --> 0:30:37.920
<v Speaker 1>but we have been assured by Boston Dynamics that as

0:30:37.960 --> 0:30:41.360
<v Speaker 1>not the case, so I'm gonna trust them. The robot

0:30:41.400 --> 0:30:45.160
<v Speaker 1>weighs as the base model, but you can also get

0:30:45.240 --> 0:30:48.520
<v Speaker 1>one while you can't. But the Boston Dynamics also makes

0:30:48.560 --> 0:30:53.040
<v Speaker 1>one that has an articulated arm that is mounted to

0:30:53.080 --> 0:30:55.240
<v Speaker 1>the top of the robot. So think of the robot

0:30:55.280 --> 0:30:57.880
<v Speaker 1>is like a platform. You've got four legs attached to

0:30:57.920 --> 0:31:00.800
<v Speaker 1>it on the top front part of it. You've also

0:31:00.800 --> 0:31:04.320
<v Speaker 1>got an articulated arm that can reach out and grab

0:31:04.440 --> 0:31:07.880
<v Speaker 1>stuff is on a joint, so it's like it's got

0:31:07.880 --> 0:31:11.080
<v Speaker 1>an elbow. And this adds an extra five kilograms to

0:31:11.120 --> 0:31:14.560
<v Speaker 1>the weight of the robot. And if you just take

0:31:14.600 --> 0:31:17.920
<v Speaker 1>a look at the design, the hand and arm makes

0:31:17.960 --> 0:31:19.840
<v Speaker 1>it look like it's kind of a head and neck

0:31:20.080 --> 0:31:22.080
<v Speaker 1>of an animal, so kind of like the spot Mini

0:31:22.200 --> 0:31:26.560
<v Speaker 1>is actually a tiny frisky a pedasaurus or something. According

0:31:26.560 --> 0:31:29.000
<v Speaker 1>to the company's spot Mini can prance around for about

0:31:29.120 --> 0:31:31.960
<v Speaker 1>ninety minutes before it needs a recharge, and it can

0:31:32.000 --> 0:31:36.160
<v Speaker 1>carry about fourteen kilograms of payload and has seventeen joints

0:31:36.160 --> 0:31:39.240
<v Speaker 1>of articulation. If you haven't seen videos of that thing

0:31:39.240 --> 0:31:41.040
<v Speaker 1>in motion, I highly recommend you check it out. They

0:31:41.040 --> 0:31:44.920
<v Speaker 1>are fascinating and again a little unnerving because you know,

0:31:45.120 --> 0:31:48.800
<v Speaker 1>they again are mocking organic creatures. So there's this sort

0:31:48.840 --> 0:31:54.200
<v Speaker 1>of kind of Uncanny Valley thing going on with these

0:31:54.320 --> 0:31:57.280
<v Speaker 1>robots that move like living things, but clearly are not

0:31:57.400 --> 0:32:00.560
<v Speaker 1>living things. There's also Little Dog, which is a much

0:32:00.600 --> 0:32:04.320
<v Speaker 1>smaller robot that Boston Dynamics created for DARPA. DARPA, in turn,

0:32:04.400 --> 0:32:07.840
<v Speaker 1>relies on Little Dog as a development platform for other

0:32:07.880 --> 0:32:10.360
<v Speaker 1>advances in the robotics. So if you've listened to my

0:32:10.400 --> 0:32:13.240
<v Speaker 1>other episodes that involved DARPA, you know that DARPA itself

0:32:13.280 --> 0:32:17.480
<v Speaker 1>does not conduct original research. Rather, it's an agency that

0:32:17.520 --> 0:32:20.560
<v Speaker 1>offers up funding to other companies and organizations to do

0:32:20.600 --> 0:32:23.560
<v Speaker 1>that kind of work, and that's in the interest of

0:32:23.560 --> 0:32:26.720
<v Speaker 1>the Department of Defense. Little Dogs Men is kind of

0:32:26.720 --> 0:32:30.320
<v Speaker 1>a standard platform upon which robotics organizations can develop new

0:32:30.360 --> 0:32:34.760
<v Speaker 1>technology for DARPA projects. So that might involve things like pathfinding,

0:32:35.080 --> 0:32:38.760
<v Speaker 1>object recognition, uh, you know that sort of stuff, things

0:32:38.840 --> 0:32:40.960
<v Speaker 1>that are maybe more on the software side of things

0:32:40.960 --> 0:32:44.280
<v Speaker 1>than the hardware side of things. Other four legged robots

0:32:44.280 --> 0:32:47.320
<v Speaker 1>built by Boston Dynamics include the Cheetah, which could hit

0:32:47.360 --> 0:32:49.480
<v Speaker 1>a top speed of twenty eight miles per hour that's

0:32:49.480 --> 0:32:52.600
<v Speaker 1>about forty five kilometers per hour. The Cheetah was not

0:32:52.800 --> 0:32:56.320
<v Speaker 1>built to run free across the landscape. It was running

0:32:56.360 --> 0:33:00.240
<v Speaker 1>on a treadmill. It actually had tethered power supply. Eye

0:33:00.240 --> 0:33:04.960
<v Speaker 1>tethered controls, so again, this wasn't a a all inclusive robot.

0:33:05.360 --> 0:33:07.880
<v Speaker 1>The purpose of the Cheetah was for robotics experts to

0:33:08.000 --> 0:33:11.720
<v Speaker 1>experiment with ways to build a fast moving robot. So again,

0:33:11.800 --> 0:33:14.080
<v Speaker 1>this was for them to kind of build out the

0:33:14.120 --> 0:33:18.600
<v Speaker 1>technologies that would then be incorporated into future designs, rather

0:33:18.640 --> 0:33:21.320
<v Speaker 1>than something that was its own self contained robot. So

0:33:21.400 --> 0:33:25.120
<v Speaker 1>again it kind of a development platform. Uh. It was

0:33:25.320 --> 0:33:28.080
<v Speaker 1>really fascinating to to watch though. It would run on

0:33:28.120 --> 0:33:31.520
<v Speaker 1>these treadmills at blistering speeds. You'd see this treadmill start

0:33:31.560 --> 0:33:34.320
<v Speaker 1>to ramp up, and at twenty eight miles per hour,

0:33:34.440 --> 0:33:37.959
<v Speaker 1>it meant that it was moving faster even than Hussain Bolt. However,

0:33:38.320 --> 0:33:43.360
<v Speaker 1>it couldn't balance itself, so unlike Hussain Bolt, you would

0:33:43.360 --> 0:33:46.280
<v Speaker 1>not be able to Like, it couldn't take a turn

0:33:46.360 --> 0:33:48.760
<v Speaker 1>to save its life. So if somehow one of these

0:33:48.880 --> 0:33:51.800
<v Speaker 1>Cheetah robots were to get after you, all you need

0:33:51.800 --> 0:33:55.760
<v Speaker 1>to do is take a left or right you'd be fine. Uh. Also,

0:33:55.840 --> 0:33:57.880
<v Speaker 1>it be tethered to a computer and probably couldn't move

0:33:57.960 --> 0:34:02.040
<v Speaker 1>very far, so you're probably fine either way. But that's

0:34:02.080 --> 0:34:05.760
<v Speaker 1>just one They did, however, use that design to build

0:34:05.760 --> 0:34:09.400
<v Speaker 1>out another four legged fast robot called the Wildcat. This

0:34:09.440 --> 0:34:13.759
<v Speaker 1>one was a self contained robot. Buston Dynamics showed off

0:34:13.760 --> 0:34:17.480
<v Speaker 1>the Wildcat robot in two thousand thirteen with videos of

0:34:17.520 --> 0:34:22.160
<v Speaker 1>this four legged robot bounding and galloping outside. It was

0:34:22.520 --> 0:34:24.560
<v Speaker 1>not tethered so it can run around and had a

0:34:24.600 --> 0:34:28.759
<v Speaker 1>gasoline engine very similar to Big Dog. Pretty loud, but

0:34:28.880 --> 0:34:31.200
<v Speaker 1>also pretty fast. It could get a top speed of

0:34:31.239 --> 0:34:34.200
<v Speaker 1>about sixteen miles per hour, so not quite as fast

0:34:34.200 --> 0:34:36.440
<v Speaker 1>as the Cheetah. If you are Hussain Bolt, you could

0:34:36.480 --> 0:34:41.480
<v Speaker 1>outrun this particular robot. If you are me, you would

0:34:41.560 --> 0:34:45.919
<v Speaker 1>be robot meat. I don't go faster than sixteen miles

0:34:45.920 --> 0:34:50.440
<v Speaker 1>per unless I'm either inside another vehicle or falling off

0:34:50.440 --> 0:34:53.879
<v Speaker 1>a cliff. There is another Cheetah robot by the way,

0:34:53.920 --> 0:34:57.800
<v Speaker 1>if you do searches for Cheetah robot, there's a different

0:34:57.800 --> 0:35:00.440
<v Speaker 1>one that comes out of the m I T Robotics apartment.

0:35:01.160 --> 0:35:04.040
<v Speaker 1>This one's a really cool robot. It's a four legged

0:35:04.120 --> 0:35:07.239
<v Speaker 1>robot that can detect and jump over obstacles. There's some

0:35:07.320 --> 0:35:12.120
<v Speaker 1>great videos of engineers showing it uh seeing an oncoming

0:35:12.120 --> 0:35:15.200
<v Speaker 1>obstacle on a treadmill and leaping over it. Even as

0:35:15.200 --> 0:35:17.600
<v Speaker 1>the obstacles grow taller and taller, it's still able to

0:35:17.640 --> 0:35:21.200
<v Speaker 1>get over them. It's an incredibly impressive robot, but it

0:35:21.320 --> 0:35:26.640
<v Speaker 1>is not a Boston Dynamics robot. Then there's Rise, which

0:35:26.680 --> 0:35:29.800
<v Speaker 1>is a wall climbing robot. This one has six legs

0:35:29.880 --> 0:35:32.560
<v Speaker 1>and it's pretty small. It's about nine point six inches

0:35:32.680 --> 0:35:36.640
<v Speaker 1>or long, has a tail like protrusion that makes it

0:35:36.680 --> 0:35:39.919
<v Speaker 1>look sort of like a robotic horseshoe crab, and each

0:35:40.000 --> 0:35:42.279
<v Speaker 1>leg has two joints, which means it has a total

0:35:42.320 --> 0:35:45.880
<v Speaker 1>of twelve actuated degrees of freedom. The feet have a

0:35:45.920 --> 0:35:49.759
<v Speaker 1>little micro claws on it, so it can grip to surfaces.

0:35:49.760 --> 0:35:52.759
<v Speaker 1>As long as the surface isn't completely smooth, it can

0:35:52.800 --> 0:35:55.480
<v Speaker 1>grip onto it and allow this little robot to climb

0:35:55.560 --> 0:35:58.720
<v Speaker 1>right up a vertical surface. On top of the normal

0:35:58.760 --> 0:36:02.120
<v Speaker 1>sensors that you would expect in any given robot, there

0:36:02.160 --> 0:36:04.440
<v Speaker 1>were some additional ones to ensure that it wouldn't take

0:36:04.480 --> 0:36:09.000
<v Speaker 1>an unplanned tumble, which included foot contact sensors so the

0:36:09.080 --> 0:36:11.759
<v Speaker 1>robot would actually know when its claws had been more

0:36:11.800 --> 0:36:15.200
<v Speaker 1>or less engaged in whatever surface it was climbing. They

0:36:15.239 --> 0:36:19.480
<v Speaker 1>also had legs strain sensors so if any legs were

0:36:20.760 --> 0:36:23.799
<v Speaker 1>having more strain on them than normal, it could either

0:36:23.920 --> 0:36:27.160
<v Speaker 1>redistribute its weight in an attempt to continue its climb,

0:36:27.320 --> 0:36:30.800
<v Speaker 1>or it could stop its climb rather than risking falling

0:36:30.840 --> 0:36:33.200
<v Speaker 1>off of its surface and allow someone to come up

0:36:33.200 --> 0:36:38.280
<v Speaker 1>and retrieve it. According to Boston Dynamics UH, this robot

0:36:38.320 --> 0:36:43.120
<v Speaker 1>could actually climb faster than an average human, and unlike humans,

0:36:43.120 --> 0:36:45.400
<v Speaker 1>it doesn't tire out, although it could run out a

0:36:45.400 --> 0:36:48.400
<v Speaker 1>battery charge, so that's sort of similar. And this was

0:36:48.440 --> 0:36:51.920
<v Speaker 1>not built for a specific purpose. It was more like

0:36:52.640 --> 0:36:57.640
<v Speaker 1>building out capabilities of robots with the ultimate goal of

0:36:57.680 --> 0:37:00.239
<v Speaker 1>creating robots that could be useful for people like first

0:37:00.280 --> 0:37:06.760
<v Speaker 1>responders in various UH emergencies. So there wasn't a specific mission,

0:37:07.120 --> 0:37:09.600
<v Speaker 1>but it was more about let's build out these capabilities

0:37:09.640 --> 0:37:12.560
<v Speaker 1>that could come in handy in future robotic designs. I

0:37:12.640 --> 0:37:15.440
<v Speaker 1>got a lot more to say about Boston Dynamics, but

0:37:15.520 --> 0:37:18.040
<v Speaker 1>before I get into this final segment, let's take another

0:37:18.120 --> 0:37:27.640
<v Speaker 1>quick break to thank our sponsor. Okay, so let's talk

0:37:27.680 --> 0:37:30.759
<v Speaker 1>about a couple more robots before we get into some

0:37:30.960 --> 0:37:35.719
<v Speaker 1>interesting recent stories involving Boston Dynamics. There was also a

0:37:35.840 --> 0:37:39.920
<v Speaker 1>robot called Rex and that's spelled r h e X.

0:37:40.000 --> 0:37:42.600
<v Speaker 1>That's a six legged robot designed to be able to

0:37:42.640 --> 0:37:46.680
<v Speaker 1>tackle particularly tough terrain. It's not a big robot. It

0:37:46.960 --> 0:37:50.400
<v Speaker 1>is about fourteen centimeters tall, so it doesn't exactly tower

0:37:50.520 --> 0:37:53.799
<v Speaker 1>above the landscape, but it's curved legs could propel it

0:37:53.840 --> 0:37:56.840
<v Speaker 1>over lots of different surfaces better than robots much larger

0:37:56.880 --> 0:38:00.200
<v Speaker 1>than itself. It relied on TELA operations, which means you know,

0:38:00.280 --> 0:38:03.480
<v Speaker 1>someone's controlling it remotely using a camera to get a

0:38:03.560 --> 0:38:05.720
<v Speaker 1>robot's eye view of what was in front of the critter.

0:38:06.200 --> 0:38:09.279
<v Speaker 1>The legs rotate kind of like wheels, so they're these

0:38:09.280 --> 0:38:12.320
<v Speaker 1>sort of semi circular legs. They don't make a full circle,

0:38:12.640 --> 0:38:15.839
<v Speaker 1>but they do rotate around and they can go through

0:38:15.920 --> 0:38:18.760
<v Speaker 1>pretty much anything like that shows robots going through mud

0:38:18.760 --> 0:38:22.200
<v Speaker 1>and water, and because it's a fully sealed robot, it

0:38:22.239 --> 0:38:24.680
<v Speaker 1>doesn't you know, it's not in danger of having water,

0:38:25.239 --> 0:38:28.480
<v Speaker 1>give it any short circuits or anything like that, no disassemble.

0:38:28.920 --> 0:38:33.760
<v Speaker 1>It can go over rocks and twigs and even logs

0:38:33.800 --> 0:38:36.319
<v Speaker 1>and stuff. So it's a pretty interesting and robust looking

0:38:36.360 --> 0:38:39.360
<v Speaker 1>little critter. And again it's sort of a proof of

0:38:39.440 --> 0:38:42.680
<v Speaker 1>concept of technologies that could be used in future robots.

0:38:42.960 --> 0:38:46.239
<v Speaker 1>There's also sand Flea, which is a wheeled robot, an

0:38:46.320 --> 0:38:51.000
<v Speaker 1>unusual thing for Boston Dynamic or Boston Dynamics, I should say.

0:38:51.480 --> 0:38:53.840
<v Speaker 1>It can jump actually, so it's a wheeled robot, but

0:38:53.840 --> 0:38:56.759
<v Speaker 1>it can also leap into the air to the tune

0:38:56.800 --> 0:39:00.000
<v Speaker 1>of about thirty feet in the air. It uses gyroscope

0:39:00.000 --> 0:39:04.000
<v Speaker 1>hopes to maintain its orientation during jumps so it doesn't

0:39:04.040 --> 0:39:06.839
<v Speaker 1>just tumble to the ground and you know, crash into

0:39:06.880 --> 0:39:08.520
<v Speaker 1>lots of little bit so it can actually land on

0:39:08.520 --> 0:39:11.440
<v Speaker 1>its wheels properly and then jump again. There's some great

0:39:11.560 --> 0:39:14.800
<v Speaker 1>footage of it jumping from the ground onto the top

0:39:14.880 --> 0:39:17.799
<v Speaker 1>of a building that I was really impressed by, so

0:39:17.840 --> 0:39:20.000
<v Speaker 1>you should check that out to sand Flea is the

0:39:20.080 --> 0:39:22.360
<v Speaker 1>name of that one. Then we get to the humanoid

0:39:22.480 --> 0:39:26.040
<v Speaker 1>robots that Boston Dynamics has built. Now, the ones I've

0:39:26.080 --> 0:39:29.239
<v Speaker 1>mentioned earlier were mostly based off of animal designs, with

0:39:29.360 --> 0:39:31.880
<v Speaker 1>that exception of sand Flea because that's a wheeled robot.

0:39:32.239 --> 0:39:34.600
<v Speaker 1>But these are all bipedal machines that I'm going to

0:39:34.680 --> 0:39:38.680
<v Speaker 1>talk about at this point. First, there's the Protection Ensemble

0:39:38.880 --> 0:39:42.880
<v Speaker 1>Test mannequin, also known as pet Man. This is an

0:39:42.880 --> 0:39:47.360
<v Speaker 1>anthropomorphic robot that's pretty basic. Its movements were largely influenced

0:39:47.360 --> 0:39:50.360
<v Speaker 1>by the work done on the Big Dog project. In

0:39:50.400 --> 0:39:54.640
<v Speaker 1>other words, it lumbers around a little bit. It when

0:39:54.640 --> 0:39:58.080
<v Speaker 1>it's not wearing anything, it does not look terribly human.

0:39:58.120 --> 0:40:01.400
<v Speaker 1>I mean, it's basic human shape that's got legs and arms.

0:40:02.120 --> 0:40:04.680
<v Speaker 1>But it does important work for humans, and that is

0:40:04.719 --> 0:40:07.400
<v Speaker 1>to test out chemical protection suits to make sure they

0:40:07.400 --> 0:40:10.960
<v Speaker 1>are of suitable durability for use by real, live human beings.

0:40:11.960 --> 0:40:15.359
<v Speaker 1>So a suit might protect against chemicals when it's nice

0:40:15.360 --> 0:40:17.160
<v Speaker 1>and new and when it's just kind of folded up,

0:40:17.760 --> 0:40:20.480
<v Speaker 1>But on the real world, a suit's gonna be exposed

0:40:20.480 --> 0:40:24.280
<v Speaker 1>to stresses and wear and tear, and so pet Man

0:40:24.400 --> 0:40:27.920
<v Speaker 1>could simulate that by moving around while a suit is

0:40:27.960 --> 0:40:30.080
<v Speaker 1>actually on the device. It would be wearing one of

0:40:30.080 --> 0:40:33.440
<v Speaker 1>these chemical protection suits, and it could test the durability

0:40:33.440 --> 0:40:36.479
<v Speaker 1>of the suit and actually even do this while being

0:40:36.520 --> 0:40:41.479
<v Speaker 1>exposed to different types of stresses like temperature changes or

0:40:41.520 --> 0:40:45.320
<v Speaker 1>even chemicals. You could spray chemicals on this thing, because

0:40:45.840 --> 0:40:47.640
<v Speaker 1>it's a robot, you know, you wouldn't want to do

0:40:47.680 --> 0:40:49.560
<v Speaker 1>that to a real human. You'd put them to way

0:40:49.640 --> 0:40:53.720
<v Speaker 1>too much risk. If in fact, the chemical resistance suit

0:40:53.840 --> 0:40:57.000
<v Speaker 1>didn't live up to its design, but with a robot,

0:40:57.040 --> 0:40:59.640
<v Speaker 1>you don't have to worry about that, So that's exactly

0:40:59.760 --> 0:41:02.440
<v Speaker 1>what they would use it for. It's kind of kind

0:41:02.440 --> 0:41:06.120
<v Speaker 1>of interesting. Um and it's also fun to watch videos

0:41:06.160 --> 0:41:08.799
<v Speaker 1>of it wearing the suits because then it just looks

0:41:08.800 --> 0:41:13.160
<v Speaker 1>like a It kind of looks like a slasher movie monster,

0:41:13.320 --> 0:41:18.000
<v Speaker 1>like Jason or Mike Myers, Mike Wires. That's just this big,

0:41:18.120 --> 0:41:23.240
<v Speaker 1>lumbering hulk of a thing and uh typically camouflage chemical suits.

0:41:23.520 --> 0:41:28.400
<v Speaker 1>It's kind of terrifying. Then there's Atlas, the agile anthropomorphic robot.

0:41:28.520 --> 0:41:32.480
<v Speaker 1>The first generation of Atlas was a pretty monstrous beast itself.

0:41:32.520 --> 0:41:36.880
<v Speaker 1>It measured six ft tall uh three centimeters in other words,

0:41:37.040 --> 0:41:40.480
<v Speaker 1>and waited a hundred fifty ms or three thirty pounds.

0:41:41.520 --> 0:41:44.640
<v Speaker 1>It's sensor's range finders and optical cameras communicated with a

0:41:44.640 --> 0:41:48.120
<v Speaker 1>computer that was separate from the robot itself in the

0:41:48.160 --> 0:41:51.960
<v Speaker 1>original prototype model, so in other words, all the computational

0:41:51.960 --> 0:41:56.320
<v Speaker 1>stuff was offloaded onto a nearby unit. According to Boston Dynamics,

0:41:56.680 --> 0:41:59.160
<v Speaker 1>the robot had a total of twenty eight degrees of

0:41:59.239 --> 0:42:02.520
<v Speaker 1>freedom when you added up all of its various actuated joints.

0:42:02.800 --> 0:42:06.160
<v Speaker 1>The earliest version required a tethered power supply, and then

0:42:06.280 --> 0:42:09.000
<v Speaker 1>later builds would incorporate the power onto the robot itself,

0:42:09.440 --> 0:42:11.719
<v Speaker 1>and its movement was largely based off the results of

0:42:11.760 --> 0:42:15.360
<v Speaker 1>developing pet Man. So while pet Man was kind of

0:42:15.360 --> 0:42:18.200
<v Speaker 1>an evolution of the work that was done on Big Dog,

0:42:18.880 --> 0:42:20.799
<v Speaker 1>Atlas was an evolution of the work that was done

0:42:20.800 --> 0:42:23.719
<v Speaker 1>on pet Man. And Atlas could do some pretty cool stuff.

0:42:23.719 --> 0:42:26.800
<v Speaker 1>It could balance on one leg, which is really remarkable

0:42:26.800 --> 0:42:29.960
<v Speaker 1>when you think about how big this thing was, and

0:42:30.000 --> 0:42:34.200
<v Speaker 1>also it could recover from being shoved uh or sometimes

0:42:34.280 --> 0:42:36.160
<v Speaker 1>it could. Other times it would lose its balance and

0:42:36.200 --> 0:42:40.719
<v Speaker 1>unpredictably fall over, sometimes without even being shoved. First, it

0:42:40.760 --> 0:42:43.279
<v Speaker 1>was that generation of Atlas that would be featured in

0:42:43.320 --> 0:42:47.000
<v Speaker 1>the Team DARPA Robotics Challenge. I did a full episode

0:42:47.400 --> 0:42:51.120
<v Speaker 1>about the Robotics Challenge, but I would give a quick summary. Here.

0:42:52.160 --> 0:42:54.359
<v Speaker 1>You had a bunch of teams that were competing in

0:42:54.400 --> 0:42:57.719
<v Speaker 1>designing a robotics solution to a series of problems that

0:42:57.800 --> 0:43:00.440
<v Speaker 1>simulated the sorts of task a robot might have to

0:43:00.480 --> 0:43:03.640
<v Speaker 1>complete in the wake of a disaster. The inspiration for

0:43:03.760 --> 0:43:07.680
<v Speaker 1>the challenge was a real world disaster The Fukushima nuclear

0:43:07.719 --> 0:43:11.400
<v Speaker 1>reactors when they malfunctioned after its tsunami um It was

0:43:11.520 --> 0:43:14.080
<v Speaker 1>very dangerous to send people into that area, but a

0:43:14.200 --> 0:43:17.560
<v Speaker 1>robot would be a much better choice. So this was

0:43:17.640 --> 0:43:20.319
<v Speaker 1>kind of a challenge to see if any teams could

0:43:20.360 --> 0:43:23.680
<v Speaker 1>design robotics platforms that could respond to the sort of

0:43:23.680 --> 0:43:27.080
<v Speaker 1>things that would be necessary in another disaster of that caliber.

0:43:28.040 --> 0:43:30.120
<v Speaker 1>So the robots would have to operate a vehicle, a

0:43:30.200 --> 0:43:32.839
<v Speaker 1>human powered vehicle, typically not a human power, but human

0:43:32.880 --> 0:43:36.040
<v Speaker 1>operated vehicle, to a specific destination, so in other words,

0:43:36.160 --> 0:43:38.880
<v Speaker 1>like a golf cart. They'd have to drive this themselves,

0:43:39.600 --> 0:43:43.000
<v Speaker 1>get out of that vehicle, open a door, walk through

0:43:43.000 --> 0:43:46.360
<v Speaker 1>a doorway, and then complete several other challenges, including the

0:43:46.360 --> 0:43:49.760
<v Speaker 1>operation of a handheld power tool. At one point, six

0:43:49.880 --> 0:43:53.399
<v Speaker 1>of the competing teams would use the Atlas robot as

0:43:53.400 --> 0:43:58.000
<v Speaker 1>their robotics platform. Other teams would rely on different humanoid robots,

0:43:58.040 --> 0:44:01.160
<v Speaker 1>so they weren't required to use Atlas, but six teams

0:44:01.200 --> 0:44:04.000
<v Speaker 1>did use Atlas. The nature of the challenges meant that

0:44:04.040 --> 0:44:06.480
<v Speaker 1>the robot would have to simulate human activities, and the

0:44:06.480 --> 0:44:09.880
<v Speaker 1>winning team, Team KIST, used a robot called Hubo, so

0:44:09.960 --> 0:44:12.560
<v Speaker 1>it was not an Atlas. There are a lot of

0:44:12.640 --> 0:44:15.879
<v Speaker 1>videos of the competition out there, including some of the

0:44:15.960 --> 0:44:20.799
<v Speaker 1>various Atlas robots. There are also some great videos of

0:44:20.880 --> 0:44:24.680
<v Speaker 1>heartbreaking and occasionally incredibly funny moments of robots falling over

0:44:24.719 --> 0:44:27.640
<v Speaker 1>while trying to do seemingly simple things like walk through

0:44:27.680 --> 0:44:31.960
<v Speaker 1>a doorway. As it turns out, that's a lot trickier

0:44:31.960 --> 0:44:35.480
<v Speaker 1>than it sounds. In two thousand and sixteen, Boston Dynamics

0:44:35.520 --> 0:44:38.760
<v Speaker 1>unveiled a second generation of Atlas robots that looked slightly

0:44:38.840 --> 0:44:42.600
<v Speaker 1>less industrial and had more advanced sensors for navigation and

0:44:42.680 --> 0:44:47.160
<v Speaker 1>orientation purposes, as well as more advanced maneuverability technology. It

0:44:47.239 --> 0:44:50.640
<v Speaker 1>could walk on surfaces like snow, and even planned paths

0:44:50.640 --> 0:44:54.239
<v Speaker 1>in areas where other objects are currently in motion. This

0:44:54.280 --> 0:44:57.360
<v Speaker 1>one was a seventy five tall, so a little shorter.

0:44:57.600 --> 0:45:01.359
<v Speaker 1>That's about five ft nine inches tall. It two ms

0:45:01.480 --> 0:45:03.880
<v Speaker 1>or around a d eighty pounds, a little you know,

0:45:04.840 --> 0:45:09.000
<v Speaker 1>significantly lighter than three pounds. Boston Dynamics has credited three

0:45:09.080 --> 0:45:12.360
<v Speaker 1>D printing for the drastic reduction in weight and size,

0:45:13.440 --> 0:45:16.719
<v Speaker 1>and there's an even smaller, lighter, and more capable generation

0:45:16.719 --> 0:45:22.040
<v Speaker 1>of Atlas the debuted in late Boston Dynamics posted a

0:45:22.120 --> 0:45:24.520
<v Speaker 1>video of it showing this robot in action. It could

0:45:24.600 --> 0:45:27.680
<v Speaker 1>jump up on boxes, so it could walk up to

0:45:27.920 --> 0:45:31.200
<v Speaker 1>an obstacle like a box, judge how tall it was,

0:45:31.320 --> 0:45:34.719
<v Speaker 1>and then jump so that it landed and maintained its

0:45:34.719 --> 0:45:37.040
<v Speaker 1>balance on top of the box. It could even do

0:45:37.120 --> 0:45:39.640
<v Speaker 1>a full back flip off a box and land on

0:45:39.680 --> 0:45:42.879
<v Speaker 1>the ground, regaining its balance so it doesn't even tip over,

0:45:43.600 --> 0:45:45.839
<v Speaker 1>which is an incredible thing to see. If you haven't

0:45:45.840 --> 0:45:49.239
<v Speaker 1>watched that video, you should definitely find that one. And

0:45:49.320 --> 0:45:52.759
<v Speaker 1>that brings us to handle a robot that seems to

0:45:52.840 --> 0:45:56.080
<v Speaker 1>look like kind of like a bucking horse on roller skates.

0:45:56.080 --> 0:45:57.840
<v Speaker 1>I've seen other people refer to it as kind of

0:45:57.880 --> 0:46:01.280
<v Speaker 1>like a donkey on roller skates. It's a bipedal robot,

0:46:01.640 --> 0:46:05.000
<v Speaker 1>but it's lower legs don't end in feet, they end

0:46:05.040 --> 0:46:07.239
<v Speaker 1>in wheels, so it has two wheels at its base,

0:46:07.320 --> 0:46:09.399
<v Speaker 1>kind of like a segue, and it uses that same

0:46:09.440 --> 0:46:13.879
<v Speaker 1>sort of technology to maintain its upright position. Has two

0:46:13.960 --> 0:46:16.640
<v Speaker 1>upper limbs that can pick up and carry objects weighing

0:46:16.719 --> 0:46:20.680
<v Speaker 1>up to and the robot is two meters tall, weighs

0:46:20.680 --> 0:46:24.120
<v Speaker 1>a hundred and five kilograms, and has ten actuated joints.

0:46:24.640 --> 0:46:27.279
<v Speaker 1>It uses battery power and a combination of hydraulic and

0:46:27.320 --> 0:46:31.600
<v Speaker 1>electric actuators to actually work those limbs, and has depth

0:46:31.640 --> 0:46:35.120
<v Speaker 1>cameras to provide perception. It can speed along the ground

0:46:35.200 --> 0:46:39.279
<v Speaker 1>and even jump up onto higher surfaces. One demonstration, there's

0:46:39.320 --> 0:46:41.080
<v Speaker 1>a video that you can watch of this as well.

0:46:41.560 --> 0:46:44.480
<v Speaker 1>It will show the robot rolling toward a table and

0:46:44.520 --> 0:46:47.400
<v Speaker 1>then the last second it jumps up and lands on

0:46:47.440 --> 0:46:51.080
<v Speaker 1>the table surface, rolls across the table before landing on

0:46:51.080 --> 0:46:54.520
<v Speaker 1>the other side and continuing on. It's pretty impressive, and

0:46:54.600 --> 0:46:57.200
<v Speaker 1>Boston Dynamics has also pointed out that because it only

0:46:57.239 --> 0:47:01.839
<v Speaker 1>has ten actuated joints, it's far less complex than some

0:47:01.920 --> 0:47:05.319
<v Speaker 1>other models, and that uh that reduction in complexity could

0:47:05.320 --> 0:47:09.000
<v Speaker 1>mean a reduction in cost as well. The wheels work

0:47:09.040 --> 0:47:12.560
<v Speaker 1>on most services until you get into some really difficult terrain,

0:47:13.040 --> 0:47:15.080
<v Speaker 1>and I find it fascinating that a company that had

0:47:15.120 --> 0:47:19.440
<v Speaker 1>made its name from mostly legged robot designs had gone

0:47:19.520 --> 0:47:23.239
<v Speaker 1>with this hybrid approach. But the videos show that the

0:47:23.280 --> 0:47:27.040
<v Speaker 1>design is pretty effective, at least for specific applications. Now,

0:47:27.080 --> 0:47:30.400
<v Speaker 1>one thing I have not really covered in this episode

0:47:31.000 --> 0:47:34.920
<v Speaker 1>is who owns Boston Dynamics these days, because that's actually

0:47:35.000 --> 0:47:37.120
<v Speaker 1>changed a couple of times over the past few years.

0:47:37.120 --> 0:47:39.640
<v Speaker 1>It operated as an independent company for more than a

0:47:39.640 --> 0:47:41.719
<v Speaker 1>couple of well a couple of decades, and then on

0:47:41.760 --> 0:47:46.600
<v Speaker 1>December thirteen, the top secret R and D branch of Google,

0:47:47.160 --> 0:47:49.839
<v Speaker 1>known as Google X and these days just called X

0:47:50.120 --> 0:47:54.560
<v Speaker 1>acquired Boston Dynamics um as X it is now a

0:47:54.600 --> 0:47:59.040
<v Speaker 1>subsidiary company of Google's parent company, alphabet So. At the time,

0:47:59.120 --> 0:48:01.560
<v Speaker 1>it was a division under Google. Now it's its own

0:48:01.600 --> 0:48:05.440
<v Speaker 1>spin off company called x SO. Boston Dynamics was just

0:48:05.600 --> 0:48:09.960
<v Speaker 1>one of nine robotics companies that Google acquired around that time,

0:48:10.200 --> 0:48:13.680
<v Speaker 1>and the co founder of Android, Andy Reuben, was slated

0:48:13.680 --> 0:48:16.160
<v Speaker 1>to take the helm of all nine companies under a

0:48:16.160 --> 0:48:21.200
<v Speaker 1>new robotics division that was called Replicant, which isn't terrifying

0:48:21.239 --> 0:48:25.120
<v Speaker 1>at all thanks a lot Blade Runner well. According to Reuben,

0:48:25.920 --> 0:48:28.520
<v Speaker 1>the initial plan was to have those companies do their

0:48:28.520 --> 0:48:31.640
<v Speaker 1>own thing, working on research the way they normally would

0:48:31.719 --> 0:48:34.400
<v Speaker 1>and advancing the art and science of robotics, so in

0:48:34.440 --> 0:48:37.640
<v Speaker 1>other words, there wouldn't be any pressure to develop commercial

0:48:37.640 --> 0:48:40.520
<v Speaker 1>products right out of the gate. Instead, they would just

0:48:40.520 --> 0:48:43.759
<v Speaker 1>do exploratory research and the advances in the field would

0:48:43.800 --> 0:48:47.040
<v Speaker 1>guide Google's decisions on how to leverage those developments in

0:48:47.160 --> 0:48:52.720
<v Speaker 1>commercial applications. But in October, Andy Reuben would leave Google.

0:48:53.280 --> 0:48:56.480
<v Speaker 1>Now Reuben reportedly left to found a new company to

0:48:56.520 --> 0:48:59.400
<v Speaker 1>act as an incubator for technology hardware products. So, in

0:48:59.440 --> 0:49:01.359
<v Speaker 1>other words, he wanted to build a company that would

0:49:01.400 --> 0:49:04.799
<v Speaker 1>help hardware developers get to market with their ideas. That

0:49:04.840 --> 0:49:10.560
<v Speaker 1>company is called Essential. But later in information would leak

0:49:10.600 --> 0:49:14.640
<v Speaker 1>that Reuben had apparently or allegedly i should say, left

0:49:14.680 --> 0:49:18.799
<v Speaker 1>Google after a one of his employees, a woman, had

0:49:18.840 --> 0:49:23.360
<v Speaker 1>filed a complaint to human resources about Reuben having an

0:49:23.400 --> 0:49:28.800
<v Speaker 1>inappropriate relationship in the workplace. Now, Reuben's spokesperson over it

0:49:28.960 --> 0:49:32.600
<v Speaker 1>Essential says that this report is misleading, that Reuben had

0:49:32.640 --> 0:49:36.279
<v Speaker 1>never engaged in any misconduct at Google, that any relationships

0:49:36.280 --> 0:49:39.880
<v Speaker 1>he had at Google were consensual, uh, and that there

0:49:39.920 --> 0:49:43.840
<v Speaker 1>were no other issues there. But whatever the case, Reuben

0:49:43.920 --> 0:49:46.680
<v Speaker 1>took a leave of absence at Essential to deal with

0:49:46.760 --> 0:49:50.319
<v Speaker 1>quote personal matters in the quote. So back to the

0:49:50.400 --> 0:49:55.200
<v Speaker 1>robotics companies under X. So Reuben leaves the company, and

0:49:55.360 --> 0:49:58.640
<v Speaker 1>there was kind of a vacuuman leadership at that part

0:49:58.719 --> 0:50:01.000
<v Speaker 1>of Google, and the is a lot of confusion about

0:50:01.040 --> 0:50:03.040
<v Speaker 1>what was going to happen after all these companies had

0:50:03.080 --> 0:50:05.799
<v Speaker 1>been told that they were going to continue operating as normal,

0:50:05.960 --> 0:50:11.960
<v Speaker 1>really doing this exploratory research. But in Google management attempted

0:50:11.960 --> 0:50:14.960
<v Speaker 1>to put some sort of leadership and structure in place,

0:50:15.200 --> 0:50:19.200
<v Speaker 1>and reportedly the change came with an intent to make

0:50:19.360 --> 0:50:23.960
<v Speaker 1>actual commercial products, so the divisions would have to dedicate

0:50:24.000 --> 0:50:27.320
<v Speaker 1>themselves to building stuff that could be sold. The mission

0:50:27.320 --> 0:50:31.080
<v Speaker 1>statement was effectively being changed from do exploratory research to

0:50:31.160 --> 0:50:34.600
<v Speaker 1>build us something that we can market now. According to

0:50:34.680 --> 0:50:38.719
<v Speaker 1>Business Insider, Boston Dynamics was told to start working on

0:50:38.800 --> 0:50:42.160
<v Speaker 1>designing consumer robots. Now. These would have to be quiet,

0:50:42.280 --> 0:50:44.479
<v Speaker 1>and they'd have to be suitable for operating around human

0:50:44.520 --> 0:50:46.800
<v Speaker 1>beings of all ages. And this was a really narrow

0:50:46.880 --> 0:50:49.680
<v Speaker 1>focus and something that many people at Boston Dynamics were

0:50:49.680 --> 0:50:54.759
<v Speaker 1>not necessarily keen to work on. For one thing, they

0:50:54.760 --> 0:50:57.799
<v Speaker 1>wanted to continue their work in pushing the boundaries and

0:50:57.800 --> 0:51:01.560
<v Speaker 1>looking into all sorts of mechanisms to operate robots, including

0:51:01.600 --> 0:51:04.200
<v Speaker 1>ones that would not be suitable for a consumer robot.

0:51:04.719 --> 0:51:07.759
<v Speaker 1>For example, hydraulic actuators. You know, they're much louder than

0:51:07.760 --> 0:51:10.960
<v Speaker 1>electronic ones, but more powerful, and therefore they can give

0:51:11.000 --> 0:51:14.960
<v Speaker 1>a lot more uh uses applications for robots, but ones

0:51:15.000 --> 0:51:19.560
<v Speaker 1>that wouldn't necessarily be appropriate for a consumer product. Jonathan Rosenberg,

0:51:19.600 --> 0:51:22.880
<v Speaker 1>who had taken the helm of the replicant division, stated, quote, we,

0:51:23.040 --> 0:51:26.160
<v Speaker 1>as a startup of our size, cannot spend thirty plus

0:51:26.200 --> 0:51:29.320
<v Speaker 1>percent of our resources on things that take ten years

0:51:29.480 --> 0:51:33.720
<v Speaker 1>end quote. So he was saying, we can't really afford

0:51:33.760 --> 0:51:37.480
<v Speaker 1>the luxury of doing exploratory research with the idea that

0:51:37.600 --> 0:51:39.840
<v Speaker 1>sometime down the line it's going to pay off. We

0:51:39.920 --> 0:51:42.560
<v Speaker 1>have to start making things that we can actually sell.

0:51:43.000 --> 0:51:44.960
<v Speaker 1>So from a business perspective, you can kind of see

0:51:45.000 --> 0:51:47.799
<v Speaker 1>where he's coming from. But from the perspective of people

0:51:47.800 --> 0:51:52.120
<v Speaker 1>at Boston Dynamics, this was very antithetical to what they

0:51:52.480 --> 0:51:56.880
<v Speaker 1>had been doing up to that point. So Boston Dynamics

0:51:57.200 --> 0:52:00.120
<v Speaker 1>would eventually go on to release a video of Atlas

0:52:00.200 --> 0:52:03.319
<v Speaker 1>stacking boxes in an application that might be suitable for

0:52:03.360 --> 0:52:07.799
<v Speaker 1>something like a warehouse, But apparently that quote soured the

0:52:07.880 --> 0:52:12.120
<v Speaker 1>soup end quote with Google. Google management wanted a consumer

0:52:12.160 --> 0:52:14.719
<v Speaker 1>facing product, not something that was going to have applications

0:52:14.719 --> 0:52:18.120
<v Speaker 1>in industrial settings, and so at that point Google began

0:52:18.160 --> 0:52:22.719
<v Speaker 1>to shop around for another suitor to take over Boston Dynamics. Reportedly,

0:52:23.719 --> 0:52:27.040
<v Speaker 1>one of those potential parties was the Toyota Research Institute,

0:52:27.160 --> 0:52:31.640
<v Speaker 1>but ultimately Google found a buyer in a Japanese company

0:52:31.680 --> 0:52:36.000
<v Speaker 1>called soft Bank. Soft Bank also bought another robotics company

0:52:36.040 --> 0:52:40.000
<v Speaker 1>off of Google slash alphabet called Shaft, which had competed

0:52:40.040 --> 0:52:44.080
<v Speaker 1>in that DARPA robotics challenge I mentioned earlier. Masa Yoshi,

0:52:44.120 --> 0:52:48.040
<v Speaker 1>san CEO of soft Bank, released this statement when news

0:52:48.080 --> 0:52:51.720
<v Speaker 1>broke that the company was acquiring Boston Dynamics. Quote, today,

0:52:51.760 --> 0:52:54.839
<v Speaker 1>there are many issues we still cannot solve by ourselves

0:52:54.840 --> 0:52:58.120
<v Speaker 1>with human capabilities. Smart robotics are going to be a

0:52:58.239 --> 0:53:01.680
<v Speaker 1>key driver of the next stage of information revolution, and

0:53:01.719 --> 0:53:04.240
<v Speaker 1>Mark and his team at Boston Dynamics are the clear

0:53:04.320 --> 0:53:08.920
<v Speaker 1>technology technology leaders in advanced dynamic robots. I am thrilled

0:53:09.040 --> 0:53:11.919
<v Speaker 1>to welcome them to the soft Bank family and look

0:53:11.960 --> 0:53:14.440
<v Speaker 1>forward to supporting them as they continue to advance the

0:53:14.440 --> 0:53:17.600
<v Speaker 1>field of robotics and explore applications that can help make

0:53:17.640 --> 0:53:22.560
<v Speaker 1>life easier, safer, and more fulfilling. So that's the story

0:53:22.640 --> 0:53:25.600
<v Speaker 1>as it stands now with Boston Dynamics. There's a lot

0:53:25.640 --> 0:53:28.080
<v Speaker 1>of hope over at Boston Dynamics that they will be

0:53:28.120 --> 0:53:31.600
<v Speaker 1>able to continue their mission that they had been following

0:53:31.640 --> 0:53:35.920
<v Speaker 1>for years before the Google acquisition. There's also obviously some

0:53:36.000 --> 0:53:38.840
<v Speaker 1>concern that maybe soft Bank will follow suit with Google

0:53:38.840 --> 0:53:40.719
<v Speaker 1>and say, hey, can you make us a robot that

0:53:41.560 --> 0:53:44.359
<v Speaker 1>you know, we'll bake cheesecake and greet people at the door.

0:53:45.280 --> 0:53:48.840
<v Speaker 1>And I totally want a cheesecake robot now. And I

0:53:48.880 --> 0:53:50.719
<v Speaker 1>need to think these things through before I say them,

0:53:50.760 --> 0:53:52.319
<v Speaker 1>because this was not in my notes. It was just

0:53:53.160 --> 0:53:56.399
<v Speaker 1>kind of off the cuff. And Okay, guys, we're gonna

0:53:56.400 --> 0:53:59.400
<v Speaker 1>wrap this up. So that's the story of Boston Dynamics

0:53:59.440 --> 0:54:01.319
<v Speaker 1>so far. I can't wait to see what comes out

0:54:01.360 --> 0:54:05.799
<v Speaker 1>of that story next. But if you guys have suggestions

0:54:05.840 --> 0:54:08.080
<v Speaker 1>for things I should cover in future episodes of tech Stuff,

0:54:08.080 --> 0:54:10.919
<v Speaker 1>you should write me the email addresses tech Stuff at

0:54:10.920 --> 0:54:13.400
<v Speaker 1>how stuff works dot com, or you can drop me

0:54:13.400 --> 0:54:15.399
<v Speaker 1>a line on Facebook or Twitter. The handle of both

0:54:15.440 --> 0:54:18.120
<v Speaker 1>of those is tech Stuff hs W. Remember we also

0:54:18.160 --> 0:54:21.360
<v Speaker 1>have an Instagram account, and you can watch me record

0:54:21.400 --> 0:54:24.920
<v Speaker 1>shows live on Wednesdays and Fridays over at twitch dot

0:54:25.000 --> 0:54:28.400
<v Speaker 1>tv slash tech Stuff. There's a schedule right there. You

0:54:28.400 --> 0:54:30.279
<v Speaker 1>can check that out and chat with me in the

0:54:30.320 --> 0:54:34.200
<v Speaker 1>chat room if you like. I'll enjoy that interaction. I'm

0:54:34.200 --> 0:54:36.880
<v Speaker 1>wrapping this up because there's a cheesecake out there with

0:54:36.920 --> 0:54:39.160
<v Speaker 1>my name on it. I gotta go find it. And

0:54:39.320 --> 0:54:42.880
<v Speaker 1>you guys, well, I'll talk to you again really soon

0:54:48.680 --> 0:54:51.160
<v Speaker 1>for more on this and thousands of other topics because

0:54:51.160 --> 0:55:00.319
<v Speaker 1>it has staff works dot com zo