GY-530 VL53L0X Laser Ranging Sensor Time-of-Flight

[Patou]

Hello,
There is a new i2c sensor to mesure distances : GY-530 VL53L0X Laser Ranging Sensor Time-of-Flight
https://www.aliexpress.com/premium/gy-5 ... ckPrompt=1
Specifications:
Infrared distance measurement module
Model: GY - VL53L0X
Using the chip: VL53L0X
Power supply: 2.8 to 5V
Ranging time: <30ms
Operating mode: Power consumption 20mW
Standby power consumption: 5μA
Distance: <2 meters
Communication: the IIC communication protocol (fully compatible with 3-5 v system)
PCB size: about 13.3x10.5mm/0.51"x0.43"

Looks very interesting compare to HC-SR04 works on i2c bus no dedicated input for this device laser based and not ultrasonic
For the good C+ programmers is there big work to adapt the lux BH 1750 plug-in for this laser distance ?

[enesbcs]

There is a new i2c sensor to mesure distances : GY-530 VL53L0X Laser Ranging Sensor Time-of-Flight

It maybe new for you, but the plugin for it in the repository since 2017:
https://github.com/letscontrolit/ESPEas ... L53L0X.ino

[Patou]

Thanks gave a Nice wk

[Patou]

Hello again,
I do not find a binary file with this plugin included and I am quiet new in compiling and build up binary files
I am currently using : ESP_Easy_mega-20190110_test_core_250_beta_ESP8266_4096.bin
2 Questions :
Is there somewhere a tutorial how to compile and add plugin in binary this will make me more clever ?
Or Do you have a ready made binary file including this plugin ?
I am still leaning ...
Patou

[Domosapiens]

@2
https://www.letscontrolit.com/wiki/inde ... evelopment

[enesbcs]

Hello again,
I do not find a binary file with this plugin included and I am quiet new in compiling and build up binary files
I am currently using : ESP_Easy_mega-20190110_test_core_250_beta_ESP8266_4096.bin
2 Questions :
Is there somewhere a tutorial how to compile and add plugin in binary this will make me more clever ?
Or Do you have a ready made binary file including this plugin ?
I am still leaning ...
Patou

With PlatformIO you can build your own build from source.
Anyway, i've a binary, that contains VL53L0X plugin, attached. (however it is compiled from an older codebase, it still works)

[juju]

Hello, this thread is pretty old but I get a try

So I bought the same Sensor and I cannot manage to use it with (EspEasy or else).
After many researched, I found that my sensor uses the 0x39 I2C address instead of 0X29.
Is there a solution to edit this address used by the plugin without full recompilation ?

Thanks in advance.

[TD-er]

Hello, this thread is pretty old but I get a try

So I bought the same Sensor and I cannot manage to use it with (EspEasy or else).
After many researched, I found that my sensor uses the 0x39 I2C address instead of 0X29.
Is there a solution to edit this address used by the plugin without full recompilation ?

Thanks in advance.

Using the web interface to save the settings, you may need to rebuild it, as that address is not encoded in the combobox: https://github.com/letscontrolit/ESPEas ... no#L66-L67
However, it does use the address as a form value in the HTML, so what you can do is fake a HTTP POST command to send plugin_133_vl53l0x_i2c as being your requested address.

The simplest way I can think of right now is to change the HTML via the browser's inspect window to set the value to 0x39 and then press submit.

[juju]

Thanks for this quick answer.
I'll try today.

Actually when I try to enable the device, nothing happens. The page refreshes and the device is still disabled. Maybe your trick will help me.

[Ath]

After many researched, I found that my sensor uses the 0x39 I2C address instead of 0X29.

Strange, according to the chip documentation, a VL53L0X has an I2C address of 0x52, not 0x29, 0x30 or 0x39, at wat address is it found by the ESPEasy I2C Scanner (Tools page)?

Can you provide a link to the actual device you bought?

[juju]

Hello,

So I bought this one on Aliexpress (perhaps not the best choice) :
https://fr.aliexpress.com/item/40013516 ... 6c37zwVDZQ

The I2c scanner show this information :

I2C Addresses in use
0x39

Supported devices
PCF8574A
TSL2561
APDS9960

The I2C Scan on Tasmota show the same address.

[Ath]

Have you tried to change the address by bringing the SD0 pin low/high? (As suggested in the plugin) And assuming you got one with that connection

