cloned_multi_tb3_simulation_launch map is not being published about navigation2 HOT 4 CLOSED

Hit "startup" - Nav2 starts in the inactive state in the multirobot bringup launch files 😄

from navigation2.

Thank you for the quick response. However when I hit "startup" I get the following error output.

[component_container_isolated-9] [INFO] [1712997793.523376375] [robot2.lifecycle_manager_navigation]: Configuring behavior_server
[component_container_isolated-9] [INFO] [1712997793.523622913] [robot2.behavior_server]: Configuring
[component_container_isolated-9] [INFO] [1712997793.529405218] [robot2.behavior_server]: Creating behavior plugin spin of type nav2_behaviors/Spin
[component_container_isolated-9] [INFO] [1712997793.530493930] [robot2.behavior_server]: Configuring spin
[component_container_isolated-9] [INFO] [1712997793.535834517] [robot2.behavior_server]: Creating behavior plugin backup of type nav2_behaviors/BackUp
[component_container_isolated-9] [INFO] [1712997793.536937255] [robot2.behavior_server]: Configuring backup
[component_container_isolated-9] [INFO] [1712997793.541945830] [robot2.behavior_server]: Creating behavior plugin drive_on_heading of type nav2_behaviors/DriveOnHeading
[component_container_isolated-9] [INFO] [1712997793.542991402] [robot2.behavior_server]: Configuring drive_on_heading
[component_container_isolated-9] [INFO] [1712997793.546849067] [robot2.behavior_server]: Creating behavior plugin assisted_teleop of type nav2_behaviors/AssistedTeleop
[component_container_isolated-9] [INFO] [1712997793.548907324] [robot2.behavior_server]: Configuring assisted_teleop
[component_container_isolated-9] [INFO] [1712997793.555642773] [robot2.behavior_server]: Creating behavior plugin wait of type nav2_behaviors/Wait
[component_container_isolated-9] [INFO] [1712997793.556352253] [robot2.behavior_server]: Configuring wait
[component_container_isolated-9] [INFO] [1712997793.560182417] [robot2.lifecycle_manager_navigation]: Configuring bt_navigator
[component_container_isolated-9] [INFO] [1712997793.560444449] [robot2.bt_navigator]: Configuring
[component_container_isolated-9] [ERROR] [1712997793.594457838] [robot2.bt_navigator]: Caught exception in callback for transition 10
[component_container_isolated-9] [ERROR] [1712997793.594532808] [robot2.bt_navigator]: Original error: Could not load library: libnav2_are_error_codes_active_condition_bt_node.so: cannot open shared object file: No such file or directory
[component_container_isolated-9] [WARN] [1712997793.594556423] [robot2.bt_navigator]: Error occurred while doing error handling.
[component_container_isolated-9] [FATAL] [1712997793.594568726] [robot2.bt_navigator]: Lifecycle node bt_navigator does not have error state implemented
[component_container_isolated-9] [ERROR] [1712997793.594961383] [robot2.lifecycle_manager_navigation]: Failed to change state for node: bt_navigator
[component_container_isolated-9] [ERROR] [1712997793.595012168] [robot2.lifecycle_manager_navigation]: Failed to bring up all requested nodes. Aborting bringup.

from navigation2.

Make sure to use an appropriate configuration file for your distribution. Don’t use the main branch’s for humble.

from navigation2.

Hello again,

I managed to load the map.

There were two issues.

Don’t use the main branch’s for humble.

I did you the params file from the humble branch, however it seams like this params file tries to load plugins which are not available in the humble distribution. To solve the issue I copied the plugins from the nav2_params.yaml file as mentioned in #2919

The second issue was the error
map_server: Original error: parameter 'yaml_filename' is not initialized
This error occurred because in the nav2_multirobot_params_all.yaml the lines 262 to 264 were commented out. By commenting them in and adding the the use_sim_time: True parameter it worked.

map_server:
 ros__parameters:
    use_sim_time: True
     yaml_filename: ""

I can now navigate the two robots at once.

from navigation2.