SparkFun Optical Tracking Odometry Sensor - PAA5160E1 (Qwiic)

SparkFun Optical Tracking Odometry Sensor - PAA5160E1 (Qwiic)- IMU stopped communicating on I2C bus

FTC Team 14683 - We purchased the OTOS unit on January 13th. It arrived on January 16th.

We connected it to or REV Control Hub that afternoon and the unit worked for an hour, and then it stopped talking on the I2C bus.

Same as FTCSandman

We planned on using this on our FTC Decode Robot using a rev control hub. We connected it correctly, mounted it the correct height on the robot and had it working successfully for just over 1 hour before it stopped talking on the I2C bus. We have two robots, and we moved it to the other and had the same result. The chip is receiving power, the power light comes on and I can see the laser also producing light, just no comms. We would like to have this replaced as soon as possible and after checking some forums, it seems this has happened to a bunch of other customers.

We have also connected the OTOS to an Arduino and have the same result. We are able to see the X & Y values come back to the Arduino, but not the Heading. It does not see the IMU.

Is there a known issue or do you have any recommendations to prevent this from failing? Are there any other tests we can preform? We would like to get this handled as quickly as possible. Our next competition is February 14th and we would like to have this working. Any info and direction is appreciated.

How long are they wires? Are there any bare spots on the wire-side where the SDA/SCL might touch/short one another?

You might try disabling the pull-up resistors Hardware Overview - SparkFun Optical Tracking Odometry Sensor - PAA5160E1 (Qwiic) Hookup Guide by cutting the traces between the pads (can always be re-enabled by placing a solder blob onto those same pads) and see if it appears then

If not: Was it purchased from us? If so head over to Return Policy - SparkFun Electronics (contact vendor if purchased elsewhere) and we’ll get ya squared away