jflyper

I think this is a de-sync between BF and BFC. Can you raise this issue at the configurator repo. We would also appreciate if you can supply a suggested change...

I2C mag repeatedly come up as not working properly in various symptoms (including "it works on iNav"), but it is usually the case that only those with proper measurement apparatus...

You want to try 200? I'm building for default 200 now. Or, you can do it yourself?

Yeap. That it, line 417. Change 400000 to whatever you want, 200000, 100000, ...

Good finding!

😭

@McGiverGim The "DA 5883" looks like a QMC5883; there are numerous Chinese sites listing the DA chip as "_HMC5883 alternative_". EDIT Strange thing is that it could have been detected...

I think the manufacturer is offering custom chips with non-standard I2C address; data sheet says _The default I2C address is 0D: 0001101_ _If other I2C address options are required, please...

Here's the whole story. https://github.com/iNavFlight/inav/issues/1903

Data sheet mentions "_OTP Load_" immediately after POR and Soft Reset. I suspect I2C address is written in the OTP area...