ArduRover integration with ROS navigation stack (obstacle avoidance) not working properly)

I am Integrating ArduRover V4.0.0 with ROS navigation stack I followed the instructions from this link
the ros planner trajectory is displayed correct in rviz map but the rover is not moving in the correct directions I checked the ENU->NED conversions in mavros and they exist .I appreciate if anyone can help


1 Like

Are /cmd_vel generated by controller? (edit: sorry, probably they are because rover is moving, nevertheless it’s worth to check if they are correct, you can also try rostopic pub some cmd_vels)

Yes the controller is publishing the velocities message to the /cmd_vel correctly the problem is that it moves to wrong direction

And then you send them with mavros setpoint_velocity, right?

I remapped the /mavros/setpoint_velocity/cmd_vel_unstamped topic to /cmd_vel topic in mavros/node.launch so it is sent directly to mavros

Ok, then maybe check all the options of mav_frame service in /setpoint_velocity and compare what you’re setting with mavlink message sent. If that doesn’t work, post all your launch files here, maybe someone will have time to verify. In general this kind of mismatch should be easy to debug, at least if you already know that this is somewhere between mavros and ardupilot

I will try that. Thank you

@soldierofhell thank you for your advice I changed the mav_frame for setpoint_velocity in apm_config.yaml file to BODY_NED and the velocities conversions are as I expect however sometimes the rover still drifts from the actual planner path do you have any idea of what could causing this issue

You mean drift from local planner not from global? Is this Ackermann rover? What local planner are you using? Maybe also read about rover controller in Ardupilot dev guide

No its not an Ackermann rover . I am using Trajectory planner as my local planner and for the drift it drifts from both local and global planners’ plans . I appreciate if you can share the rover controller in Ardupilot link you mean

Here’s a general description of Ardurover’s modes:

In general investigate carefully

IMO here’s the relevant code and seems like nothing like simple PIDs is done here so maybe only PID tuning is required:

But this steering/throttle control is better suited for ackermann, you must check how it’s converted to diffdrive robot you have

Let us know what you find

thank you I will check these links and get back to you

steering/throttle -> throttle left/right function for diffdrive:

I was thinking a bit about this control for diffdrive in Ardurover and I don’t get it. I think the Twist (linear and angular velocity) should be converted to left and right wheel linear velocity with standard kinematics and then for each wheel PID vel -> throttle shoud be applied. Something like in ros_controllers:
But maybe it’s just because the default stream is for ackermann throttle/steering and it was not designed for diffdrive

our driving mode is skid steering and as I can see in AP_MotorsUGV.cpp it is supported it is strange that it still drifts

@soldierofhell , I found this discussing it mention the steering/throttle rates tuning do you think it might could help the ardupilot to control the rover better ?