2023-06-08, 07:43 PM
(This post was last modified: 2023-06-08, 08:11 PM by baltika_no_9.)
Well this is probably of no use to you but let me try. I have a gy-91 and it works fine.
Pi4 4GB, OPv3 64bit, all latest updates.
I connect the gy-91 (powering the 3.3V pin from 3.3V on the pi)
I run some tests to check that the pi can see both BMP280 and the IMU and that works fine
i2cdetect -y 1 shows the correct addresses - 68 (MPU), 76 (BMP280)
Start Pypilot (v3.2.13), and it shows Detected IMU-925x
I select IMU only
Approve the access request and give read/write permissions
In Pypilot I seem to need to click IMU only again but after that the data appears in Signal K
I can calibrate the device in Pypilot without issue.
I know there have been issues with some gy-91s but my experience is different.
I'd be happy to send one of you my gy-91 to try if you like.
Note I am connecting directly to the pi, not via a PICAN hat.
Pi4 4GB, OPv3 64bit, all latest updates.
I connect the gy-91 (powering the 3.3V pin from 3.3V on the pi)
I run some tests to check that the pi can see both BMP280 and the IMU and that works fine
i2cdetect -y 1 shows the correct addresses - 68 (MPU), 76 (BMP280)
Start Pypilot (v3.2.13), and it shows Detected IMU-925x
I select IMU only
Approve the access request and give read/write permissions
In Pypilot I seem to need to click IMU only again but after that the data appears in Signal K
I can calibrate the device in Pypilot without issue.
I know there have been issues with some gy-91s but my experience is different.
I'd be happy to send one of you my gy-91 to try if you like.
Note I am connecting directly to the pi, not via a PICAN hat.