In file included from ../../libraries/AP_HAL_SITL/RCInput.cpp:6:
../../libraries/AP_HAL_SITL/RCInput.h:22:17: warning: private field '_sitlState' is not used [-Wunused-private-field]
22 | SITL_State *_sitlState;
| ^
../../libraries/AP_HAL_SITL/RCInput.h:23:10: warning: private field 'using_rc_protocol' is not used [-Wunused-private-field]
23 | bool using_rc_protocol;
| ^
../../libraries/AP_Airspeed/AP_Airspeed_AUAV.h:68:11: warning: private field 'pressure_abs_L' is not used [-Wunused-private-field]
68 | float pressure_abs_L;
Fixes an issue where omni motors (BrushedWithRelay/BrushedBiplor)
are not configured correctly due to initialization order. setup_omni()
must execute first so that _motors_num is set correctly when
setup_pwm_type() uses it to determine which motors are in use.
This condition must be exactly the same as the one in ChibiOS as whether
we use full duplex or not causes different bus traffic.
This probably needs refactoring, the semantics are confusing and subtle,
though the use of the same driver between I2C and SPI devices must be
accounted for.
Updated the forward throttle battery voltage compensation feature to
disable the throttle entirely when the sag-compensated voltage drops
below the new parameter FWD_THR_CUTOFF_V.
Key changes:
- Added new parameter FWD_THR_CUTOFF_V to control the voltage threshold
for this feature. The default value of 0 matches the original behavior
of never cutting the throttle due to low voltage.
- Modified forward throttle battery voltage compensation logic in the
servos code to cut off the throttle in auto-throttle modes if the
resting voltage estimate of the FWD_BAT_IDX battery is under
FWD_THR_CUTOFF_V.
if a vehicle magically sets a parameter (eg. via compass learn) then it can persist pat test end and reboots and everything,.
In this case it can randomly cause the next test to fail with a megneti field difference error
This was definitely not working (no caller to auto_trim()), and has probably subtly broken in several other ways since it has not been autotested.
If this feature is wanted in the future then factoring Copter's support up into RC_Channel (and possible AP_Vehicle) is probably the way to do this.
we're moving towards using an RC aux switch for this functionality.
Blimp doesn't currently have suport for this functionality (lacking a call
