VL53L4CD Low Power mode power consumption?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-09 3:44 PM
Hi,
I am trying to find a low power solution for close range (down to 1mm) proximity detection at 1Hz frequency. It seems VL53L4CD can do the job pretty good but I didn't find power consumption details of low power mode in the datasheet.
I also found there is a Ultra Low Power driver for VL53L3CX which only consumes ~50uA@1Hz but it doesn't support close-range. Can VL53L4CD achieve something similar wrt power consumption?
Thanks!
Solved! Go to Solution.
- Labels:
-
Time of flight
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-11 8:14 AM
Wow, you have not asked an easy question.
Basically, integration time is what gives us accuracy. A four fold increase in the integration time, will give a two fold increase in accuracy.
The UltraLowPower (ULP) driver saves power by decreasing the integration time. But at the expense of accuracy. We went so low, we can only see if something is there or not.
The other trick is the ToF sensors are about +/- 3% accurate, but that breaks down at the closer distances. The VL53L4CD in my testing is +/- 2mm at 7mm. (And that assumes you are not looking at really black surfaces and really reflective surfaces.
(The issue seems to be that the photons are taking multiple bounces between the target and the structure that's holding the sensor.)
I'm pretty sure you could run the ULP driver on the L4CD, but the accuracy issues would remain. You could tell something was in front of you, but not exactly where.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-11 8:14 AM
Wow, you have not asked an easy question.
Basically, integration time is what gives us accuracy. A four fold increase in the integration time, will give a two fold increase in accuracy.
The UltraLowPower (ULP) driver saves power by decreasing the integration time. But at the expense of accuracy. We went so low, we can only see if something is there or not.
The other trick is the ToF sensors are about +/- 3% accurate, but that breaks down at the closer distances. The VL53L4CD in my testing is +/- 2mm at 7mm. (And that assumes you are not looking at really black surfaces and really reflective surfaces.
(The issue seems to be that the photons are taking multiple bounces between the target and the structure that's holding the sensor.)
I'm pretty sure you could run the ULP driver on the L4CD, but the accuracy issues would remain. You could tell something was in front of you, but not exactly where.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-14 6:28 AM
Thank you @John E KVAM​ !
Very helpful answer especially the fact that I can run ULP on L4CD.
