The parameter 'server_uri' is not initialized (#436)

Posted by @gmchoi96:

Hi,
I’m planning to test the fleet adapter to apply it to my actual robot.

First, run rmf

ros2 launch rmf_demos office.launch.xml

Afterwards, when I try to run the fleet adapter, the following error appears.

ros2 run rmf_demos_fleet_adapter fleet_adapter -c /home/gmchoi/rmf_ws/src/rmf_demos/rmf_demos_fleet_adapter/config.yaml -n
/home/gmchoi/rmf_ws/install/rmf_demos_maps/share/rmf_demos_maps/maps/office/nav_graphs/0.yaml -s
"ws://localhost:8000/_internal"

usage: fleet _adapter [-h] -c CONFIG_FILE -n NAV_GRAPH [-sim]
fleet adapter: error: unrecognized arguments: ws://localhost:8000/_internal
[ros2run]: Process exited with failure 2

May I know why this problem occurs?

This may be a simple question because I’m very immature overall. I would appreciate your help.


Edited by @gmchoi96 at 2024-02-26T03:11:38Z

Chosen answer

Answer chosen by @gmchoi96 at 2024-02-27T00:07:22Z.
Answered by @Yadunund:

There is no -s argument defined by the executable.
server_uri is a ROS parameter as defined here. So if you want to pass it to the fleet_adapter node, you’ll need to run the above command with --ros-args -p server_uri:="ws://localhost:8000/_internal" instead.

Alternatively, you may set the value via launch argument server_uri:=<URI> if you launch the existing launch file

Posted by @Yadunund:

There is no -s argument defined by the executable.
server_uri is a ROS parameter as defined here. So if you want to pass it to the fleet_adapter node, you’ll need to run the above command with --ros-args -p server_uri:="ws://localhost:8000/_internal" instead.

Alternatively, you may set the value via launch argument server_uri:=<URI> if you launch the existing launch file


This is the chosen answer.

Posted by @gmchoi96:

Thank you so much! for the quick and accurate response.