[Other issue]: The robot's model does not load correctly

[zzz11wh]

Before proceeding, is there an existing issue or discussion for this?

• I have done a search for similar issues and discussions.

Description

Hello
When I ran the demo, I ran into some problems, my terminal shows [fleet_adapter-14] [INFO] [1706022280.900932158] [tinyRobot_command_handle]: Successfully added new robot: tinyRobot2 and
schedule_visualizer_node-4] [INFO] [1706022288.915672244] [schedule_data_node]: Requesting new schedule update because update timed out
[schedule_visualizer_node-4] [INFO] [1706022288.915734107] [schedule_data_node]: [rmf_traffic_ros2::MirrorManager::request_update] Requesting changes for query ID [1] since beginning of recorded history
[rmf_traffic_schedu
This is causing the bots to not load correctly on my map, and I would like to know what is causing this. Thank you for your time, and I sincerely thank you

[mxgrey]

The terminal printout that you're sharing is very normal, so it doesn't explain any problem that you're having.

You'll need to tell us a lot more about

1. What exactly are you doing, e.g. each terminal command that you are running
2. Are you running out-of-the-box demos from this rmf_demos repo or did you customize something? If you customized anything, you'll need to let us know what you changed.
3. What does you mean that the robot's model does not load correctly? Does the robot not appear at all in Gazebo? Does the model look wrong or different than you expect?

[zzz11wh]

Hello, thank you very much for replying to my question. I am very grateful for your reply. I encountered an issue while running the Office World demo, and I only ran the ROS2 launch rmf_ Demos_ The command gz office. launch.xml was used, but the robot was not loaded on rviz

[zzz11wh]

schedule_visualizer_node-4] [INFO] [1706255007.593262846] [schedule_data_node]: Requesting new schedule update because update timed out
[schedule_visualizer_node-4] [INFO] [1706255007.593336200] [schedule_data_node]: [rmf_traffic_ros2::MirrorManager::request_update] Requesting changes for query ID [1] since beginning of recorded history
[rmf_traffic_schedule-1] [INFO] [1706255007.603382619] [rmf_traffic_schedule_primary]: [ScheduleNode::update_mirrors] Sending remedial update starting from the beginning going to 6 for query 1
[schedule_visualizer_node-4] [INFO] [1706255027.603961849] [schedule_data_node]: Requesting new schedule update because update timed out
schedule_visualizer_node-4] [INFO] [1706255007.593262846] [schedule_data_node]: Requesting new schedule update because update timed out
[schedule_visualizer_node-4] [INFO] [1706255007.593336200] [schedule_data_node]: [rmf_traffic_ros2::MirrorManager::request_update] Requesting changes for query ID [1] since beginning of recorded history
[rmf_traffic_schedule-1] [INFO] [1706255007.603382619] [rmf_traffic_schedule_primary]: [ScheduleNode::update_mirrors] Sending remedial update starting from the beginning going to 6 for query 1
[schedule_visualizer_node-4] [INFO] [1706255027.603961849] [schedule_data_node]: Requesting new schedule update because update timed out
schedule_visualizer_node-4] [INFO] [1706255007.593262846] [schedule_data_node]: Requesting new schedule update because update timed out
[schedule_visualizer_node-4] [INFO] [1706255007.593336200] [schedule_data_node]: [rmf_traffic_ros2::MirrorManager::request_update] Requesting changes for query ID [1] since beginning of recorded history
[rmf_traffic_schedule-1] [INFO] [1706255007.603382619] [rmf_traffic_schedule_primary]: [ScheduleNode::update_mirrors] Sending remedial update starting from the beginning going to 6 for query 1
[schedule_visualizer_node-4] [INFO] [1706255027.603961849] [schedule_data_node]: Requesting new schedule update because update timed out
my terminal output timeout

[mxgrey]

Please use https://gist.github.com/ to upload and share large amounts of terminal output instead of putting it directly into your posts. That helps keep the conversations readable.

There's still nothing wrong with the terminal output that you're showing here. The timeout messages are normal when no robots are performing any tasks.

Here's a few things you can do that will help us understand what's going on:

1. Provide a screenshot of Gazebo
2. Copy/paste ALL the terminal output from after you run $ ros2 launch rmf_demos_gz_classic office.launch.xml into a gist and share the link here
3. Copy/paste the output of $ ros2 topic echo /fleet_states into a gist and share the link here

[zzz11wh]

https://gist.github.com/zzz11wh/6c7f4271a92c6fca4a6ee0a1df22f23a
Thank you very much for receiving your reply, this is the output of my terminal, and finally has been updating timed out, I wonder if this has something to do with the absence of bots on the map