AHRS: fixed error_yaw reporting with 2 MAVLink connections
when a user first connects with USB, and later switches to the telemetry port without restarting we were getting zero for error_yaw in the logs, as AHRS.get_error_yaw() was being called twice. This ensures we give the last value after the counter is reset
Showing
- libraries/AP_AHRS/AP_AHRS_DCM.cpp 10 additions, 8 deletionslibraries/AP_AHRS/AP_AHRS_DCM.cpp
- libraries/AP_AHRS/AP_AHRS_DCM.h 2 additions, 0 deletionslibraries/AP_AHRS/AP_AHRS_DCM.h
- libraries/AP_AHRS/AP_AHRS_Quaternion.cpp 14 additions, 10 deletionslibraries/AP_AHRS/AP_AHRS_Quaternion.cpp
- libraries/AP_AHRS/AP_AHRS_Quaternion.h 2 additions, 0 deletionslibraries/AP_AHRS/AP_AHRS_Quaternion.h
Loading
Please register or sign in to comment