Skip to content

Comments

Implementation of ROS2 Control Package#11

Open
sambrus wants to merge 24 commits intodevfrom
sbr/feat-ros2-control
Open

Implementation of ROS2 Control Package#11
sambrus wants to merge 24 commits intodevfrom
sbr/feat-ros2-control

Conversation

@sambrus
Copy link

@sambrus sambrus commented Feb 4, 2026

Add the following :

  • Lucy ROS2 Control package
  • Lucy ROS2 Control launch file
  • Lucy ROS2 Control yaml configuration file
  • Lucy ROS2 Control Hardware Interface implementation (C++)
  • Linkage with our hardware

Arcod7 and others added 19 commits November 1, 2025 16:13
…publish (right arm, left arm) inside ros2_control configuration
Copy link

@charlesmadjeri charlesmadjeri left a comment

Choose a reason for hiding this comment

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

Add in package.xml and CMakelists the package as test target to check build.
Also add unit tests if possible.

Image

#include "rclcpp_lifecycle/state.hpp"
#include <sensor_msgs/msg/joint_state.hpp>

namespace ros2_control_demo_example_2

Choose a reason for hiding this comment

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

demo_example_2 naming should be changed to a persisting naming

Comment on lines +1 to +13
// Copyright 2021 ros2_control Development Team
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

Choose a reason for hiding this comment

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

Copyright ? It should be our own implementation now is it ?

Comment on lines +1 to +13
// Copyright 2021 ros2_control Development Team
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

Choose a reason for hiding this comment

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

Copyright ? It should be our own implementation now is it ?

#include "hardware_interface/lexical_casts.hpp"
#include "hardware_interface/types/hardware_interface_type_values.hpp"

namespace ros2_control_demo_example_2

Choose a reason for hiding this comment

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

demo_example_2 naming should be changed to a persisting naming


/*
This function should be used to initialize/activate the hardware.
In our case, the hardware is already ready to receive informations from the Jetson ?

Choose a reason for hiding this comment

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

To answer, we will probably use this function later to trigger the config change check and update config pipeline

Comment on lines +55 to +62
# install(
# DIRECTORY description/launch description/ros2_control description/urdf
# DESTINATION share/ros2_control_demo_example_2
# )
# install(
# DIRECTORY bringup/launch bringup/config
# DESTINATION share/ros2_control_demo_example_2
# )

Choose a reason for hiding this comment

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

usefull to keep ?

Choose a reason for hiding this comment

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

Add test config to be built by colcon during tests pipeline

type="ros2_control_demo_example_2::LucySystemHardware"
base_class_type="hardware_interface::SystemInterface">
<description>
Our LucySystemHardware.

Choose a reason for hiding this comment

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

"Sentience Robotics Lucy system ros2_control package"

Choose a reason for hiding this comment

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

Or the same as the next xml file

Choose a reason for hiding this comment

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

2 xml files, why ? Is it standard and following good practicies ?

Choose a reason for hiding this comment

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

2 xml files, why ? Is it standard and following good practicies ?

Signed-off-by: Charles Madjeri <charles@madjeri.com>
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.

3 participants