Skip to content

Conversation

@mergify
Copy link

@mergify mergify bot commented Dec 31, 2025

This PR introduces a new message definition: VDA5050SafetyState.

VDA5050SafetyState provides a standardized message for reporting the safety state of a robot or AGV in accordance with the VDA5050 schema. The fields and enumerations in this message are directly derived from the official VDA5050 specification to ensure compatibility with VDA5050-compliant fleet management systems and controllers.

While this message already exists in the ipa320/vda5050_msgs package, it is being added to control_msgs to:

  • Enable direct integration with the upcoming vda5050_safety_state_broadcaster in ros2_controllers, and

  • Ensure that the message is maintained and versioned alongside other core control interfaces.


Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:

  1. Limited scope. Your PR should do one thing or one set of things. Avoid adding “random fixes” to PRs. Put those on separate PRs.
  2. Give your PR a descriptive title. Add a short summary, if required.
  3. Make sure the pipeline is green.
  4. Don’t be afraid to request reviews from maintainers.
  5. New code = new tests. If you are adding new functionality, always make sure to add some tests exercising the code and serving as live documentation of your original intention.

To send us a pull request, please:

  • Fork the repository.
  • Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
  • Ensure local tests pass. (colcon test and pre-commit run (requires you to install pre-commit by pip3 install pre-commit)
  • Commit to your fork using clear commit messages.
  • Send a pull request, answering any default questions in the pull request interface.
  • Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.

This is an automatic backport of pull request #266 done by [Mergify](https://mergify.com).

(cherry picked from commit 6cd40a5)

# Conflicts:
#	control_msgs/CMakeLists.txt
@mergify mergify bot added the conflicts label Dec 31, 2025
@mergify
Copy link
Author

mergify bot commented Dec 31, 2025

Cherry-pick of 6cd40a5 has failed:

On branch mergify/bp/jazzy/pr-266
Your branch is up to date with 'origin/jazzy'.

You are currently cherry-picking commit 6cd40a5.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   control_msgs/msg/VDA5050SafetyState.msg

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   control_msgs/CMakeLists.txt

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@christophfroehlich christophfroehlich merged commit bae4b32 into jazzy Dec 31, 2025
6 checks passed
@christophfroehlich christophfroehlich deleted the mergify/bp/jazzy/pr-266 branch December 31, 2025 09:18
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