Ekf3 core 0 unhealthy without compass with GSF

I am trying to setup gps on SpeedyBeef4v4. I do not connect compass, but want to get heading using GSF. It is working correctly, heading is corrected after some time, but got ekf3 core 0 unhealthy and can’t arm in loiter.
This is my parameters:

Can someone help me, thank you.

Not being able to arm in loiter is fairly expected unless you provide enough movement for GSF to converge. Loiter requires good yaw estimate.

Thank you. I was making circles with a radius of 5 meters 10 times in a row, but I still got EK3 core 0 unhealthy. I think if GSF is bad, it can cause the “need estimate” error, but not the error in EKF.
@rmackay9 maybe you know where the problem can be and why the core of EKF can become unhealthy?

I would try going in a straight line.

1 Like

I have done like you recommended. I went forward for ~15 meters and went back, got the error “inconsistent yaw reboot or wait” or “roll and pitch”, after this, I rebooted the fc and calibrated gyro and accelerometer. One more time went forward and got the error “AHRS: EKF not started” after what got ek3 core 0 unhealthy. Tried one more time and got “gyro is not calibrated” and “ek3 core 0 unhealthy” after. But gyro was calibrated on a flat surface.

1 Like

disabled use of GPS for ahrs and got just an error “need position estimate” and also when trying to set ekf origin got the error “No SRTM data for this area”

@rmackay9 Is it possible it will not work on speedybeef4v4?

Hi @ollksander,

The missing features for the speedybeef4v4 are here on the wiki and I think the GSF feature is always included if EKF3 is there

Thamk you @rmackay9, I understand. Also I got one new error. when enabled compass and tried to calibrate it. Error I encountered: “CompassCalibrator: Cannot start compass thread.” I read that it can be related to RAM of the FC. Is it true and how could I fix this?

This is my parameters: