VL53L1x: As per the VL53L1x sensor datasheet, slave ID is 0x29. but sensor is responding to 0x4D . Even after XSHUT pin is pulled down , device is responding to slave ID 0x4D.

[VNair.1]

I have connected VL53L1X sensor to Onion omega2+ controller i2c driver. I2c clock frequency is set to 100khz. For Detecting Slave Devices we have used below command:

"i2cdetect -y 0"

Output of above command:

root@***:~# i2cdetect -y 0

   0 1 2 3 4 5 6 7 8 9 a b c d e f

00:     -- -- -- -- -- -- -- -- -- -- -- -- --

10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

40: -- -- -- -- -- -- -- -- -- -- -- -- -- 4d -- --

50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

70: -- -- -- -- -- -- -- --

As per the datasheet default slave ID is 0x29 but the sensor is responding to 0x4D.

Even if we connect XSHUT pin to GND, VL53L1x sensor is responding .

We have connected the pullup resistor across the I2C pin and XSHUT pin .

[John E KVAM]

You have another device on the I2C.

The one thing I can guarentee is that if the XSHUT is low, the sensor will never respond.

So I can only conclude that there is something else on the I2C.

According to ADAFruit - a truely wonderful company I see:

0x4D

• INA219 High-Side DC Current/Voltage sensor (0x40 - 0x4F)
• INA260 Precision DC Current/Power Sensor (0x40 - 0x4F)
• PCT2075 Temperature Sensor (0x28-0x2E, 0x48-0x4F, 0x70-0x77)

As possible devices that might be at 4D.

But the bigger question is why you are not getting a response at 0x29 when you actually lift the XSHUT pin.

Connection of power, ground, SDA and SCL are all that is need in addtion to lifting the XSHUT pin.

if that doesn't help, perhaps you can give me more information about your configuation.

• john