WEBVTT

00:00.200 --> 00:02.140
The Rust community is awesome.

00:02.240 --> 00:04.040
I'm sure you're thinking the same.

00:04.160 --> 00:10.520
There are so many amazing tools that help us to speed up the development of robotics application, and

00:10.520 --> 00:12.890
we are just getting started in this course.

00:13.590 --> 00:20.280
As you will see, we will be using many of other fantastic open source software that offer extremely

00:20.280 --> 00:21.870
complex functionalities.

00:22.720 --> 00:30.700
One of these tools is move it to which we will analyze in detail in the upcoming lessons and we will

00:30.700 --> 00:32.230
use it for our robot.

00:33.050 --> 00:40.460
This software aims to solve some of the most common problems of manipulator robots, such as trajectory

00:40.460 --> 00:44.270
planning and the development of pick and place applications.

00:44.870 --> 00:50.780
It is commonly used by many companies for the development of the robotic arms.

00:51.530 --> 00:58.700
By targeting a general problem, a common need shared by different manipulator robots, including our

00:58.700 --> 00:59.840
small robotic arm.

01:00.050 --> 01:04.190
This software is implemented in a general purpose manner.

01:04.550 --> 01:10.970
This means that the core logic remains the same and it is shared among all the robots that are using

01:10.970 --> 01:11.470
it.

01:11.480 --> 01:16.010
But its functionalities can be configured based on the robot.

01:16.430 --> 01:23.240
For example, different configurations are required depending on whether you want to use this software

01:23.240 --> 01:26.750
for trajectory planning in a three degrees of freedom robot.

01:26.750 --> 01:34.040
So with three joints driven by three motors, or for a more complex robot, for example, with six motors

01:34.040 --> 01:35.990
with six degrees of freedom.

01:36.750 --> 01:42.660
For this reason, the software, along with many other similar software that are already available in

01:42.660 --> 01:48.360
Ros2, provides several parameters for the configuration of its functionalities.

01:48.630 --> 01:54.930
You can think of a node parameter as a setting to customize the behavior of a particular software or

01:54.930 --> 02:02.400
application so only that application can interpret and use these parameters to configure its behavior

02:02.400 --> 02:03.210
accordingly.