2025-01-20 10:26 AM - last edited on 2025-01-20 01:41 PM by Peter BENSCH
Following up on a diff post. I have a strange result.
If I call the GetSensorId for the VL53L1X we use today I get a return of decimal 61098 which is 0xEEAA. However the comments in the code claim for the GetSensorId should be: "This function returns the sensor id, sensor Id must be 0xEEAC". Which is inconsistent? What is even stranger is that the L4CD shows it should be 0xEEAA (which we have not even received yet).
I'm perplexed now.
Solved! Go to Solution.
2025-01-20 12:26 PM
The VL53L1X, L1CB, L3, L4CD and the L4CX are basically the same underlying MCU will a few tweaks and the addition of a lens or the change of the VCSEL, or some modification of the MCU's code to so something a little bit different.
So, each of these sensors are iterations on the one before it.
And I'm guessing that whoever updated the manuals goofed it up.
I'll believe you that the documentation might be off. I think we stopped putting the chipID in the datasheet.
But different chips will have different ChipIDs, and those ID's will not change.
So you can tell.
- john
2025-01-20 11:21 AM
Correction. The L4 is EBAA which is 60330.
Still confused though why I do not get back EEAC or 61100 from VL53L1X and instead get back 60108 -- but at least its not the CD!
2025-01-20 12:26 PM
The VL53L1X, L1CB, L3, L4CD and the L4CX are basically the same underlying MCU will a few tweaks and the addition of a lens or the change of the VCSEL, or some modification of the MCU's code to so something a little bit different.
So, each of these sensors are iterations on the one before it.
And I'm guessing that whoever updated the manuals goofed it up.
I'll believe you that the documentation might be off. I think we stopped putting the chipID in the datasheet.
But different chips will have different ChipIDs, and those ID's will not change.
So you can tell.
- john