About Hardwariano

Hardwariano · 2020-10-26

HelloI use VL53L1X in polling mode to detect hand presence in the range [30, 200] mm. It works well and VL53L1X_GetResult() returns values continuously. Now I want to add window thresholds [40, 80] mm because I need GPIO interrupt to trigger some oth...

Hardwariano · 2020-10-22

HelloI have problems with Ultra Lite Driver (ULD) crosstalk functions "VL53L1X_SetXtalk()" and "VL53L1X_GetXtalk()". I'm not sure if I have made a mistake or if there is an error in the ULD. I will give an example to explain my problem. #############...

Hardwariano · 2020-10-09

Hello. I have VL53L1X working in window mode with GPIO polarity active low:Window mode = 3 (within the distance range (min/max)).Min = 50mmMax = 200 mm It is working well. If my hand is: Within window: GPIO interrupt goes up and downBelow or beyond w...

Hardwariano · 2020-09-16

HelloI open this thread as a continuation of this other one, which is very long. My problem is that the boot states I read with "VL53L1X_BootState" (0x02 and 0x03) do not match the documentation (0x00 and 0x01).As John says in the aforementioned thre...

Hardwariano · 2020-09-14

Hello. I'm using VL53L1X sensor with Ultra Lite Driver (ULD). VL53L1X_GetRangeStatus function returns all the time status 13. This value comes from the array "status_rtn".Where can I find info about the meaning of these values?What does status=13 mea...

Hardwariano · 2022-04-04

Hi MMengUnfortunately I could not solve the problem. What I did was to change the TOF sensor. I chose the VL53L1CX and VL53L1CB sensors. Personally I think VL53L1CX/CB works better and are much easier to control and understand than VL53L0X. Also, the...

Hardwariano · 2021-04-06

In the end I think I was able to solve the problem. It has taken me a long time and a lot of testing, but I think it works well now. I am sharing this because I think there is some kind of bug in the ST API and I did not receive any response months a...

Hardwariano · 2021-04-06

Hi VVita, check this thread I opened some time ago.

Hardwariano · 2020-11-11

Thanks for your answer @John E KVAM . "If you don't set them up, you will get an interrupt after every range. "I didn't know that. I tried it and now I get an interrupt after every range as you said. Until now, when I wanted to measure continuously ...

Hardwariano · 2020-11-09

Any idea what the problem might be? I'm stuck with this and I can't continue with my project. I tried to make the example as clear as possible, but if it is not well understood I can try to explain it in another way. Thanks

User statistics

User Activity

VL53L1X - Sensor doesn't return distance values after setting window thresholds. Ultra Lite Driver (ULD)

VL53L1X - Problems with Ultra Lite Driver (ULD) crosstalk functions "VL53L1X_SetXtalk()" and "VL53L1X_GetXtalk()". Wrong values.

VL53L1X - GPIO interrupt works when range status is different from 0

VL53L1X - Boot states Ultra Lite Driver (ULD)

VL53L1X - Ultra Lite Driver - Function VL53L1X_GetRangeStatus() return values

Re: VL53L0X returns 0x1FFFF (8191)

Re: VL53L1X - Problems with Ultra Lite Driver (ULD) crosstalk functions "VL53L1X_SetXtalk()" and "VL53L1X_GetXtalk()". Wrong values.

Re: VL53L1X does not boot.

Re: VL53L1X - Sensor doesn't return distance values after setting window thresholds. Ultra Lite Driver (ULD)

Re: VL53L1X - Problems with Ultra Lite Driver (ULD) crosstalk functions "VL53L1X_SetXtalk()" and "VL53L1X_GetXtalk()". Wrong values.