Docs are here: http://www.14point7.com/Support/Softwar ... tation.zip
Initial support will be purely logging, and even that will need special support added to OLV:
Perhaps I can convince Alan to provide an alternative non floating point data format. Or perhaps it's easier than I originally thought.
Analysis of lambda output var requirements:
Lambda in range: 0 - 2.0 (0.68 - 1.36 (10:1 - 20:1 AFR for gasoline) are its analogue output levels and reasonable defaults, but that's only 8 bit).
Quoted accuracy: 0.01 when the sensor is in good condition, without free air calibration.
2.0/0.01 = 200 steps, so an 8 bit unsigned with fixed scaling would work fine.
I'd suggest that it should be output as 16 bit fixed point numbers with specific scales for each variable as that seems excessive and is simple to parse, and fast to transmit/receive.
Even if you expand to 4.0 and 0.001 accuracy you only end up with a range of 4000 steps. Following that logic you could go to 0.0001 accuracy with 0 - 6.5 lambda range, or 0.001 accuracy with 0 - 65 lambda range, or any other reasonable combination.
The first step will be logging support.
From the docs.Lambda: Range is 0.68 to 207 Lambda
32bit IEEE 754 formatted floating point number.
[Byte3 ][Byte2][Byte1][Byte0]=[Bit31 Bit30 … Bit24][Bit23 Bit22 … Bit16] [Bit15 Bit14 … Bit8][Bit7 Bit6 … Bit0]
*Byte3 is the first byte received
Sign Bit = Bit31
Exponent = Bit30 … Bit23
Significand = Bit22…Bit0
Format info: http://en.wikipedia.org/wiki/Binary32
Calculator: http://www.h-schmidt.net/FloatApplet/IEEE754.html
Easy in Java: http://download.oracle.com/javase/6/doc ... t%28int%29
Fred.