arduino wire library multiple i2c busses

Also, VL53L0X.h (local folder copy) also uses. The main project file has already been changed to use and although it uses a local copy of I2C_Anything.h, that copy uses as well.

This worked great, even though I had tried my best to screw it up. The 7-element VL53L0X array manager (Teensy 3.5) Consequently, the main processor must utilize (multi-wire) capable library functions. The main processor now uses Wire to talk to the second-deck VL53L0X array manager (Teensy 3.5), and Wire1 for the IR homing beacon detector/demodulator and the MPU6050 IMU. With the addition of a Teensy 3.5 for the main robot processor, the multiple I2C bus problem is now relevant to the main processor as well. Teensy 3.x processors provide for multiple I2C buses, a feature I used originally to manage the 7-element VL53L0X array located on the ‘second deck’ of Wall_E2, my autonomous wall following robot. The problem – utilizing multiple I2C buses: So, this post is my account of what went wrong, and the steps taken to get things working properly again. In the process I have created a spaghetti mess of conflicting I2C library file locations and configurations. Basically, I have been trying to use both the ‘i2c_t3.h’ and ‘Wire.h’ Teensy to utilize multiple I2C buses (Wire1, Wire2, etc) over the last few years, without really understanding what I was doing.

As I worked to troubleshoot the issue, it soon became evident that “I wasn’t in Kansas anymore”, and in fact had once again gone down a rabbit hole into Wonderland, with nary a bread-crumb in sight. While working on porting Wall-E2’s ‘second deck’ hardware (VL53L0X array and LIDAR) to Wall_E3, I started running into problems associated with using Wire1 on the main Teensy 3.5 master processor to communicate with the Teensy 3.5 slave processor that manages the seven VL53L0X time-of-flight distance sensors.

Arduino wire library multiple i2c busses