1
00:00:01,110 --> 00:00:05,790
So what is Ross and why is it so prevalent in the robotics community?

2
00:00:06,090 --> 00:00:12,810
Ross stands for Robot Operating System and it was released in 2007 as a means to create a collaborative

3
00:00:12,810 --> 00:00:15,060
software framework for robotics development.

4
00:00:15,720 --> 00:00:21,420
You see, robots are hard enough as it is to build, but roboticists always run into the issues of having

5
00:00:21,420 --> 00:00:24,120
to write all of their operating code from scratch.

6
00:00:24,210 --> 00:00:26,280
Generally in some type of embedded system.

7
00:00:26,310 --> 00:00:27,540
See type language.

8
00:00:28,230 --> 00:00:35,250
For example, it could take weeks just to code a blinking indicator light, creating the firmware controller,

9
00:00:35,250 --> 00:00:40,590
managing the serial communications between your microcontroller and main computer, and then actually

10
00:00:40,590 --> 00:00:45,420
creating the high level software node to dictate when the light should blink a certain way.

11
00:00:45,960 --> 00:00:51,930
Not to mention all the debugging and visualization systems you would have to create so that you could

12
00:00:51,930 --> 00:00:57,270
actually make sure your code sensors and actuators are all acting as intended.

13
00:00:57,570 --> 00:01:00,300
That's a lot of coding just to make a light blink.

14
00:01:00,870 --> 00:01:08,010
Thus, Ros was born as an open source project, which comes with tons of built in tools as well as packages

15
00:01:08,010 --> 00:01:13,920
created by other developers to minimize the amount of software development time needed to get your robot

16
00:01:13,920 --> 00:01:14,910
up and running.

17
00:01:15,660 --> 00:01:20,850
Rusty came around to fill in some of the gaps the original Ross one failed to be able to fill.

18
00:01:21,300 --> 00:01:27,780
Rust One excelled in applications in controlled areas such as robotic arms directly connected to a network.

19
00:01:28,170 --> 00:01:31,980
But since then, the robotics application space has grown tremendously.

20
00:01:32,220 --> 00:01:38,580
Applications such as limbed, outdoor terrain, capable mobile robots, drone swarms, and so much more.

21
00:01:38,790 --> 00:01:42,630
Rusty creates a new decentralized style of robotics development.

22
00:01:42,810 --> 00:01:48,720
It caters towards features such as multi operating system support, allowing security configurations

23
00:01:48,720 --> 00:01:54,600
for no data streams, and a reliable, independent communication structure that doesn't fall apart if

24
00:01:54,600 --> 00:01:56,040
there are disruptions in the network.

25
00:01:56,460 --> 00:02:01,680
It also allows for cross ROS version support, so you can still work with systems that were previously

26
00:02:01,680 --> 00:02:03,420
developed with ROS one.

27
00:02:03,960 --> 00:02:05,820
So why should you learn Ros?

28
00:02:05,850 --> 00:02:12,360
Bottom line, it saves you as a robotics developer time by giving you an optimized framework which many

29
00:02:12,360 --> 00:02:14,010
other developers have contributed to.

30
00:02:14,160 --> 00:02:18,840
To help you get up and running quickly and scale your robotic systems.

31
00:02:19,350 --> 00:02:25,680
Ros is used in a variety of applications from research and development, robotic arms, humanoid robots,

32
00:02:25,680 --> 00:02:28,260
self driving cars and so much more.

33
00:02:28,500 --> 00:02:33,720
Not to mention the multiple programming language and libraries developed for it with C++ and Python

34
00:02:33,720 --> 00:02:39,510
officially supported, as well as community driven libraries in Java, JavaScript, Lua, and so much

35
00:02:39,510 --> 00:02:39,960
more.

36
00:02:40,670 --> 00:02:45,830
Ross continues to be developed and improved by the vast open source robotics community all from which

37
00:02:45,830 --> 00:02:48,470
you and your robots can benefit from.

38
00:02:48,980 --> 00:02:53,840
So let's go ahead and jump into Ross so you can see exactly what it has to offer.