Home › Forums › Forums › Technical Support for BerryGPS and BerryGPS-IMU › PiSugar 2 i2c issues
Tagged: berrygpsimu, pisugar
- This topic has 1 reply, 2 voices, and was last updated 1 year, 6 months ago by mlaity.
- January 28, 2021 at 3:50 pm #16554hwilliamsParticipant
I installed a BerryGPS_IMUv4 on my pi zero w. Using usb power from my laptop I am able to get readings from the accel, gyro, compass, etc just fine. Whenever I add the pisugar, I get issues when running ‘sudo i2cdetect -y 1’. It will show a handfull of populated addresses, but if I run it multiple times the addresses intermittently disappear. When the pisugar is attached I cannot run the example code as the ‘BerryIMU device is not found’.
Attached is the output I would normally get from the command when just connecting the IMU and using usb power.
I know this seems to be more an issue with the pisugar, but does anyone recommend a workflow to troubleshoot this issue? I would love to be able to use both of these modules together as it makes for a very compact package I’m happy with.
Attachments:November 11, 2021 at 4:25 am #17069mlaityParticipant
I am experiencing the same issue, using a Raspberry Pi 4B, OzzMaker BerryGPS-IMU-4, and PiSugar 2 Pro. Were you ever able to resolve this?
The I2C addresses continually come and go for each device, making both devices inaccessible. I have reached out to PiSugar support as well. We can’t just create additional I2C buses as both devices have built-in headers to connect to I2C Bus 1 on Pi Pins 3 and 5.
There does not seem to be a conflict in I2C addresses between these devices, with the BerryGPS-IMU-v4 using 1c, 6a, and 77, and the PiSugar using 32 and 75.
- You must be logged in to reply to this topic.