This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MPU-9250 instead of MPU-9255?
Hi Sean,

Finally the IMU arrived, but now it appears to be a 9250 instead of a 9255...
Does it work with the MPU-9250? Or do I have to make modifications for that?
Currently the heading is very unstable, is there a calibration procedure?

Hans Fix
Yes, both IMUs work.
(07-17-2018, 02:12 PM)Sailoog Wrote: Yes, both IMUs work.

Thanks Sailoog,

I am using the Pypilot image of Sean, does that have the same calibration feature?
(I can see the level calibration, and there is a button 'lock calibration')

you can lock the calibration with tinypilot as well.

I recommend upgrading pypilot to latest git. I think openplotter 1.0 doesn't have the latest calibration fixes.

Would it be useful to "upgrade pypilot" similar to "upgrade opencpn" in the menu?
Yes, it is.
Latest calibration fixes were added in openplotter v1.1.0
I will add any change you make in every major update.
I don't think it is a calibration issue. I connected it to a rpi3 with an openplotter image that i dowloaded yesterday. First i had the same problems there. Than I added two pull ups of 3k3 on the i2c lines, and it all became stable.
Sadly enough not for the rpi zero.. that remained unstable.
So I continued testing on the rpi3 which went well untill 5 minutes ago, than it became unstable again. After rebooting it was stable again.
Do the i2c interfaces use different speeds on the two devices? Can I switch it to a lower speed?
After some measurements on i2c: communication seems to be ok. there was a wrong connection with pull ups, but that didn't cause the problems.
Also suspected a capacitor which was not soldered correctly, but that doesn't seem to improve it either....
I believe the speed is 100khz. If you have issues with i2c connection, it is most likely hardware.
Hi, I 've put the oscilloscope on it, and the signals seem to be ok, from the power supply there was a small spike, but with an other power supply the results were the same.
So still strange why it is working on the Rpi with open plotter and not on the tiny pilot image.

I think, I will wait for a new IMU sensor, and see what happens with that one...
(After some changing between the two boards, the thing is not working at all any more, although it is detected by the Rpi-Pypilot as a MPU-9250/MPU-9255 ....)
If it works with openplotter it should work with tinypilot because the driver is the same.

There is a bug in tinypilot that if you change to a different sensor, it won't work. If you delete RTIMULib.ini it will work again. I will correct this soon, I am currently working on supporting more sensors. the library may technically detect them and give data, but many sensors need to calibrate the accelerometer bias unlike mpu925x.

The new mpu9255 with orange (not yellow) capacitor also need accelerometer bias calibrated, so beware of this. Currently I have some that have bias so far wrong (more than 1 g) that they saturate the 2g range even when perfectly still. This needs additional work to automatically switch to 4g range in the driver, and will lose a bit of precision (which should be ok)

So at the moment I suggest only mpu9250/mpu9255 with yellow capacitor or otherwise factory calibrated accelerometer (range .098 to 1.02 g) but I will support other sensors soon, and it requires additional calibration for accelerometer bias.

Forum Jump:

Users browsing this thread: 1 Guest(s)