Frame rate and number of bins are different parameters.
How many bins you get is a matter of memory size. 64 zones times 18 bins is just the amount of memory we have to dedicate to getting you data. You can select to output half the number of zones - and double the number of bins for instance.
So, you are trading zones for bins.
As one range is being read out, another is being collected. So, to get the max frame rate, we cannot stop. Nor can we store more data from a given range.
And then there is data speed. ONce you start reading out the data, we will not over-write it. If you are slow extracting the data the sensor will grind to a halt waiting for you.
If you have a really fast communication path (SPI) then the frame rate is limited by the sensor.
8x8 zones is 15 frames and 4x4 zones is 60 frames max. That's running in continuous mode.
If you set up for 8x8 zones - even if you only read out a few of these zones, you cannot go faster.
So, the trick is to figure out how much data you are asking for; and knowing your read-out speed. I2C maxes out at 1Mbit for instance, but lots of people run it at 400Kbits.
As a practical matter it might just be easier to run it and see. Most MCUs have a timing function.
Good luck,
- john
Our community relies on fruitful exchanges and good quality content. You can thank and reward helpful and positive contributions by marking them as 'Accept as Solution'. When marking a solution, make sure it answers your original question or issue that you raised.
ST Employees that act as moderators have the right to accept the solution, judging by their expertise. This helps other community members identify useful discussions and refrain from raising the same question. If you notice any false behavior or abuse of the action, do not hesitate to 'Report Inappropriate Content'
