Williangalvani on readme
README.md: update (compare)
Williangalvani on positionControl
Remove acceleration controller,… (compare)
module load missioncommand in mavproxy that is helpful, and using gdb with ArduSub SITL helps too to troubleshoot if commands are not accepted or the mission does not start. Check the ArduPilot Discord and Forums for help too.
attitudethey are accepted but don't result in any movement from the servos unlike when I use
mode ALT-HOLD. Any idea what might be happening? My test command is
setyaw 1 5 0which I believe should set the yaw to 1 at a 5 degree angular velocity. Am I using the command properly? I'm using chibios SUB 4.0.2 on a pixhawk1
Armresulted in servo movement but if I just used
armfollowed by a loop sending the
set_target_attitudemessage from your gist I got no servo movement so assume it wasn't working as expected. What version of sub did that gist work for you on?
We've been having some trouble getting depth hold and arming to persist, for example we'd like the GCS heartbeat failsafe to result in enabling depth hold mode. Setting the parameter with
rosservice call /param/set "param_id: 'FS_GCS_ENABLE'
real: 0.0" seems to do nothing, after loss of activity we get the error message
FCU: Lost manual control and thrusters are disarmed.
Would anyone happen to know how to handle this? We've also tried with
rosrun mavparam but this didn't make any difference either.