Possibly the suggested 0x30 alternate address in the plugin is a typo, and should be 0x39 (those keyboard keys are sooo close together )

[juju]

I'm not sur to understand your suggest.

I bought this one : https://ae01.alicdn.com/kf/He58d57900da ... pg_Q90.jpg
And in EasyEsp I tried the 2 options 0X29 and 0X30 without success.

I can change this setting and save it. But I never manage to Enable the device. Nothing happens and if I refresh the page the device is still disabled.

Thanks for your time.

[Ath]

Have you tried to manipulate the page like TD-er suggested? That's currently the only way to get that 0x39 address in there. Possibly it is auto-disabled after ~10 reboots because it's crashing but I'm not sure a wrong address would even crash it. So the Enabled checkbox should normally be saved.

What version (date?) of ESPEasy are you running on this device, as the plugin seems to come from the PluginPlayGround, there won't be regular builds available, only self-built, AFAICS.

[juju]

I just tried and it doesn't work.

I use the bin posted by enesbcs on this topic.
Please find the firmware information :

Build:⋄ 20103 - Mega
Libraries:⋄ ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3
GIT version:⋄ (custom)
Plugins:⋄ 43 [Normal] [Testing] [Development] [IR]
Build time:⋄ Feb 9 2019 16:39:22
Binary filename:⋄ Self built!


I tried to compile with a most recent version to add the plugin but it's not my cup of tea and I have many errors. I continue my researches.

[TD-er]

After many researched, I found that my sensor uses the 0x39 I2C address instead of 0X29.

Strange, according to the chip documentation, a VL53L0X has an I2C address of 0x52, not 0x29, 0x30 or 0x39, at wat address is it found by the ESPEasy I2C Scanner (Tools page)?

Can you provide a link to the actual device you bought?

0x52 >> 1 = 0x29

The problem with I2C device addresses is that the last bit is used to signal the communication direction (R/W).
So some use the 6 bit notation (as does our scanner) and some use the 7 bit notation. (e.g. NXP almost always mentions the 7 bit notation in the datasheets)

[Ath]

0x52 >> 1 = 0x29

My hex calculations aren't that trained to see that immediately, thnx

[TD-er]

0x52 >> 1 = 0x29

My hex calculations aren't that trained to see that immediately, thnx

Would you say it is a bit shifted?

[Ath]

0x52 >> 1 = 0x29

My hex calculations aren't that trained to see that immediately, thnx

Would you say it is a bit shifted?

[Ath]

I've pulled the plugin from the PlayGround to my local dev system, added the VL53L0X library mentioned in the source and fixed a few nasty errors (buffer overflow, fixed on I2C address 0x29, crashing if no sensor attached on 0x29 )
Also added address 0x39 to the Address selector and cleaned up the other options as well.

ESP8266 4M1M testing build attached (including plugins P133 and P050 in addition to the normal test configuration)

Please test and report your findings here

As it is rather a lot newer than the previous build, it may need a blank flash (complete reset) and re-configuration (can be restored from a config backup)

[TD-er]

Ah you got a bit carried away I see

[juju]

Thanks again for your help.

It's small better, I can add the device on the webserver and enable it.
But the distance is still 0.

I still see the I2C address 0X39 in I2C scan, so I guess the wiring is ok.

In the log I have now an error I never have before :
597545: VL53L0X: Sensor not found, init failed for 0x39
(I tried the other value and same results).

May the night be with me

[TD-er]

@Ton:
Maybe log the incorrect read value? That's more useful in debugging.

[juju]

Please find the verbose log

Logging: Debug Dev (9)
647026: VL53L0X: Sensor not found, init failed for 0x39
647026: VL53L0X : idx: 0x39
647026: VL53L0X : plugin(idx): 0x0

But the logs entries look like the sample error code in the arduino vl53l0x library.
I have à second sensor I’ll try tomorrow.

[Ath]

Ah you got a bit carried away I see

Well, I think it is quite annoying that a plugin that hasn't been (really) touched for such a long time, isn't working as intended.
It also needs the multi-instance treatment, didn't do that yet, might help to fix the I2C addressing issues now faced.

@Ton:
Maybe log the incorrect read value? That's more useful in debugging.

I'll add some more detailed logging.
Think I'll have to order such sensor, and pick one with I2C address selection, just to be able to properly test it, hm, delivery from Ali/China will take a few weeks so this one will to go on the back-burner (Rather not want to pay the extra 'processing' & shipment costs attached to a local supplier, plus they don't seem to have the ones with the SD0 connection for address selection)

