Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add information about which driver features dont work with mock hardw… #1227

Merged
merged 4 commits into from
Jan 10, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ur_robot_driver/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ request.
**Custom script snippets** can be sent to the robot on a topic basis. By default, they will
interrupt other programs (such as the one controlling the robot). For a certain subset of functions,
it is however possible to send them as secondary programs. See [UR
documentation](https://www.universal-robots.com/how-tos-and-faqs/how-to/ur-how-tos/secondary-program-17257/)
documentation](https://www.universal-robots.com/articles/ur/programming/secondary-program/)
on details.
<br/>
**Note to e-Series users:**
Expand Down
8 changes: 8 additions & 0 deletions ur_robot_driver/doc/usage/simulation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -43,3 +43,11 @@ environment for testing of "piping" of hardware and controllers, as well as test
descriptions. For more details see `ros2_control documentation
<https://control.ros.org/rolling/doc/ros2_control/hardware_interface/doc/mock_components_userdoc.html>`_
for more details.

.. note::
Some driver functionalities currently don't work with mock hardware:

* The TCP pose broadcaster does not work.
* The passthrough trajectory controller does not function when calling the follow joint trajectory action.
* The force mode controller also does not respond when trying to start force mode.
* The GPIO controller cannot verify that it has changed the state of an I/O pin, so it will report a failure when trying to set an I/O pin.
Loading