Closed pky404 closed 3 weeks ago
Please provide your full configuration file. Are you sure your file is being loaded at all? Seems to me that you didnt specify a valid filepath or didn’t specify a file 🙂
Rest of the parameters like costmap parameters are loaded correctly in the same launch sequence except the controller server parameters.
Resolved: The parameters for only the controller server and collision monitor were not loading due to the way they were namespaced in the yaml file. Not working:
robot:
controller_server:
/*/
Working this way:
/robot/controller_server:
/*/
Description: I'm experiencing an issue where the RegulatedPurePursuitController specified in the YAML file for the Nav2 container with composition set to True is not being loaded. Instead, the system defaults to using the DWBController. However, the rest of the parameters are loaded correctly from the YAML file, indicating that the file itself is correctly referenced. The same parameter file when passed in composition set to False is working correctly and nav2 is working fine.
Environment: ROS2 Version: Humble Controller: RegulatedPurePursuitController (RPP) Expected Behavior: The RegulatedPurePursuitController specified in the YAML file should load and initialize as the active controller in the controller_server.
Observed Behavior: The DWBController loads instead of the RegulatedPurePursuitController, despite RPP being specified in the YAML file.
Steps to Reproduce:
Configure a YAML file to use RegulatedPurePursuitController. Pass the YAML configuration to nav2_container in the Nav2 launch file. Launch the Nav2 stack and observe which controller initializes. Additional Information:
RPP and DWBController are both installed in the workspace. YAML file path is correctly referenced in the launch file, and other parameters load without issue. Any insight into why this is happening, or if there are additional debugging steps to verify the controller configuration in the Nav2 composition setup, would be appreciated.