[Ath]

In the log I have now an error I never have before :
597545: VL53L0X: Sensor not found, init failed for 0x39

I added that on purpose

[juju]

Hello, I can send you the sensor if you need it.
I bought 2 of them.
Just tell me

[Ath]

Hello, I can send you the sensor if you need it.
I bought 2 of them.
Just tell me

That I'll keep in mind, as I've been unable to find this sensor with changable address, so far, on Ali.

[Ath]

So I bought this one on Aliexpress (perhaps not the best choice) :
https://fr.aliexpress.com/item/40013516 ... 6c37zwVDZQ

Which of the 5 available sensors did you buy?, as only one of them is a VL53L0X
You might need to check the text that's on the unit to get the actual type of the unit.
(APDS) 9930 = Proximity sensor, similar to the APDS9960, on I2C address..., wait for it... 0x39
GY1145 = UV/IR sensor, on 0x60
(GY)VL53L0X = tof sensor, on 0x29
(GY)PAJ7620 = Gesture sensor (ESPEasy already supports the similar APDS9960 on 0x39), on 0x73
ADXL345 = accelerometer on 0x53

As I'm now thinking you actually got an APDS9930, you could try to use the Gesture - APDS-9960 plugin, available in the TEST builds. It won't give you the time-of-flight measurements though

[juju]

You are right, this is the gesture sensor...
I didn't see any mention of this sensor on the ali page and I made the mistake.

I'm so sorry for the inconvenient and wasting your time...
It doesn't work with espeasy but I don't need it.

I bought another from AZDelivery. I'll try in few days.

Thanks a lot again.

[Ath]

It doesn't work with espeasy but I don't need it.

Have you tried the APDS9960 plugin? It is included in the 'test' builds, and can also work as a r/g/b sensor, but maybe it is ignored, as I don't know if this driver does a chip-check or not.

[juju]

Yes I tried without succès.
I’ll try tomorrow with simple arduino code just to see if It works.

It’s just the beginning of a long journey.

[juju]

I received a real vl53l0x from azdelivery and It works like a charm.
Now I Know if my stove has enough pellets or not with an email.



Again thanks you

[Ath]

Great to hear.

I'll remove the unneeded extra address for the sensor from the code as that's not selectable on the hardware, improve the plugin to handle multiple-instance use, and add as a PR (pull request) to the repository. After it is merged and released you will need to reconfigure (delete the plugin and add again), as it won't keep the current plugin id (133), but probably something like 109 or 110 (next number in the current set of plugins).

[juju]

ok perfect. I'll try this new one.
And if you need help to test, you can contact me.

Have a nice day !

[Simba]

Hello,
Thanks Ath for your compilation, it works well with the VL53L0X.
Will you be able to do a compilation with the latest version (Release mega-20210114) for normal_ESP8266_4M1M, because I need the arithmetic function (acos) not available in your version.
thank you so much

[Ath]

I've updated the plugin to have ID 110 instead of 133, in preparation of a PR, so you will have to reconfigure your device after updating. Also removed the unsupported I2C address 0x39.

This build ('normal' with VL53L0X included) is based on current MEGA branch (2021-02-06) including all WiFi fixes that have been done since 20210114 release.

