WEBVTT 00:00.470 --> 00:02.330 I know what you might be thinking. 00:02.960 --> 00:05.540 Did we really need a new version of Ross? 00:06.080 --> 00:13.130 Didn't you just explain that the first version of Ross is amazing and helped us to solve all the problems 00:13.130 --> 00:18.080 of robotics, So why bother developing a new, different version of Ross? 00:19.880 --> 00:27.590 The answer is complex, but can be summed up in one sentence The Ross one developers had no idea and 00:27.590 --> 00:34.580 couldn't even imagine all the things that the community, the companies and the university will do with 00:34.580 --> 00:35.240 Ross. 00:35.720 --> 00:44.510 The development was initially intended for a single robot, the PR2, developed by Willow Garage, and 00:44.510 --> 00:50.300 it was soon realised that Ross could be useful for many other robotics applications. 00:51.100 --> 00:58.360 Over the years, Ross has been used for mobile robots, manipulators, humanoid robots, astronaut robots, 00:58.390 --> 01:01.360 robotic dogs, drones, and much more. 01:02.100 --> 01:08.670 Well, this is a great accomplishment and the culmination of the Euros project creating an universal 01:08.670 --> 01:10.530 operating system for robots. 01:10.560 --> 01:14.880 It has also revealed some limitations and some shortcomings. 01:15.640 --> 01:22.570 It is important to remember that the development of Ros began back in 2007, and the technology was 01:22.570 --> 01:27.250 quite different than wireless networks were not yet widespread. 01:27.400 --> 01:35.710 And Ros was designed to work on wired networks or generally with reliable and stable connections such 01:35.710 --> 01:38.380 as those you found in research laboratories. 01:38.860 --> 01:40.210 Things have changed. 01:40.240 --> 01:46.660 Wireless connections are now predominant, and robots, like everything else, are constantly connected 01:46.660 --> 01:49.000 to networks and to the Internet. 01:49.300 --> 01:56.740 In some cases, the connection can be unreliable, such as in certain factories or in certain area of 01:56.740 --> 02:03.670 our homes, where it's simply impossible to guarantee the same reliability as a wired connection. 02:04.470 --> 02:11.100 While Ross helped to speed up the development of individual robots, soon we set more ambitious goals 02:11.100 --> 02:13.440 such as managing fleets of robots. 02:14.010 --> 02:21.870 This led to new and diverse applications and uses of Ross that not only manage a single robot but also 02:21.870 --> 02:28.290 connect it to other robots, enabling collaboration between multiple robots to complete a single task. 02:30.210 --> 02:37.620 Another field where Ross was used is serial communication with microcontrollers and electronic hardware 02:37.620 --> 02:43.290 devices for sensor reading or sending comments to motors, among other tasks. 02:44.100 --> 02:51.210 When we move from simulated environment to building real robots, dealing with these devices becomes 02:51.210 --> 02:57.690 essential for keeping the robot with the ability to modify and interact with the surrounding environment. 02:57.840 --> 03:04.620 It is also crucial to receive data from these devices so that the robot can understand and reconstruct 03:04.620 --> 03:05.940 the world around it. 03:06.930 --> 03:14.070 Moreover, robots have soon left the safe and controlled environment of research laboratories and have 03:14.070 --> 03:16.860 entered our homes and industries. 03:17.720 --> 03:22.820 This highlighted another aspect, that is the communication security. 03:23.600 --> 03:29.840 It became necessary to ensure that communications between robots and between the robots communication 03:29.840 --> 03:34.670 and the Internet were secure enough guaranteeing the communication privacy. 03:34.700 --> 03:38.030 The robot safety and preventing tampering. 03:39.010 --> 03:46.540 Furthermore, Ros is being used to build increasingly complex robots in which time constraints are crucial 03:46.540 --> 03:48.190 for proper functioning. 03:48.220 --> 03:54.610 This is the case for robot control, with a particular consideration for legged robots like dogs and 03:54.610 --> 03:55.510 humanoids. 03:55.750 --> 04:01.900 In these systems there are strict timing constraints and it is essential that the calculation and the 04:01.900 --> 04:08.380 operation are performed in real time with guaranteed maximum response times. 04:09.380 --> 04:15.380 All these applications were not initially considered during the development of Ros, which is why they 04:15.380 --> 04:16.760 are not supported. 04:17.500 --> 04:24.250 Over the years anyway, many companies and research organizations have developed their custom solutions 04:24.250 --> 04:31.600 and alternative approaches that expand the capabilities of Ros and try to overcome its limitations. 04:32.440 --> 04:39.550 Russia emerges from this awareness, drawing on ten years of experience gained from using and encountering 04:39.550 --> 04:46.390 the limitations of Rose, one aiming to satisfy the new unforeseen demands and applications from the 04:46.390 --> 04:47.740 robotics community.