New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APM Rover only: Control APM Rover via teleop twist message? #643
Comments
Infortunatly, Apmrover doesn't have velocity setpoint yet, and it needs gps. To use the position setpoint you need to be in Guided mode. |
Support for setpoint_velocity should come with next rover release : PR in review ArduPilot/ardupilot#5735 |
Closing as it is not MAVROS related |
Why was this closed and how is it not mavros related? Can anyone help with this? Thanks |
The answer:
|
Also if you are not specific about your issue, share code and logs, it will be difficult to someone to help you out. |
I want to take over control of APM Rover with current firmware on PX4v2 somehow from mavros with teleop twist message.
The rover setup is like this:
RC receiver -> PX4v2 (no GPS) - > motor controller board in mixing mode (throttle+steering).
Computer with mavros via TELEM1.
So quite a normal setup.
My first idea was to use /mavros/setpoint_velocity/cmd_vel and set the fcu into OFFBOARD mode.
But this seems not to be possible
a) Rover seems not to support setpoint_velocity/cmd_vel
b) OFFBOARD is no APM Rover mode (http://ardupilot.org/rover/docs/rover-control-modes.html)
Then I searched thru the mavros issues if I can find something related to this topic.
There are many issue comments but not always related to APM Rover or they are confusing or there are needs to change FCU firmware which is no acceptable.
I like programming but why always reinvent everything if there are already other possibilities to realize it.
So I want just to ask the clear question:
What needs to be done in a sensefull way with the current state of mavros / APM Rover firmware to take over control somehow from mavros with teleop twist message?
The text was updated successfully, but these errors were encountered: