Greg,
We have been working with the V1 off-season to learn its capabilities. We'd be interested in your experience and sharing your Labview code.
I have a V2 on order. From what I have read about the V2, there should not need to be library updates to communicate, but it does require some different I2C commands to get data. It no longer uses the ACK/NACK to signal that it has completed the measurement process.
According to their website page here:
http://pulsedlight3d.com/products/li...-v2-blue-label
"Now broadly compatible with the most basic of I2C drivers and most micro-controller boards. Instead of “ack” and “nack” responses when the sensor is available or busy, a status register (0x01) can be queried to indicate sensor status.
The previous measurement value can be read at anytime during an acquisition until it is overwritten by a new value. No need to wait for the sensor to become available to read data. Just fire it up and let it rip!"
For the V1, I'm curious about how you did the data read. We are using a time delay between the write command to take a measurement and then reading that measurement. I was never able to find a way to sense the ACK/NACK status using Labview.
-Steve