Node list #11
Open
Node list #11
Conversation
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
…nodes, used hardcoded tests first. will figure out how to integrate roslib to fetch all running nodes
…he correct approach
…ected, missing, and unexpected nodes. Used "ros2 launch rosbridge_server rosbridge_websocket_launch.xml" to run ROS bridge server, and then "cb" and "ros2 launch subjugator_bringup gazebo.launch.py" to get the GUI to work properly.
connect to the sub and the local machine
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.
Created a GUI update that returns the expected, unexpected, and missing nodes. Used "ros2 launch rosbridge_server rosbridge_websocket_launch.xml" to run ROS bridge server, and then "cb" and "ros2 launch subjugator_bringup gazebo.launch.py" to get the GUI to work properly. Updated the node list to match the nodes that are supposed to go live.