Edit: Subject WAS: I thought I could save someone from i2C cursing... but after a lot of problems.... Well - scroll down - it is solved now! :-D
Yes cursing - not cruising!
Spent quite some time in trouble shoot mode today. Had my Pi ready for installation in my boat with a pijuice UPS, a industrialberry.com CAN HAT, as well as an I2C extender. First time everything tested together, but yesterday all but the I2C worked flawlessly at my desk. Some minor tweaking was desired to change the pijuice I2C adress, but that was programmable in the GUI, so no problem at all.
Hooked it all up, data was coming through from all sources the CAN gave me B&G data, the I2C showed the Barometer card, and the I2C extender was blinking like disco lights. Then I realized - no MPU and pypilot data. Yanked it all out, triple checked connections and did what amateur like me could do. All of a sudden I a cartoonish ping in my head and I remembered the I2C address conflict from yesterday, and surely enough - both the CAN HAT and the MPU9250 are on 0x68. After some googling, the answer was easy. Set the AD0 to high by connecting the pin to 3.3V. That should set the slave address on it to 0x69 and we should be rockin' from there.
Had my solder iron at home, so I got to prioritize woodwork instead for the rest of the day, but even that Openplotter related. :-D It is a waveshare 13.3 inch touchscreen, but as the connectors are on the side of the screen, it needed some protection.
#gettingthere
Yes cursing - not cruising!
Spent quite some time in trouble shoot mode today. Had my Pi ready for installation in my boat with a pijuice UPS, a industrialberry.com CAN HAT, as well as an I2C extender. First time everything tested together, but yesterday all but the I2C worked flawlessly at my desk. Some minor tweaking was desired to change the pijuice I2C adress, but that was programmable in the GUI, so no problem at all.
Hooked it all up, data was coming through from all sources the CAN gave me B&G data, the I2C showed the Barometer card, and the I2C extender was blinking like disco lights. Then I realized - no MPU and pypilot data. Yanked it all out, triple checked connections and did what amateur like me could do. All of a sudden I a cartoonish ping in my head and I remembered the I2C address conflict from yesterday, and surely enough - both the CAN HAT and the MPU9250 are on 0x68. After some googling, the answer was easy. Set the AD0 to high by connecting the pin to 3.3V. That should set the slave address on it to 0x69 and we should be rockin' from there.
Had my solder iron at home, so I got to prioritize woodwork instead for the rest of the day, but even that Openplotter related. :-D It is a waveshare 13.3 inch touchscreen, but as the connectors are on the side of the screen, it needed some protection.
#gettingthere