New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MS5611 and HMC5883 not detected in SPRacing F3 Deluxe #1572
Comments
Please consider providing details of your setup, complete dump and bootlog. |
Just tested a SPR F3 deluxe on both 1.6.1 and 1.7.0 RC1. Both version correctly detected and use the available hardware. |
I guess it's a hardware quality issue. The fact that sensor is being detected by Betaflight doesn't mean that it's functioning properly. INAV is much less tolerant to faulty sensors. |
Neigher Betaflight nor INAV before 1.6 have hardware failure detection. INAV 1.6 and above will detect and disable failing or unreliable sensors for safety. I would assume everybody will want to know about sensor failure before taking off. For the record, both baro and compass work reliably on my genuine SPRacingF3 board. |
And why iNav 1.5.1. didn't work as well? Only 1.5.0 (and probably below). |
There is no difference in 1.5.1 and 1.5.0 regarding i2c bus operations on F3 targets (including SPRacingF3). The board should work equally good (or bad) with both firmware versions. Most likely you are experiencing random sensor failure that manifest itself on all firmwares. Quality problems are very frequent with Chinese boards - you should contact the seller of your board for solving quality issues. Regarding your question wether you can fly or not: in the end it's either blocking faulty boards from flying or having tons of "fly-away" reports. To me choice is pretty much obvious,. |
Random sensors failure should be random, right? :) But I (and one more dude, check your VK group, please) get working (almost) board at 1.5.0, and it hangs with over 600% CPU load at 1.5.1. I tested more than once. Something has done between 1.5.0 and 1.5.1. |
I'm having exactly the same issue with an SPF3 board : MS5611 & HMC5883 are detected and seem to be working fine with iNav 1.5.0. In the following versions, they are not detected and if I manually select them, CPU load go up to 600%. |
olivierlando, welcome to the club. ;) With you I know 5 peoples with this problem. Where you bought your board? |
Nothing affecting I2C and sensor detection on SPRacingF3 board was done between 1.5.0 and 1.5.1. The glitch is triggered by something else. I probably should buy one board from the same source as you guys to investigate. |
Konstantin, I (and other guys) is ready to help as we can. Just say what to do. :) May be this issue didn't link to I2C? |
It's virtually impossible to debug remotely. I would use logic analyzer to check the activity on I2C bus to see what sensor locks up the bus. |
May be I will send to you my board, when I get refund for it? May be this will be faster, than order it from China? |
@dragon1020 where are you located? |
Moscow, Russia. :) |
I bought mine on Amazon : https://www.amazon.fr/gp/product/B01D8EK1YY . I've made some more search and it seems that there are often I2C issues with this version of the board. In Cleanflight the sensors are detected but I can see an lot of I2C errors... I'm going to ask for a refund. Maybe these blocking errors in iNav have saved my plane ;) |
That's the point of hardware failure detection - you want to know about the failure before you fly 😆 |
@dragon1020 yes, it would definitely be faster than ordering from China. Ping me on VK - once I have failing hardware we'll get this squared out - maybe there is some hardware or software solution to this issue. |
Ok, but I bought mine on Ali, from a famous :) supplier ReadytoSky. |
ReadyToSky is know for random quality but very cheap hardware. Finding a decent quality hardware has become a huge problem lately. |
Same problem, SPRacingF3 Deluxe from ReadyToSky, |
Similar issues on my board SPRF3 Deluxe which I bought it in UK. |
Well, I got exactly the same problem with my new SP Racing F3 board. I tested with cleanflight/betaflight and iNav 1.5.0 all work well, but got problem with iNav 1.5.1, 1.6.0, 1.6.1. |
@digitalentity I also bought my SP Racing F3 board from the amazon link appeared above (https://www.amazon.com/gp/product/B01CG6CU9E). I will return it and find another one. |
I believe this issue can be closed - obviously hardware-related. |
Not too early? You don't look at my FC yet. And by the way, look private messages in VK - it's about sending to you my FC. |
georges6788; where did you get your board from in the end? I have a Chinese board that's acting out the same as everyone elses. Genuine SP board then? |
@georges6788 I am also curious where did you get the new board; I am looking for a working SPRF3. Thanks~ |
@moonliftfpv, liutairan |
2 new SPRacingF3 deluxe, i can confirm darkling1979:
I have measured the internal pullups and there are 1k @ SCL and SDA. Is maybe 1k too low? Can someone with a working SPRF3 measure the pullups (between SCL <-> 3.3V and SDA <-> 3.3V)? |
After removing the magnetometer chip (i have heated the chip on top with a soldering iron, until it was removable) , INav detected the baro and gives the expected values. So the magnetometer chip seems to be the culprit. No loss for wings and little loss for copters, they usually need a separate mounted magnetometer. |
@Allerhopp What FC did you modify this way ? SPF3 from Aliexpress / Readytosky ? If this works then I am extremely interrested ! |
That's exactly the one I have !! Thanks a lot :D |
Same problem. In cleanflight everything works reliably, some i2cErrors on startup. |
Hi, |
Hi folks, unfortunately I have a faulty board too. Very bad beginning of my holidy:( However I have not that much time to wait for a new one. So I tried improvin solder joints on the i2c pull up resistors with no luck. MY board (v1) look a bit different from darklings but i manages to find the appropriate resistors using my multimeter. Hope this helps someone!!! Best regrads from Germany. Denis |
I have a short update: I connected my neo 6m gps to the module. The onboard compass doesnot seem to work to at the moment. |
Hi, dumpBetaflight / SPRACINGF3 3.1.7 Apr 3 2017 / 22:27:23 (e1c4b5c)name - mmix reset servo 0 1000 2000 1500 90 90 100 -1 feature -RX_PPM set gps_pos_p = 15 set rc_rate = 100 get magalign_mag = DEFAULT mag_hardware = AUTO mag_declination = 0 magzero_x = 0 magzero_y = 0 magzero_z = 0 get barobaro_tab_size = 21 baro_noise_lpf = 0.600 baro_cf_vel = 0.985 baro_cf_alt = 0.965 baro_hardware = AUTO |
I flashed Inav 1.4.0 and all sensors detected. dumpversionINAV/SPRACINGF3 1.4.0 Nov 28 2016 / 10:59:44 (6bf7a91)pflagsPersistent config flags: 0x00000000dump mastermixermixer QUADX featurefeature -RX_PPM beeperbeeper GYRO_CALIBRATED mapmap AETR1234 serialserial 0 1 115200 38400 0 115200 ledled 0 0,0::C:0 colorcolor 0 0,0,0 mode_colormode_color 0 0 1 set looptime = 2000 rxfailrxfail 0 a dump profileprofileprofile 0 auxaux 0 0 0 900 900 adjrangeadjrange 0 0 0 900 900 0 0 rxrangerxrange 0 1000 2000 servoservo 0 1000 2000 1500 90 90 100 -1 set nav_alt_p = 50 dump ratesrateprofilerateprofile 0 set rc_expo = 70 |
In my opinion the problem with the high cpu load is that the i2c bus is notworking as inav ist expecting it to work. I solved the problem by removing the onboard magnetometer. I than had the same problem again after connecting an external magnetometer on my gps module via i2c and activating it. It turned out that the gps module had no supply voltage bevaus the SP3 does not output 5v when power over usb. Best regards, Denis |
I was having the same problems mentioned above until I desoldered the HMC5883 chip. As soon as I did that I was able to connect with the iNav configurator and the barometer is connected and working now. |
So did I right now - desoldered the HMC5883 after useless effort to power up the board from external source. now everything work fine. Mag will do better when distanced as far as possible from FC. |
If this is a hardware issue then why it works fine in cleanflight/betaflight and iNav 1.4.0? |
Because neither CF not early INAV cares about sensor quality and reliability. If sensor is at least sporadically detectable - CF and early INAV consider it usable which in turn have caused a flood of "fly-away" bugreports some time ago. |
I have same issue to sp3, baro don't work with 1.7x version, but it work with 1.6.1 version inav |
In Betaflight It can Auto detected and read fine. But in Inav its not auto detected.
Also, when I set manually
set baro_hardware = MS5611
the CPU load rise to about 660%The text was updated successfully, but these errors were encountered: