EKF3 IMU0 GSF: not enough memory

Hi,

Noticed a situation when installing Copter-4.6.0-beta5 (just seen beta6 released but not tested).

SpeedyBee F405 V3 BLS 50A 30x30 FC&ESC Stack

While trying to learn Chris Rosser’s tuning guides I was distracted and updated to beta5, (never change two things at once while tuning, RULE no1)!

After a test flight I could not see any data logs. I had cleared the memory before this test?

I repeated the flight and still did not have any logs?

Thinking it was s random anomaly I again did a test flight and still no logs BUT I noticed this on the MS HUD,

EKF3 IMU0 GSF: not enough memory.

Reinstalled 4.5.7 and flew a further test flight.

When seeking the data logs I found the previous logs and the latest?

Not knowledgeable to know if this is useful information but offer it as interesting?

Hi @GreyBadger,

Thanks for the report. So this appears to be that the SpeedyBee is running out of memory which is definitely not a good thing.

I’m actually surprised that you were able to arm the vehicle. Has the ARMING_CHECK parameter been set to zero? If “yes” then it would be good to restore this to “1”.

Now that you can get logs off the vehicle, could you provide an onboard log of one of the 4.6 flights? The F4 boards are definitely reaching there limits but maybe we can remove some default features to free up some memory

Hi,
Thanks for the reply.
Arming_Check was set 1 and I did not have any problems arming.
Sorry the files were presented but held rubbish so i deleted them!
During the test flight all seemed normal in bets5, it was only after I tried to view the files that the DataFlash Logs windws reported that there was no files!
I could only see them after I revereted to 5.7.
Agin sorry i can’t be more helpful.

1 Like

Didn’t that FC have some issues with SD cards in general and other hwrdware conflicts?
I think that was the reason why v4 has been developed.

1 Like

Sorry I posted the wrong version, the FC in question is a V4. I have just checked the message list in MP to confirm.

@GreyBadger we need a log file, even if it is a tlog from the GCS or from 4.5.x