Skip to content

Conversation

@bailaC
Copy link
Contributor

@bailaC bailaC commented Feb 18, 2021

No description provided.

@codecov-io
Copy link

codecov-io commented Feb 19, 2021

Codecov Report

Merging #68 (7e53311) into master (046ce0c) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #68    +/-   ##
=======================================
  Coverage    0.00%   0.00%            
=======================================
  Files           7       2     -5     
  Lines         504     163   -341     
=======================================
+ Misses        504     163   -341     
Flag Coverage Δ
unittests 0.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...l_demo_hardware/src/rrbot_system_position_only.cpp
...l_demo_hardware/src/rrbot_system_position_only.cpp
...l_demo_hardware/src/rrbot_system_position_only.cpp
...l_demo_hardware/src/rrbot_system_position_only.cpp
...l_demo_hardware/src/rrbot_system_position_only.cpp
...l_demo_hardware/src/rrbot_system_position_only.cpp
...l_demo_hardware/src/rrbot_system_position_only.cpp
...rol_demo_hardware/src/rrbot_system_with_sensor.cpp 0.00% <0.00%> (ø)
...l_demo_hardware/src/rrbot_system_position_only.cpp 0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 046ce0c...7e53311. Read the comment docs.

Copy link
Member

@destogl destogl left a 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.

#include "hardware_interface/types/hardware_interface_status_values.hpp"
#include "ros2_control_demo_hardware/visibility_control.h"

using hardware_interface::return_type;
Copy link
Member

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?

Copy link
Contributor

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.

Copy link
Member

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?

Copy link
Member

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.

@destogl
Copy link
Member

destogl commented Feb 22, 2021

I just checked with the suggested changes. It is now failing for ['topic_name' parameter was empty]. I think I understand that adding a new parameter named 'topic_name' will resolve this issue.

Can you suggest what should be the final change here? Should I keep it as it is considering it will be corrected in the future anyway?

We have to create an official controller/publisher in ros2_controller repo. I will get to you in the next two days about this.

bailaC and others added 9 commits March 6, 2021 12:29
* 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
Copy link
Member

@destogl destogl left a 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(),
)

Copy link
Member

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:

Suggested change
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:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fts_controller:
fts_broadcaster:

- joint2
interface_name: position

fts_controller:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
fts_controller:
fts_broadcaster:

@destogl destogl closed this Jun 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create demo for example 3 : Industrial Robots with integrated sensor

5 participants