Sparkfun OTOS error unable to communicate

[Dosterhoudt]

We have a SparkFun Odometry brand new out of the box. When loading code on the driver hub we get an error displayed cannot communicate with 12c device. The light is on the odometry board. We switched to a new wire. Same error. We then attached to another team’s robot that has been successfully using their Sparkfun odometry (also using their cord). It gave the same communication error.

[amchammond]

We are now having a similar issue. Ours worked 2 days ago, now it won’t communicate. Lights are on and have checked cables.

[amchammond]

Can someone from Sparkfun please respond to this topic? We are currently dead in the water with a competition looming a week away. Thanks,
Chris

[TS-Russell]

Is anything else on the i2c bus?

If the sensor is not appearing via i2c scan: It might be worth attempting to disable the i2c pull-up resistors and see if it pops up Hardware Overview - SparkFun Optical Tracking Odometry Sensor - PAA5160E1 (Qwiic) Hookup Guide

[Dosterhoudt]

The Rev Imu is configured on port 0 and the Spark Fun OTOS on port 1 and no other devices. We did not have to do anything to the resistors on our other robot.

[TS-Russell]

Ok. Your next step is still my previous suggestion, whether you feel it necessary or not…

[SparkFro]

Hi there,

Please see my recommendations on this other thread:

Optical Odometry Error Communicating

Hi there, Shouldn’t need to disable the pullup resistors, though it shouldn’t hurt either (the Control Hub has built-in pullup resistors). Does the red power LED on the OTOS illuminate when plugged in and your robot is powered on? If not, you could have a bad cable or bad connector. Can you try swapping the cable to the other Qwiic connector? And closely inspect both Qwiic connectors for bent pins, that can sometimes cause problems. The image below is an example of a Qwiic connector with bent pins: [image] If that’s not it, then you could try connecting the OTOS to an Arduino or other microcontroller and run an I2C scan to at least see if it’s responding at all. If so, then you could try using our Arduino library to at least verify that it functions. If it doesn’t respond to an I2C scan, then your OTOS may have been fried by something (there is some ESD protection on the OTOS, but it’s impossible to protect against all ESD). Hope this helps!