vl53l0x question

Discussions about all things Bitcraze
Post Reply
doctorlu
Beginner
Posts: 23
Joined: Mon Dec 28, 2015 8:41 am

vl53l0x question

Post by doctorlu » Fri Mar 10, 2017 6:58 am

Dear all,
I have a question about this laser ranging module. I use the code provided in the deck driver and give it a try. However, the ranging distance could only attain 1.2m or so, but I recall that this module could achieve as maximum as 2m ranging distance. May I ask if any specific regs of this module is not properly configured, so it can only result like this. What is the result after you guys have tested? Thanks

tobias
Bitcraze
Posts: 1515
Joined: Mon Jan 28, 2013 7:17 pm
Location: Sweden

Re: vl53l0x question

Post by tobias » Fri Mar 10, 2017 8:36 am

What we have seen as well is that it starts to get problems at around 1.2-1.5m. I think it is already configured for long distance measurements but it might be worth digging it to it to be really sure.

doctorlu
Beginner
Posts: 23
Joined: Mon Dec 28, 2015 8:41 am

Re: vl53l0x question

Post by doctorlu » Tue Mar 14, 2017 6:12 am

Oh yes, so this is not only from my observation.
Have you guys decided to find out why it happens?

tobias
Bitcraze
Posts: 1515
Joined: Mon Jan 28, 2013 7:17 pm
Location: Sweden

Re: vl53l0x question

Post by tobias » Tue Mar 14, 2017 9:08 am

My qualified guess is that the 2m distance is just in perfect conditions (over specified). I will put a ticket for it on github and hopefully someone will investigate it.

doctorlu
Beginner
Posts: 23
Joined: Mon Dec 28, 2015 8:41 am

Re: vl53l0x question

Post by doctorlu » Mon Jul 03, 2017 3:13 am

Dear all,
I still have this question about Z-ranger. The laser sensor vl53l0x, is not always accessable using I2C. Sometimes, when the test board is powered up, the laser starts to work normally after quite a long time ( a few seconds from my observation ). We have ten such PCBs, all of which have such problem, even, some of the sensors cannot be accessed ever. Do you guys have such problem of Z-ranger? I use the same i2c code in the cf2 firmware to initialize it, but the device ID cannot be read out right.

EDIT: the only difference of the schematic is that we left GPIO1 and xshut pin floating. Will this cause a problem?

tobias
Bitcraze
Posts: 1515
Joined: Mon Jan 28, 2013 7:17 pm
Location: Sweden

Re: vl53l0x question

Post by tobias » Mon Jul 03, 2017 9:39 am

xshut can't be left floating, that is where your problem is.

Post Reply