Closed westphae closed 7 years ago
Happens with ahrs0.3, probably earlier.
Even with a proper procedure, reports that "up and forward axes cannot be the same".
May be due to something not cleaning up properly after an initial calibration?
(Note: I suspect my int(a1 / math.Abs(a1)) is getting rounded down to 0 sometimes instead of returning the sign, need to verify.)
This was due to the calibration routine in the goflying mpu9250 driver incorrectly assuming a specific Z direction. Fixed in 49c1854f21de3162a86c9a96ae2897c4b15272f0.
Happens with ahrs0.3, probably earlier.
Even with a proper procedure, reports that "up and forward axes cannot be the same".
May be due to something not cleaning up properly after an initial calibration?
(Note: I suspect my int(a1 / math.Abs(a1)) is getting rounded down to 0 sometimes instead of returning the sign, need to verify.)