Unable to communicate to VL53L0CX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-09-02 7:49 AM
Working on a board that uses a VL53L0CX. But I do not seem to be able to communicate with the sensor and have even tried to scan i2c addresses with no luck. I am hoping someone here can take a look at the schematic I have for the sensor and let me know if I made a mistake that I am glossing over. Not shown here is that SDA/SCL are both pulled up with 4.7k resistors.
- Labels:
-
Time of flight
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-09-02 8:05 AM
Hi,
There is no internal I2C pull up resistors in the VL53L0X, you need two external pull up. Thanks, Julien
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-09-02 8:16 AM
Thanks for the quick reply. Not shown are the pullup resistors which are 4.7k ohm each.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-09-07 7:50 AM
Changed Pull-ups on SDA and SCL from 4.7k yo 1k. Does not appear to have made any kind of difference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-09-07 10:26 AM
I have long held that there are only a few hardware things that can keep the VL53 sensors from responding.
1) lack of power. Looks like yours is OK
2) Xshut not being pulled up. Again looks like yours is good
3) I2C not configured correctly - and it looks like you've got that about right.
4) Wires are too long for the I2C protocol to work correctly.
So that leaves software.
I'm going to guess there is a configuration issue somewhere.
- john
If this or any post solves your issue, please mark them as 'Accept as Solution' It really helps. And if you notice anything wrong do not hesitate to 'Report Inappropriate Content'. Someone will review it.
