this prevents a condition where the GCS can display the wrong value if
the 2nd PARAM_VALUE is lost
Note that groundstations can tell the set failed due to readonly in
the following ways:
1) look for the statustext: Param write denied (PARAMNAME)
2) see that the value came back with the old value, with index of
65535
3) can repeat the send, looking for (1) and (2)
Michael has proposed we add a PARAM_VALUE mavlink2 flags
extension. That would be nice, but we should still make this change to
fix the issue with mavlink 1.0
Includes commits by rmackay9
AC_WPNav: fixup max speed acceleration
AC_WPNav: simplify the initialisation of poscontrol's max speed
Changed at Leonard's request to keep things simpler
when GPS primary switches we were using a position which had not been
corrected for antenna offset. This was used for calculating the reset
for sensor change.
This fixes that (trivial fix) and also fixes a similar issue on
position reset
when GPS primary switches we were using a position which had not been
corrected for antenna offset. This was used for calculating the reset
for sensor change.
This fixes that (trivial fix) and also fixes a similar issue on
position reset
If a defaults.parm file was present in the hwdef, waf ignored the --default-parameters=xyz.parm command line argument. This will allow it to use that command line argument specified file.
this also removes the old parameter conversion code used for when we
first added the SERVO parameters. This was needed for conversion from
Copter 3.4 and Plane 3.7
bugobliterator
Andrew Tridgell
Peter Hall
Peter Barker
Randy Mackay
Bill Geyer
bnsgeyer
Matt Lawrence
ashvath