You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use mock_hardware and mock_sensor_commands instead of fake (#739)
* Use mock_hardware and mock_sensor_commands instead of fake
This has been deprecated a while back and was never adapted.
* Update documentation to mock_hardware
# remember that your user needs to have the rights to write that file handle to /tmp/ttyUR
43
43
44
44
Following parameters can be set `ur.ros2_control.xacro <https://github.com/UniversalRobots/Universal_Robots_ROS2_Description/blob/ros2/urdf/ur.ros2_control.xacro>`_\ :
Copy file name to clipboardExpand all lines: ur_robot_driver/doc/usage.rst
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,9 @@ The most relevant arguments are the following:
22
22
23
23
* ``ur_type`` (\ *mandatory* ) - a type of used UR robot (\ *ur3*\ , *ur3e*\ , *ur5*\ , *ur5e*\ , *ur10*\ , *ur10e*\ , or *ur16e*\ ).
24
24
* ``robot_ip`` (\ *mandatory* ) - IP address by which the root can be reached.
25
-
* ``use_fake_hardware`` (default: *false* ) - use simple hardware emulator from ros2_control.
25
+
* ``use_mock_hardware`` (default: *false* ) - use simple hardware emulator from ros2_control.
26
26
Useful for testing launch files, descriptions, etc. See explanation below.
27
-
* ``initial_positions`` (default: dictionary with all joint values set to 0) - Allows passing a dictionary to set the initial joint values for the fake hardware from `ros2_control <http://control.ros.org/>`_. It can also be set from a yaml file with the ``load_yaml`` commands as follows:
27
+
* ``initial_positions`` (default: dictionary with all joint values set to 0) - Allows passing a dictionary to set the initial joint values for the mock hardware from `ros2_control <http://control.ros.org/>`_. It can also be set from a yaml file with the ``load_yaml`` commands as follows:
28
28
29
29
.. code-block::
30
30
@@ -41,7 +41,7 @@ The most relevant arguments are the following:
41
41
wrist_2_joint: -1.765
42
42
wrist_3_joint: 0.0
43
43
44
-
* ``fake_sensor_commands`` (default: *false* ) - enables setting sensor values for the hardware emulators.
44
+
* ``mock_sensor_commands`` (default: *false* ) - enables setting sensor values for the hardware emulators.
45
45
Useful for offline testing of controllers.
46
46
47
47
* ``robot_controller`` (default: *joint_trajectory_controller* ) - controller for robot joints to be started.
@@ -55,12 +55,12 @@ The most relevant arguments are the following:
55
55
56
56
*HINT* : list all loaded controllers using ``ros2 control list_controllers`` command.
57
57
58
-
**NOTE**\ : The package can simulate hardware with the ros2_control ``FakeSystem``. This emulator enables an environment for testing of "piping" of hardware and controllers, as well as testing robot's descriptions. For more details see `ros2_control documentation <https://ros-controls.github.io/control.ros.org/>`_ for more details.
58
+
**NOTE**\ : The package can simulate hardware with the ros2_control ``MockSystem``. This emulator enables an environment for testing of "piping" of hardware and controllers, as well as testing robot's descriptions. For more details see `ros2_control documentation <https://ros-controls.github.io/control.ros.org/>`_ for more details.
59
59
60
60
Modes of operation
61
61
------------------
62
62
63
-
As mentioned in the last section the driver has two basic modes of operation: Using fake hardware or
63
+
As mentioned in the last section the driver has two basic modes of operation: Using mock hardware or
64
64
using real hardware(Or the URSim simulator, which is equivalent from the driver's perspective).
65
65
Additionally, the robot can be simulated using
66
66
`Gazebo <https://github.com/UniversalRobots/Universal_Robots_ROS2_Gazebo_Simulation>`_ or
**NOTE**\ : Instead of using the global launch file for control stack, there are also prepeared launch files for each type of UR robots named. They accept the same arguments are the global one and are used by:
134
134
@@ -150,11 +150,11 @@ Before running any commands, first check the controllers' state using ``ros2 con
150
150
151
151
After a few seconds the robot should move.
152
152
153
-
* To test another controller, simply define it using ``initial_joint_controller`` argument, for example when using fake hardware:
153
+
* To test another controller, simply define it using ``initial_joint_controller`` argument, for example when using mock hardware:
@@ -191,17 +191,17 @@ To test the driver with the example MoveIt-setup, first start the driver as desc
191
191
Now you should be able to use the MoveIt Plugin in rviz2 to plan and execute trajectories with the
192
192
robot as explained `here <https://moveit.picknik.ai/galactic/doc/tutorials/quickstart_in_rviz/quickstart_in_rviz_tutorial.html>`_.
193
193
194
-
Fake hardware
194
+
Mock hardware
195
195
^^^^^^^^^^^^^
196
196
197
-
Currently, the ``scaled_joint_trajectory_controller`` does not work with ros2_control fake_hardware. There is an
198
-
`upstream Merge-Request <https://github.com/ros-controls/ros2_control/pull/822>`_ pending to fix that. Until this is merged and released, you'll have to fallback to the ``joint_trajectory_controller`` by passing ``initial_controller:=joint_trajectory_controller`` to the driver's startup. Also, you'll have to tell MoveIt! that you're using fake_hardware as it then has to map to the other controller:
197
+
Currently, the ``scaled_joint_trajectory_controller`` does not work with ros2_control mock_hardware. There is an
198
+
`upstream Merge-Request <https://github.com/ros-controls/ros2_control/pull/822>`_ pending to fix that. Until this is merged and released, you'll have to fallback to the ``joint_trajectory_controller`` by passing ``initial_controller:=joint_trajectory_controller`` to the driver's startup. Also, you'll have to tell MoveIt! that you're using mock_hardware as it then has to map to the other controller:
0 commit comments