That's not how it works.
With the VL53L1CB and the VL53L4CX, all the tricky math is done in the host MCU. The raw data, called a histogram, is uploaded to the host after the 'range' completes. It is the Host that evaluates the histogram data and decides what the range is.
So what is going on?
Each 'range' is really two sub-ranges, the difference being the pulse repetition interval. We need this to check for something called radar aliasing where the photons from pulse N come back after the pulse N+1.
So if range A gives a distance of 1m, and range B gives a distance 4M we know something is odd.
Some clever guy figured out how to 'unwrap' this delta and use the data to extract a target beyond the 4M max that would normally exist.
So there is no hex code.
What there is, is a
#define VL53LX_TUNINGPARM_UWR_ENABLE
The UWR stands for 'unwrap', and it's this parameter that you have to look for.
It's on by default.
And I believe the code is overly complex, but I didn't write it, so I cannot be too critical.
(sorry for the slow reply. CES and then the CES Flu knocked me down for a while. - john)
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.
