ros2_canopen: 0.3.0-1 in 'rolling/distribution.yaml' [bloom]

[ipa-vsp]

Increasing version of package(s) in repository ros2_canopen to 0.3.0-1:

• upstream repository: https://github.com/ros-industrial/ros2_canopen.git
• release repository: https://github.com/ros2-gbp/ros2_canopen-release.git
• distro file: rolling/distribution.yaml
• bloom version: 0.12.0
• previous version for package: 0.2.12-2

canopen

* Update CiA402 bus config docs
* Remove set heartbeat service from master documentation (#294 <https://github.com/ros-industrial/ros2_canopen/issues/294>)
  Co-authored-by: Christoph Hellmann Santos <mailto:[email protected]>
* Add cyclic torque mode to cia402 driver and robot system controller (#293 <https://github.com/ros-industrial/ros2_canopen/issues/293>)
  * Add base functions for switching to cyclic torque mode
  * Add cyclic torque mode as effort interface to robot_system controller
  * Add documentation about cyclic torque mode.
  ---------
  Co-authored-by: Christoph Hellmann Santos <mailto:[email protected]>

canopen_402_driver

* Reformat using pre-commit
* Implement position offsets
* pre-commit fix
* impl operation mode
* Add cyclic torque mode to cia402 driver and robot system controller (#293 <https://github.com/ros-industrial/ros2_canopen/issues/293>)
  * Add base functions for switching to cyclic torque mode
  * Add cyclic torque mode as effort interface to robot_system controller
  * Add documentation about cyclic torque mode.
  ---------
  Co-authored-by: Christoph Hellmann Santos <mailto:[email protected]>

canopen_base_driver

• No changes

canopen_core

• No changes

canopen_fake_slaves

* fix loop timer for run_velocity_mode
* Fix clang format
* Add comments for the fake slave function
* Fix the thread issue.
* Apply suggestions from code review
  Co-authored-by: Dr. Denis <mailto:[email protected]>
* Working version.
* Periodic messages sent, but not received properly.
* Working logic. Still have to work on the edf file.
* Put the periodic messages in OnWrite
* Extend fake_slaves to publish messages via rpdo

canopen_interfaces

• No changes

canopen_master_driver

• No changes

canopen_proxy_driver

• No changes

canopen_ros2_control

* pre-commit fix
* impl operation mode
* Add cyclic torque mode to cia402 driver and robot system controller (#293 <https://github.com/ros-industrial/ros2_canopen/issues/293>)
  * Add base functions for switching to cyclic torque mode
  * Add cyclic torque mode as effort interface to robot_system controller
  * Add documentation about cyclic torque mode.
  ---------
  Co-authored-by: Christoph Hellmann Santos <mailto:[email protected]>
* Fix clang format
* Update canopen_system.hpp
* Add pdo mapping support
* Fix clang format
* Fix pre-commit
* Periodic messages sent, but not received properly.
* Fix the bug that the rpdo queue keeps poping although it is empty.
* Use proper function to get rpdo data
* Fix bug in state interface indexing..
* WIP: Extend the rpdo to have a queue (FIFO) to save the values.
  The read function take the latest value out of the queue and assign to the system interface.
  Need tests.

canopen_ros2_controllers

• No changes

canopen_tests

* Add new line to get checking pipeline okay
* Working version.
* Periodic messages sent, but not received properly.

canopen_utils

• No changes

lely_core_libraries

* Add yaml dependency to package.xml of lely_core_libraries (#290 <https://github.com/ros-industrial/ros2_canopen/issues/290>)

[github-actions]

Thanks for sending a pull request to ROS distro!

This is an automated tool that helps check your pull request for correctness.
This tool checks a number of attributes associated with your ROS package and generates a report that helps our reviewers merge your pull request in a timely fashion. Here are a few things to consider when sending adding or updating a package to ROS Distro.
ROS Distro includes a very helpful CONTRIBUTING.md file that we recommend reading if it is your first time submitting a package.
Please also read the ROS Distro review guidelines which summarizes this release process.

ROS Distro Considerations

• ROS Distributions are created using REP-134 Standards Track as a guide.
• Your package name should comply to REP-144 ROS Package Naming
• Your package must build for all platforms and architectures on the ROS buildfarm. See REP-2000 ROS Releases and Supported Platforms for all supported platforms for your ROS Distro.
• Your package must contain an OSI approved license. Your package.xml file must also include that license in a machine readable format. See REP-149 Package Manifest Format Three Specification for additional details.
• A publicly available, open source, repository for your ROS package.
• While not required, we recommend that you create an account for ROS Discourse and subscribe to the appropriate release topic.
• If you would like, you may join our Discord Server and ask questions in the #infra-help channel.

Package Considerations

Having your package included in a ROS Distro is a badge of quality, and we recommend that package developers strive to create packages of the highest quality. We recommend package developers review the following resources before submitting their package.

• REP-2004 Package Quality Declaration-- The ROS 2 TSC has created a quality rating system for ROS packages. These ratings should serve as a guide for package developers. We recommend package developers achieve a quality level of three or higher.
• Documentation -- it is recommended that ROS packages include an extensive README.md file, and API level documentation using the Sphinx documentation system.
• Maintainer Responsibilities -- the ROS 2 documentation includes a guide to ROS package maintainer responsibilities that summarizes your responsibilities as an open source maintainer. While we do not enforce these requirements on package maintainers they should be considered best practices.
• We recommend that your package should strive to conform to the ROS 2 Developer Guide and the ROS 2 Style Guide.

Need Help?

Please post your questions to Robotics Stack Exchange or refer to the #infra-help channel on our Discord server.

---

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks