I am a recent purchaser knowing that the specs were fantasy but so far I am well pleased with the device for the modest outlay.
One thing I am investigating is how to interpret the waveform .wav files as this can be useful for long term storage and further analysis on a computer. The aim is to write a script to transform the wav format into something more friendly like a spreadsheet or csv file. I am using intermediate versions of this to allow comparison between captures with different settings, data etc.
What I have discovered so far about the 15000 byte files is
0-999 Header data
1000 - 3999 CH1 data1
4000 - 6999 CH2 data1
7000 - 8499 CH1 data2
8500 - 9999 CH2 data2
10000 - 14999 seems to be just nulls in my captures so far.
The header data
CH1 vertical scale at 4 where 0-6 represents 5.0V,2.5V,1.0V,500mV,200mV,100mV,50mV/div
CH2 vertical scale at 14 (same as CH1
Time scale at 22 (repeated at 52 where 0 - 29 represents
50S,20S,10S,5S,2S,1S,500mS,200mS,100mS,50mS,20mS,10ms,5mS,2mS,1mS,
500uS,200uS,100uS,50uS,20uS,10uS,5uS,2uS,1uS,500nS,200nS,100nS,50nS,20nS,10nS
Ch1 measurements at 208 - 255 (12 4byte fields)
Ch2 measurements at 256 - 303 (12 4byte fields)
Ch dataBlock1 1500 2 byte fields (little endian) which represent in some way the vertical measurement on the screen. I.e. doubling sensitivity doubles the values in this block.
I would be interested if anybody has any knowledge or insights in this area e.g. similarity to other formats, so I can avoid unnecessary work.
My current investigation is focussed on two area.
1) The representation of the data in dataBlocks1 and 2 in order to be able to transform it into 'real data'
2) The mapping of the measurement data regions on to the parameters and the encoding used in each 4 byte value. I have an inkling that the first byte is a type indicator and the next 3 are little endian values (maybe fixed point).