-
Notifications
You must be signed in to change notification settings - Fork 262
Adding demo for Example 3 : Industrial Robots with integrated sensor #68
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
Conversation
destogl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work!
.
Changes in short:
I saw some issues I did in Example 1 and you copied it here. After its adaption here, the have to be also addressed for the other example.
Also, it would be good to update the .ros2_control.xacro file as proposed in ros-controls/roadmap#32 and adapt the scenario to it. I would like the sensor to returns some random data than a fixed value.
ros2_control_demo_hardware/include/ros2_control_demo_hardware/rrbot_system_with_sensor.hpp
Outdated
Show resolved
Hide resolved
ros2_control_demo_hardware/include/ros2_control_demo_hardware/rrbot_system_with_sensor.hpp
Show resolved
Hide resolved
| #include "hardware_interface/types/hardware_interface_status_values.hpp" | ||
| #include "ros2_control_demo_hardware/visibility_control.h" | ||
|
|
||
| using hardware_interface::return_type; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bmagyar, @Karsten1987, @v-lopez
This is not encouraged by the ROS1 style guide and by google style.
Should we remove "using" from the official examples?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree (and saw you did on the PR), specially with such a generic name as return_type.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bailaC can you also remove this using? And then adapt the files accordingly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These names are long and mostly meaningless. The motivation was to keep them as short as possible, especially in compilation units that are very likely to be leaf nodes such as these system plugins. I personally prefer short, readable code to adhering to semi-enterprise, cover-all-cases style guides. That is only my opinion though, feel free to change it if you see fit.
ros2_control_demo_robot/description/rrbot/rrbot_system_with_sensor.ros2_control.xacro
Outdated
Show resolved
Hide resolved
ros2_control_demo_robot/description/rrbot/rrbot_system_with_sensor.ros2_control.xacro
Outdated
Show resolved
Hide resolved
ros2_control_demo_robot/description/rrbot_system_with_sensor.urdf.xacro
Outdated
Show resolved
Hide resolved
ros2_control_demo_robot/launch/rrbot_system_with_sensor.launch.py
Outdated
Show resolved
Hide resolved
ros2_control_demo_robot/launch/rrbot_system_with_sensor.launch.py
Outdated
Show resolved
Hide resolved
ros2_control_demo_hardware/include/ros2_control_demo_hardware/rrbot_system_with_sensor.hpp
Show resolved
Hide resolved
We have to create an official controller/publisher in ros2_controller repo. I will get to you in the next two days about this. |
* Add corrections and extensions for the rrbot * Correct build and remove demo nodes from readme. * Apply suggestions from code review Co-authored-by: Bence Magyar <[email protected]> * Adjust colors of the robot * Update ros2_control_demo_robot/package.xml Co-authored-by: Victor Lopez <[email protected]> * Update ros2_control_demo_robot/launch/test_rrbot_description.launch.py Co-authored-by: Bence Magyar <[email protected]> Co-authored-by: Victor Lopez <[email protected]>
# Conflicts: # ros2_control_demo_robot/config/rrbot_with_sensor_controllers.yaml
destogl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See proposals
| "slowdown": slowdown, | ||
| }.items(), | ||
| ) | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Starting of FTS Broadcaster is missing:
| robot_controller_spawner = Node( | |
| package="controller_manager", | |
| executable="spawner.py", | |
| arguments=["fts_broadcaster", "-c", "/controller_manager"], | |
| ) | |
| forward_position_controller: | ||
| type: forward_command_controller/ForwardCommandController | ||
|
|
||
| fts_controller: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| fts_controller: | |
| fts_broadcaster: |
| - joint2 | ||
| interface_name: position | ||
|
|
||
| fts_controller: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| fts_controller: | |
| fts_broadcaster: |
No description provided.