Hi, Barth.
Even though the datasheet states the minimum timing budget is 8ms, I looked into this again with the latest ST API and was unable to set it much lower than about 17.1ms (about 58Hz). I would guess there might be some measurement steps that could be disabled to get a higher speed at the cost of some reliability or accuracy, but I haven’t found any documentation or examples from ST that show how to do this.
Note that early versions of the API explicitly enforced a minimum of 20ms, so that is what the Pololu library does too. That check was removed in the current version of the API, which seems to let us push it a bit lower to ~17.1ms. I’ll update our library to match that. If you know of any info about how to use a an even lower timing budget with the ST API, let me know and I can try to make the library support that too.
Kevin