Speedybee F405 v3 with compass

[girgine]

Hi, I have F405 v3 from speedybee with a GPS M8030(M8) Ublox with integrated compass (QMC5883L (I2C port))

I use the GPS without any issue but compass doesn't work regardless how many configs I tested INAV and it detects both compass and GPS without any issue as soon as enable GPS and Compass..

Would this be an enhancement request for beta flight or should I enable some settings for the beta flight to recognize the compass? I have nothing else external on the I2C channel on this FCC.

Thanks for any help and suggestions,

[haslinghuis]

Try adding MAG_QMC5883 in custom defines while flashing

[girgine]

Is that option available after flashing is completed and the during the first time connection? Thanks

[girgine]

Tried the custom parameters with "MAG" added to other options & MAG_QMC5883 in Custom Defines box - unfortunately didnt work.

thanks,

[haslinghuis]

MAG option should be enough as it's would pull in the whole MAG driver stack.
Checked the board config as it contains needed configuration for mag too.

[girgine]

thank you - still doesn't work. I set mag_hardware AUTO or to QMC5883 with no luck
I also tried mag_i2c_device=1 (default was 2) , with battery or without battery.

changed SDA and SDC cables (yellow and green) i.e. yellow was on SDA but now its on SDC..

trying to see if I am missing anything else, how about pullups? do i need them? currently i2c1, 2 and 3 pullup = OFF

thank you,
Eren

[haslinghuis]

Please try flashing a core build. In CLI press the Submit Support Data and insert the ID here.

SCL should be connected to SCL and SDA to SDA.

[girgine]

Sure, here is the ID
Id: "ddbb575c-172c-49e8-ab16-c5a9fa8ce436"

I flashed with the core build - configured ports, gps , led and vtx. SCL and SDA pads are connected to correct cables coming out of the GPS.

thanks,
Eren

[haslinghuis]

https://build.betaflight.com/API/support/ddbb575c-172c-49e8-ab16-c5a9fa8ce436
https://build.betaflight.com/api/builds/091862f589de6dc0cc5327058a98773e/log

There seems to be no problem here.

If MAG is not working with Core Only build not sure what's wrong. Please check also 4.3.x

[girgine]

Thanks Mark,

4.3 doesn't work either. I am leaning towards that the GPS's compass is not compatible with beta flight, so I will purchase something else that may work.

By the way, while reviewing the output, I didn't notice any "magnetometer" as feature, is this normal? I also see that I2C is detected only 1 device , most likely it is the barometer, if compass was detected, I assume it should have been 2 device.

Eren

Devices detected: SPI:1, I2C:1 <----

feature

feature -RX_PPM
feature -INFLIGHT_ACC_CAL
feature -RX_SERIAL
feature -MOTOR_STOP
feature -SERVO_TILT
feature -SOFTSERIAL
feature -GPS
feature -RANGEFINDER
feature -TELEMETRY
feature -3D
feature -RX_PARALLEL_PWM
feature -RX_MSP
feature -RSSI_ADC
feature -LED_STRIP
feature -DISPLAY
feature -OSD
feature -CHANNEL_FORWARDING
feature -TRANSPONDER
feature -AIRMODE
feature -RX_SPI
feature -ESC_SENSOR
feature -ANTI_GRAVITY
feature RX_SERIAL
feature GPS
feature TELEMETRY
feature LED_STRIP
feature OSD
feature ESC_SENSOR
feature ANTI_GRAVITY

[haslinghuis]

Devices detected: SPI:1, I2C:1 <----

Noticed the same. There is no feature for MAG.

[girgine]

so I compared the INAV code with betaflight code. the I2c addresses are same in both 0x0d however detection and reset codes are different, I think betaflight has the right I2C address but looking at wrong register to detect whether compass is present or not.

perhaps replacing the code with INAV's version (https://github.com/iNavFlight/inav/blob/master/src/main/drivers/compass/compass_qmc5883l.c) would work? lets see if I can re-compile the .hex with the inav qmc5883l.c

by the way, the title of the file at INAV github refers "fixes the unreliable detection" :)

thanks,
Eren

[haslinghuis]

@girgine please flash firmware using #12243 in the commit field.

#12243

[girgine]

how do I pass that parameter while flashing?

betaflight flashing has "custom defines" that I can play with, otherwise, I was going to "pull" git fetch to my drive, replace the c file and re do the make.. obviously I don't know enough nor have access to anything else :)
Thanks again,
Eren

[haslinghuis]

Use the select commit field. Don't forget to select your radio protocol and add custom defines for 5883:

[girgine]

interesting.

I flashed with #12243 as you've sent - nothing changed but..

I thought something else might be causing if config is now fixed. back to documentation.. I then read the clock speed of the 5883s by the manufacturer specs should be either 100mhz or 400mhz for both or 3400mhz for QMC also supported.

I checked betaflight and noticed that the default i2c clock speed is set to 800. (.c config file if I am not mistaken sends 200 as the value?)

set i2c2_clockspeed_khz=400; then it started to work! (100 also works), re-tested with 800 , stopped working. so it seems the problem is clockspeed.

status still shows i2c:1 though and no i2c errors.

then I did few more tests.

1. I flashed with the latest 4.4.0-RC5 and without adding any custom defines, it didn't work , I even couldn't see any parameters when I type "get mag" - nothing shows up , however when I added custom defines + re-flashed then clock speed fix worked again.

2. I flashed the current release, 4.3.2 , just changed the clock speed and it worked ok..

thanks for your help and troubleshooting - I think clock speed is the culprit and also some versions do not support MAG unless added to the custom define :) still dont know why it works with INAV, (will check later on what's the default clock speed there.)

Eren

[haslinghuis]

Just found: #4531

[girgine]

it was a long thread, thanks for sharing it.
it explains why it works with INAV and doesn't with Betaflight even though it's a very old issue, I am surprised it's still lurking around.

I can see my compass variables changing in the sensor screen so it seems functional.

Thanks again for your help and support,
Eren

[dereksynkopa]

I have a similar problem on FC Speedebee F405 V4. However, in my case compas is detected and operation in BF in the sensors is correct. The problem, however, is what happens with further signal processing from the compass. You can see it best in the video at the attached links. Has anyone had a similar problem? I tested several GPS with compass and the same problem everywhere.
https://drive.google.com/file/d/1mUtvQyTrPO_TOVlIOPY0nK5JtE97DTbc/view?usp=drive_link

[ledvinap]

@dereksynkopa : it may be caused by incorrect magnetometr orientation.https://betaflight.com/docs/wiki/guides/current/magnetometer

[haslinghuis]

Did you try set i2c1_clockspeed_khz = 400

[dereksynkopa]

Yes, I tried reducing from 800kHz to 400, but there is no improvement.