search

iNavFlight / inav

INAV: Navigation-enabled flight control software
https://inavflight.github.io
GNU General Public License v3.0
3.08k stars 1.46k forks source link

OmnibusF4V3 HMC5883 (BN-880 Mangeto) hardware error only on inav 3.0 #7207

Closed krl91 closed 3 years ago

krl91 commented 3 years ago

Current Behavior

with inav 3.0 and omnibusf4v3 firmware I cannot have HMC5883, but if I use 2.5.1 BMP280 and HMC5883 are working perfectly fine.

Steps to Reproduce

  1. install inav 3.0 omnibusF4v3 firmware (for omnibus F4 v5 ) with last inav configurator stable version (29/06/2021)
  2. Calibrate the gyroscope
  3. configure HMC5883 (magnetometer) and BMP280 (barometer)
  4. magnetometer is red
  5. Calibrate the magnetometer
  6. Magnetometer is still red
  7. redo the same with inav 2.5.1 and inav configurator 2.5 both (magneto and baro) are working fine

Expected behavior

HMC5883 should work with BMP280 (both are in i2c)

Suggested solution(s)

Additional context

dump from 2.5.1

inav2.5.1_ok.txt

JulioCesarMatias commented 3 years ago

looking at your dump, the compass is not calibrated.

JulioCesarMatias commented 3 years ago

your IMU is also not calibrated.

JulioCesarMatias commented 3 years ago

whenever you put a new firmware version on your flight controller, it is highly recommended that the sensors be recalibrated.

krl91 commented 3 years ago

Hi, you're right, I forgot to write it but I did the calibration in both cases. (I just updated the issue)

JulioCesarMatias commented 3 years ago

Hi, you're right, I forgot to write it but I did the calibration in both cases. (I just updated the issue)

ok, weird, the dump shows that the compass has not been calibrated. Have you ever tried to redo the calibration again?

JulioCesarMatias commented 3 years ago

it seems to me that nothing was done, because the mix was also not configured

JulioCesarMatias commented 3 years ago

did you update the firmware with "Full chip erase"?

krl91 commented 3 years ago

I haven't done the mix, because I did many tries, Maybe it was not the good dump, I did it again : inav2.5.1_ok_2.txt

and yes, always full chip erase (I had to unplug the BN-880 if not I cannot erase)

JulioCesarMatias commented 3 years ago

use iNav communication channels to try to solve your problem:

https://t.me/INAVFlight

https://www.facebook.com/groups/INAVOfficial

JulioCesarMatias commented 3 years ago

use iNav communication channels to try to solve your problem:

https://t.me/INAVFlight

https://www.facebook.com/groups/INAVOfficial

I haven't found any problem here that matches yours. I recommend you to try telegram or facebook

JulioCesarMatias commented 3 years ago

did you select the compass template manually, or let iNav automatically search the i2c bus? Maybe it could be a QMC5883 instead of an HMC5883

JulioCesarMatias commented 3 years ago

about the title of the issue, it's not a conflict, the i2c addresses are different. Please rename the issue

krl91 commented 3 years ago

Ok thanks, I correct it. i selected the compass manually

krl91 commented 3 years ago

Ok, I don't know why exactly but it works now.. I was recording a video and this time, Thank you for your help

JulioCesarMatias commented 3 years ago

did you manually switch from HMC5883 to QMC5883?

mainframecn commented 3 years ago

i had a similar issue and had to reduce the I2C speed (configuration) from 800khz to 400khz. (HMC5883)