My VL53L0X sensor has arrived, so I tested it for a short while now, and it seems to work quite fine.
I will be reworking this plugin to have better support for multiple instances, f.e. when using an I2C multiplexer (that's not included in this build though).

[Simba]

Hello,
Thanks a lot for the file and the work done, I will test it next week.
Have a good evening

[Ath]

I have made a PR for this plugin in the ESPEasy repository (#3493). Awaiting review and a merge, but also needs a build that it can be included in, as I couldn't include it in TESTING builds because if a lack of space in the .bin files for that.

[Simba]

I tested this version and the VL53L0X works but there are no arithmetic functions.

734468: ACT : Let,6,(2*acos(1-(24.2/(96/2))))
1734470: Calculate: Unknown token.

[Ath]

I think that is a bugfix that's not yet merged in the development branch, once it is merged I can make a new build.

[TD-er]

The use of arithmetic functions is a bit limited.
You cannot use values as a parameter that still have to be calculated.
So you first have to compute the parameter of the acos function (and store it in a variable) and then hand it over to the acos function.

@Ath What merge do you mean?

[Simba]

I have no problem with my formula, it works well with Release mega-20210114_ESP8266_4M1M.

Let,6,(2*acos(1-([var#5]/([var#1]/2)))) // Angle
Let,7,round(((0.5*([var#1]/2)^2)*([var#6]-sin([var#6]))*[var#2])/1000) //Volume

I also noticed an error in the help !

Radian Angle:
sin(x) Sine of x (radian)
cos(x) Cosine of x (radian)
tan(x) Tangent of x (radian)
arcSin(x) Arc Sine of x (radian)
arcCos(x) Arc Cosine of x (radian) Doesn't work! but acos(x) work fine
arcTan(x) Arc Tangent of x (radian)

[TD-er]

Ah, I messed up in documenting....

And I really have to check the current implementation, to see what parts are fed to the compute functions and what not.
As I did start moving things around while implementing it, so not all functions will accept parameters that still have to be computed.

A quick glance at the code learned the {...:...:...} notation does not accept parameters that still need to be computed.
arithmetic formula like sin(...) should indeed work just fine.

[Ath]

@Ath What merge do you mean?

I thought I remembered a recent commit, related to that Calculate() function, that hasn't been merged yet, but I could be wrong.

[Doryphore]

Hello,

I'm trying to get the VL53L1X to work with espeasy so I installed the firmware ESP_Easy_mega_20210206_normal_ESP8266_4M1M_VCC but it doesn't work.

The VL53L1X module is from the CQrobot brand : https://www.cqrobot.com/index.php?route ... ption=true

Wiki is here :
http://www.cqrobot.wiki/index.php/VL53L ... nce_Sensor

no distance in espeasy :


The i2c adress is good :


Would the VL53L1X be different from the VL53L0X?

[Ath]

I have only tested with the VL53L0X, as I don't own the 1X device. The only real difference should be the supported measuring range.

A few things you can check:
- Does it turn up in the I2C scan (from the Tools tab)? edit: Yes it does, (missed the second screenshot)
- If you look at the logging (best via the USB/Serial connection, but via web should also work) do you see some VL53L0X logging there?

[Doryphore]

Hello,

Thank you for your reply
The espeasy log indicates: the sensor is not found !!!
60516: VL53L0X: Sensor not found, init failed for 0x29
62138: WD : Uptime 1 ConnectFailures 0 FreeMem 25464 WiFiStatus 3 ESPeasy internal wifi status: Conn. IP Init

I ordered a VL53L1X from another brand to test, from the BlueDot brand and whose circuit is different ...
https://www.amazon.fr/gp/product/B07P1H ... UTF8&psc=1

I was inspired by this tutorial, it works with the VL53L1X !
https://nerdiy.de/en/howto-espeasy-vl53 ... -auslesen/

But in this tutorial, the module's configuration page is different, here is his:


and mine

[Doryphore]

Hello,

Hello,

I tested with a VL53L1X from another brand: same result.
https://www.amazon.fr/gp/product/B07P1H ... UTF8&psc=1

The I2c scan takes the VL53L1X sensor well but in the log I have an error message:
2893640: VL53L0X: Sensor not found, init failed for 0x29
2898224: WD : Uptime 48 ConnectFailures 0 FreeMem 25704 WiFiStatus 3 ESPeasy internal wifi status: Conn. IP Init
2898625: VL53L0X: Sensor not found, init failed for 0x29
2903627: VL53L0X: Sensor not found, init failed for 0x29
2908625: VL53L0X: Sensor not found, init failed for 0x29
2913625: VL53L0X: Sensor not found, init failed for 0x29
2918629: VL53L0X: Sensor not found, init failed for 0x29
2923625: VL53L0X: Sensor not found, init failed for 0x29

[Ath]

I've added some extra logging to the VL53L0X driver, and created a build ('normal' instead of 'test' this time)
The log shows the model-id of the chip, as I expect they differ, and the driver used currently only supports 1 id, 0xEE.

The log looks like this when no sensor is attached (I just was too lazy to connect it )

Code: Select all

15138 : Info   : VL53L0X: Sensor not found, init failed for 0x29
15138 : Info   : VL53L0X: Init: unrecognized Model-ID: 0xff

So Model-ID 0xff means 'no sensor attached'.

If you report the Model-ID your VL53L1X reports I'll add that to the check, and you can then try if it works as expected.

Edit:
I just searched the docs of the VL53L0X and VL53L1X and found the Model-ID for the VL53L1X to be 0xEA. Added that to the code, so we now have experimental support for VL52L1X