VL53L7CX current consumption

[SelimMuhammed]

Dear ST,
Now I'm testing my VL53L7CX sensor that is on the package P-NUCLEO-53L7A1 in Autonomous Mode with integration time = 2ms, ranging freq. = 4Hz and 4X4 Resolution, the attached screen-shot represents the output current related to my integration time and it's typically 2ms.
My question is about the added peaks after the integration time peak, Why could this happen?
and, How can I eliminate or reduce it?
Knowing that the duration of these peaks illustrated in the other screen-shot attached.
Thank you.

[EliasB]

Hi SelimMuhammed,

The current waveforms that you provided are very normal for your given settings. The "peaks" after the integration are as follows:

First Peak: Post processing of the result

Second Peak: i2c data read out  

Third Peak: Transition to low power state

The time for the First Peak and Third Peak is fixed. You do not have control over these.

However, you can reduce the time of the Second Peak by reducing the amount of data you are reading. Another option for reducing the time required after integration is to operate at a faster i2c speed.

Elias

[SelimMuhammed]

Thanks @EliasB 

I really appreciate it 

[SelimMuhammed]

Hi again @EliasB,
Now I have minimized the amount of data by Uncommenting the MACROS as mentioned in the driver but the output waveforms still the same, However the value of (p_dev->data_read_size) is reduced (from 536 to 108 decimal).
Do you have explanation?
And which method that I should follow to minimize the data out from the sensor as you mentioned?
I also followed the instructions you mentioned in your comment, so I developed 2 different configurations for the I2C and data to be transferred:
The first configuration is I2C in fast mode with no data transfer and the second one is I2C in standard mode with all ranging data activated and the peaks are almost the same (See the attached screenshots)

[Bin · Accepted solution]

Hi:

I have confirmed with internal RD. here is the latest news:

1. basically your integration time, this is the only one you can control.

2.readout data and internally algos are working.

3.Post processing mostly internal MCU work.

4.Ranging core disabled to reduce power consumption.

The above 2, 3, and 4 are fixed and unchangeable.

In addition, fw exists in the form of a specific array VL53L7CX_FIRMWARE and is generally not modified. If you have specific projects, you can contact our FAE and raise a special request. Thanks~

Best Regards,

Bin FAN