Adding the diagnostics bridge to the flowstate_ros_bridge package#83
Open
JCarosella wants to merge 8 commits intointrinsic-ai:mainfrom
Open
Adding the diagnostics bridge to the flowstate_ros_bridge package#83JCarosella wants to merge 8 commits intointrinsic-ai:mainfrom
JCarosella wants to merge 8 commits intointrinsic-ai:mainfrom
Conversation
JCarosella
commented
Jan 8, 2026
Yadunund
requested changes
Jan 9, 2026
Contributor
Yadunund
left a comment
There was a problem hiding this comment.
Thanks for working on this! Left a high level comment to avoid API breaking changes for now. Will do a deeper review after addressing this change.
002eac1 to
0635d8b
Compare
Signed-off-by: JCarosella <juancarosella96@ekumenlabs.com>
Signed-off-by: JCarosella <juancarosella96@ekumenlabs.com>
… bridge API Signed-off-by: JCarosella <juancarosella96@ekumenlabs.com>
Signed-off-by: JCarosella <juancarosella96@ekumenlabs.com>
…arify configuration usage
ee3e697 to
3f480a1
Compare
b-corry
reviewed
Feb 12, 2026
Contributor
b-corry
left a comment
There was a problem hiding this comment.
Minor comments, otherwise LGTM
Comment on lines
+60
to
+64
| auto params_interface = ros_node_interfaces.get<rclcpp::node_interfaces::NodeParametersInterface>(); | ||
| diagnostics_pub_ = rclcpp::create_publisher<diagnostic_msgs::msg::DiagnosticArray>( | ||
| params_interface, | ||
| topics_interface, | ||
| "/diagnostics", rclcpp::SystemDefaultsQoS()); |
Contributor
There was a problem hiding this comment.
Potential enhancement: we can add optional remapping for topic names like /diagnostics. This could exist as a new remap proto message which is passed into the service config and propogated to the node options when starting the flowstate_ros_bridge.
|
|
||
| // Add key-value pairs for more detail. | ||
| diagnostic_msgs::msg::KeyValue kv_state; | ||
| kv_state.key = "Platform State"; |
Contributor
There was a problem hiding this comment.
Perhaps this could get moved to a const at top of the file.
Signed-off-by: JCarosella <juancarosella96@ekumenlabs.com>
Signed-off-by: JCarosella <juancarosella96@ekumenlabs.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the full diagnostics workflow to the ROS bridge, reading diagnostics information from Flowstate and publishing to ROS 2. The project builds and bundles correctly with the flowstate ros bridge service scripts.
Principal changes
Installation and testing
This will produce a tarball in a new
imagesdirectory at the same level of thesrcdirectory.Create a solution and add the service or add it to an existing solution
Test the new ROS 2 diagnostics topic by trying to subscribe to the
/diagnosticstopic.Result
Diagnostics feature is fully integrated and compiles successfully. New diagnostics bridge publishes correctly to ROS 2. This is the output of a test I ran locally with a solution deployed to an IPC:
Testing information here: #88 (comment)