RangeFinder: LidarLightV3HP I2C update rate slow?

This is slightly anecdotal but while testing a LidarLightV3 I have noticed that the range shown in the Ground Station, although accurate, seems to update very slowly as compared to the LidarLightV2.

I performed back-to-back tests. The VCC, GND, SDA and SCL lines were connected directly to the Pixhawk's I2C port similar to what is shown [here on the wiki](http://ardupilot.org/copter/docs/common-rangefinder-lidarlite.html#connecting-to-the-pixhawk-via-i2c). A wiring diagram is also shown below although in my case I did not use a BEC. Still, I suspect skipping the BEC is not the cause of the slow updates.


Start by reproducing the back-to-back LidarLightV2 and LidarLightV3 tests using the Pixhawk I2C wiring described in the issue and observe the Ground Station update rate. No source file or test is identified; done means determining whether the V3 update rate is genuinely slower and documenting or addressing the cause.

Written by the indexing model from the issue text.