this allows for RC inputs to be ignored at low throttle, but won't
trigger failsafe. It is meant for users flying BVLOS missions, where
they want GCS failsafe enabled, but don't want RC failsafe, and want
to be sure that RC inputs will be ignored at low RC throttle values
Thanks to suggestion from Pompecukor
[451/678] Compiling libraries/AP_Terrain/TerrainIO.cpp
../../libraries/AP_Terrain/TerrainIO.cpp: In member function ‘void AP_Terrain::open_file()’:
../../libraries/AP_Terrain/TerrainIO.cpp:167:35: error: ‘.DAT’ directive output may be truncated writing 4 bytes into a region of size between 2 and 5 [-Werror=format-truncation=]
167 | snprintf(p, 13, "/%c%02u%c%03u.DAT",
| ^~~~
compilation terminated due to -Wfatal-errors.
correctly calculate attitude
fix GPS alt message - expects alt in m + 1000, 0 - 5000 m - from vierfuffzig <tunella@gmx.de>
fix used battery capacity - from vierfuffzig <tunella@gmx.de>
AP_Generator_Richenpower: only update servo channel while disarmed
AP_Generator_Richenpower: move warning for servo output channel to prearm checks
AP_Generator: state is simply off if RPM is zero
AP_Generator: send runtime and seconds-until-maintenance in GENERATOR_STATUS
AP_Generator_RichenPower: correct runtime seconds/minutes position in packets
AP_Generator_RichenPower: correct and expand use of mode packet entry
AP_Generator_RichenPower: fail prearm check if generator not seen
AP_Generator_RichenPower: make prearm check for needing maintenance warn-only
AP_Generator_RichenPower: rename runstate to pilot_desired_runstate
AP_Generator_RichenPower: tweak decoding of time-to-maintenance
AP_Generator: add hysteresis for warmup/cooldown in IDLE
AP_Generator: stop generator in case of vehicle crash
AP_Generator: generator must go through idle from run to stop
AP_Generator: emit statustext when generator configured but not present
AP_Generator: do not log if LOG_BITMASK is zero
AP_Generator: do not warn user if generator configured but not present
They won't be able to start the generator if we can't see it.
Don't update the runstate if no readings seen.
AP_Generator: do not send generator status if no readings seen
On the assumption that ArduPilot processes mavlink packets
synchronously (or at least in order), after we have run a timesync
roundtrip we can reasonably expect any mavlink command we have sent
prior to the roundtrip to have been processed, and we should be able to
see the results in the mavlink stream.
