Skip to content

Copter/AP_NavEKF3: Throw mode Drop may skip the EKF3 in-flight yaw alignment #35197

Open

Description

@rmackay9

Bug Report

With THROW_TYPE = 1 (Drop), EKF3 may never do its normal in-flight yaw and mag field alignment ("EKF3 IMUx MAGx in-flight yaw alignment complete") because the vehicle may never climb 2.5m above the launch point.

This means the vehicle keeps its initial heading which may have been initialised incorrect because it was near any ground magnetic interference (e.g. the metal in the bridge from which it has been dropped).

How to reproduce in SITL

  1. sim_vehicle.py -v ArduCopter --console --map
  2. param set THROW_TYPE 1
  3. param set SIM_SHOVE_Z -11 <-- accelerates upwards, wait until vehicle is about 60m
  4. param set SIM_SHOVE_TIME 220000 # starts the shove which lasts 22 sec
  5. param set SIM_SHOVE_Z -8.6 <-- decelerates, wait until speed is about 0
  6. param set SIM_SHOVE_Z -9.80665 <-- no acceleration, approximately hovers
  7. THROW
  8. arm throttle force
  9. param set SIM_SHOVE_Z 0 <-- remove acceleration, vehicle will descend, throw will be detectedhe "EKF3 IMUx MAGx in-flight yaw alignment complete" will not be displayed.
image

For comparison, run the ThrowDoubleDrop autotest (Tools/autotest/autotest.py test.Copter.ThrowDoubleDrop). The message does appear but only because it is armed on the ground and then lifted 100m (SIM_SHOVE_Z) before it is released.

This was discovered during the implementation of PR #35105

Version
master

Platform
[ ] All
[ ] AntennaTracker
[x] Copter
[ ] Plane
[ ] Rover
[ ] Submarine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions