ros2 topic list shows partial list of topics

[scottcandy34]

I installed the H.1.0 firmware and there is missing lots of commands for ros2. When running ros2 topic list I only get this returned (below) which is very different from H.0.0 and G.4.1. its essentially missing important topics.

/cmd_audio
/cmd_lightring
/cmd_vel
/interface_buttons
/mobility_monitor/transition_event
/parameter_events
/robot_state/transition_event
/rosout
/static_transform/transition_event

I am not sure if this was the intended outcome or not but since there was no changelog on the docs page for the firmware release saying that it was changed I made this issue (in fact it says it did not change the ROS API commands). I discovered this issue when trying to control the robot with your create3_examples teleop commands and the robot not moving. Changing to H.0.0 or back to any galactic version works fine.

[alsora]

Hi @scottcandy34,
this seems to be a connectivity issue between your laptop and your robot.

Try running ros2 topic list multiple times or even better ros2 topic list --no-daemon --spin-time 10 and this should show the full list of topics.

P.S. no topics have been removed or changed in H.1.0

[scottcandy34]

Ok so I didn't run that yet. and just did the basic. I reinstalled the latest firmware once again. (4th time) and it seems to be ok it returns correctly and the teleop controller works great now. Such a strange issue cant say its been fun with this update lol.

[scottcandy34]

P.S. nothing has changed

[scottcandy34]

although this time I went from H.0.0 to H.1.0 and not G.4.1 to H.1.0

[kwujciak]

In my experience, partial topic list has always meant sub-par connection between my machine and the robot (whether that be pi to robot, robot to linux via wifi, etc).

[scottcandy34]

@kwujciak That would be my thoughts too but unfortunately I have tried reboots and checked network connections. But like I had mentioned above it would work by going back to galactic or H.0.0. When I did this The setup did not change once, I did not even touch the bot. It was only the last time that I got it to work. Can't say exactly what is was but its working now. Nothing was changed but the firmware.