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.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Adafruit 9dof
#1
Hello all

I have just started out on my project to use the open source software on my sail boat and therefore I apologise if I.m starting out with a really dumb question.

I have dug through previous posts but I may not have phrased my searches right when trying to find 'like problems' on this forum, so I am more than happy to be told to go off and read xyz etc.

My problem is that I bought an Adafruit 9dof which comes up and is recognised as an IMU using BNX055 etc via Pyplotter however, I can't seem to get a compass heading or a temperature or pressure reading out of it no matter what I do.  I have tested the IMU using a Python script and I get changes in values when running the script and moving the IMU around so it's not the pcb.  I did get a feasible pressure reading but not temperature reading when I set the sensor to MS5607-02BA03.

Can I kindly seek your collective wisdom to send me off in the right direction.

The IMU - https://thepihut.com/products/adafruit-9...out-bno055

Kind regards

Steve
Reply
#2
The Raspberry Pi i2c hardware does not implement the i2c standard fully as it does not support clock stretching. The BNO055 sensor requires that clock stretching be supported by i2c for it to transmit data. Therefore the standard i2c hardware has to be disabled and a device tree overlay enabled to replace it.

OpenPlotter only supports IMUs of this list: https://github.com/openplotter/RTIMULib2

I recommend you the ICM-20948 which is the replacement of MPU-9255/MPU-9250 and will be added to this list soon
Reply
#3
Thanks for the advice Sailoog. I have my new sensor (ICM-20948). Running python code I see that it is working fine and provides a heading out of the box. However, despite being recognised as an IMU it still doesn't seem to provide ant input to PyPilot or the Dashboard. Is this because I need to wait for the it to be added to the list as per your reply?

Thanks once again.

Steve
Reply
#4
(2021-03-03, 01:59 PM)Sailoog Wrote: The Raspberry Pi i2c hardware does not implement the i2c standard fully as it does not support clock stretching. The BNO055 sensor requires that clock stretching be supported by i2c for it to transmit data. Therefore the standard i2c hardware has to be disabled and a device tree overlay enabled to replace it.

OpenPlotter only supports IMUs of this list: https://github.com/openplotter/RTIMULib2

I recommend you the ICM-20948 which is the replacement of MPU-9255/MPU-9250 and will be added to this list soon

I've Pican-M hat with Qwiic (I2C) connector and SparkFun 9DoF IMU Breakout - ICM-20948 (Qwiic). Will ICM-20948 be configurable with I2C tool that is part of Openplotter tools or would it be done with some other tools?
Reply
#5
(2021-03-03, 01:59 PM)Sailoog Wrote:  
I recommend you the ICM-20948 which is the replacement of MPU-9255/MPU-9250 and will be added to this list soon

Hello Sailoog.   I wonder if this sensor is supported yet.    Best regards
Reply
#6
Not yet sorry. I need to finish openplotter-gpio app first sorry.
Reply
#7
(2021-03-15, 05:33 PM)Relax Wrote:
(2021-03-03, 01:59 PM)Sailoog Wrote: The Raspberry Pi i2c hardware does not implement the i2c standard fully as it does not support clock stretching. The BNO055 sensor requires that clock stretching be supported by i2c for it to transmit data. Therefore the standard i2c hardware has to be disabled and a device tree overlay enabled to replace it.

OpenPlotter only supports IMUs of this list: https://github.com/openplotter/RTIMULib2

I recommend you the ICM-20948 which is the replacement of MPU-9255/MPU-9250 and will be added to this list soon

I've Pican-M hat with Qwiic (I2C) connector and SparkFun 9DoF IMU Breakout - ICM-20948 (Qwiic). Will ICM-20948 be configurable with I2C tool that is part of Openplotter tools or would it be done with some other tools?

I have the same hat and sensor. This would be a useful feature for me as well for simplicity.
Reply
#8
(2021-03-15, 05:33 PM)Relax Wrote:
(2021-03-03, 01:59 PM)Sailoog Wrote: The Raspberry Pi i2c hardware does not implement the i2c standard fully as it does not support clock stretching. The BNO055 sensor requires that clock stretching be supported by i2c for it to transmit data. Therefore the standard i2c hardware has to be disabled and a device tree overlay enabled to replace it.

OpenPlotter only supports IMUs of this list: https://github.com/openplotter/RTIMULib2

I recommend you the ICM-20948 which is the replacement of MPU-9255/MPU-9250 and will be added to this list soon

I've Pican-M hat with Qwiic (I2C) connector and SparkFun 9DoF IMU Breakout - ICM-20948 (Qwiic). Will ICM-20948 be configurable with I2C tool that is part of Openplotter tools or would it be done with some other tools?

It will be managed by openplotter-pypilot app
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)