Posts: 102
Threads: 20
Joined: Sep 2019
Reputation:
4
2020-06-24, 10:48 AM
(This post was last modified: 2020-06-24, 11:49 AM by Ranur.)
My compass died yesterday. I do not see any I2c addresses from any equipment at all which is very frustrating. Tips on where to start trouble shooting?
Running i2cdetect gives me nothing. Removing i2c devices so I only have my pijuice still gives me nothing. To be clear - it HAS worked previously
Posts: 2,184
Threads: 20
Joined: Jun 2016
Reputation:
64
I have heard other reports of failed sensors.... I don't really think pypilot has done anything that could cause this.
The next step is to try different sensors and different pi with same sd card. If that works, try old sensors with new pi and new sensors with old pi.
Posts: 102
Threads: 20
Joined: Sep 2019
Reputation:
4
*some trouble shooting later...*
Using i2cdetect I realized none of my i2c devices were found. Strange - since they had been working. Even the can, which was attached as a hat on the pi was missing. Swapped the pi for a new and everything is back to normal.
Posts: 2,184
Threads: 20
Joined: Jun 2016
Reputation:
64
You might want to consider what could have burned the i2c bus on that pi so it doesn't repeat. Do you have long wires on i2c?
Posts: 2,184
Threads: 20
Joined: Jun 2016
Reputation:
64
maybe the i2c range extender _is_ the issue? I am speculating, but using i2c extenders is very rare so it seems an obvious culprit.
Posts: 17
Threads: 2
Joined: Mar 2020
Reputation:
0
I'm having a similar problem -- IMU worked previously now it's flaky. Which would you recommend changing out first? New IMU (soldered to pypilot board) or new RPi?
Posts: 2,184
Threads: 20
Joined: Jun 2016
Reputation:
64
It would be best to try a new pi and a new imu to see where the problem is. How long did it work before stopping? What does it do now?
Can you take the pypilot board off and spray it with something to improve the contact to see if it's a contact problem?