I saw the updata logs of OpenMV, said that VL53L5CX is supported. By read the source code, I found that it is only supported on OpenMV4Pro. I added ‘MICROPY_PY_TOF = 1 ‘,’#define #define OMV_ENABLE_TOF_VL53L5CX (1)’ in OpenMV4Plus boardcofing file. Does this open up its support? Is its examples can be offer?
I have solved it.This sensor is so cool.But the driver in OpenMV do not have enough funtion.Like switch to 4*4 mode.Expect it to get better.
It will need to be on a board before we really work harder on the driver. It’s challenging to just include the sensor as it’s $7 by itself which is more expensive than the camera IC.
Now that AE3 cam is on the way with tof on board I wonder if the driver will work on the other cams aswell given there is a sensor attached to the corresponding i2c lines.
A performant, well written driver for the vl53l5cx would be highly beneficial.
Do you see any reasons against general support? Thanks
We’ve upgraded to the VL53L8 on the AE3, the L5 has a lot of issues with stability.
As for it working on older cameras, you are free to hack the firmware to add this. We have no plans to.
I see.
Is there a specific reason for that decision? I’d not see any resulting rivalry in house. Rather product maintenance and costumer support come to mind.
Because it uses a lot of flash for its firmware blob, about 100K see:
Also these devices don’t get detected at runtime, so you have to enable one or the other (VL53L5 or VL53L8) but the OPENMV_4P has neither of those on board. So which one should we enable by default? It would make sense to enable the L8, but what if you or another user wants the L5?