We should reset RNGFNDx_TYPE after we finish testing a set of rangefinder drivers to avoid failing successive tests.
Also, we now fail prearm checks if we receive no data from RF, we need to continuously send DISTANCE_SENSOR messages through mavlink to pass those checks while trying to arm.
Co-Authored-By: Peter Barker <7077857+peterbarker@users.noreply.github.com>
Should remove the race condition where we disable an ESC but the vehicle
doesn't realise and lets the vehicle arm.
Also, waiting this long causes the ESCs to just go missing, not give a
telemetry failure
sitl_gps was sending out ubx packets even if the device was supposed to
be absent, allowing the EKF to get a lag and thus allocate its buffers.
The new sim doesn't do that, so we do need to direct the EKF to not use
the GPS.
Co-authored-by: Dr.-Ing. Amilcar do Carmo Lucas <amilcar.lucas@iav.de>
tidy message sending using templates
Calculate and enforce the minimum update period.
Disable unused features to save flash
forced time gaps between all transmits
correct ESC reset functionality
Avoid re-initialization repeatition
Make sure we stop FETtec if safety is on (ignore reverse) this reduces duplicated code
Error count calculation changed
as the telemetry error count is absolute only the overflow status can be safed and used for the percentage calculation
Update the README to add autotests information
FETtec needs a time gap between frames
This allows running at high fast_loop_rates
do not send fast_throttle data if a configuration command just got sent
Example parameter configuration file is for a Quadcopter with ESCs connected to Telem2
remove two FIXME
fix compilation in master
Fix the ESC not re-initializing issue.
Now we re-init whenever we loose connection
RVMASK parameter changes only take effect when not armed
Improve documentation
Always use the same wording when referring to fast-throttle commands
fix pre-arm check message
assure the length of the memmove is positive
Set HAL_AP_FETTEC_CONFIGURE_ESCS to 0 when no ESC hardware is available and you want to test the UART send function
make sure the SERVO_FWT_MASK is valid:
- it can have bit gaps between active channels, but channels higher than 12 are not allowed (AP_EST_TELEM limitation)
- Explain that the FETtec ESC IDs inside the FETtec Firmware need to be contiguous and start at 1.
add tests for ESC power outages
add test that safety switch zeroes PWM for FETtec ESC
This reverts commit 540a56adb8.
Polling this message caused issues on reboot - shouldn't be a problem
but is.
Retrying that showed that the Tracker GUIDED test failed reliably due to
a yaw problem.
