I looked at FLY074.DAT some. It doesn’t contain the eventLog stream IMU related errors that FLY083.DAT did. I’m always somewhat reluctant to use the eventLog stream info since it’s different depending on the platform and changes with every FW update. Looks a lot like debug statements that developers use to understand the behavior of the FC. Those developers understand what it means but we’re left trying to guess.
But it does seem that the FLY083 eventLog stream had a lot of ominous sounding statements about the IMU and the problems were IMU related.
I noticed that in FLY074 there were 3 failed attempts at a compass calibration before a 4th successful attempt. Is there something you can add that would explain that?
By way of an example about the pitfalls of interpreting the eventLog stream I had noticed in FLY083 that the calibration was triggered because the MA was 44,586 miles from the last time a calibration had been done. Actually, what it says is that the distance was 71750 km. I suspect that it’s just a units label problem, i.e. it’s 71750 meters (not kilometers). That would be consistent with what’s seen in the M2P.