CSV Time always the same

Jing

Customer consultation
I just bought a HANTEK oscilloscope with type DSO2D10. I've problem with saving CSV. I get the same time value at this CSV. I attached the capture picture and its CSV. I hope I can get the solution. Many thanks.

Jing

Reply
The time in the CSV table means the time interval.

oscilloscope

Hello, he mean that this number it's the same in all the csv. It never gets updated, please use this function and see the value it's the same on the entire file and it should be an incremental value based on the time (nS,uS,mS) that was taken.

morgan_flint

I guess this bug is the same that was reported in this thread:
https://www.eediscuss.com/forum. ... &extra=page%3D1
It remained unanswered.
The csv reported by Aletek was like this:
Time ,CH1 [V]
2.000000e-06,-0.080000000000,
2.000000e-06,-1.520000000000,
2.000000e-06,-3.200000000000,
2.000000e-06,-3.680000000000,
2.000000e-06,-3.840000000000,
2.000000e-06,-3.840000000000,
2.000000e-06,-3.920000000000,
2.000000e-06,-3.840000000000,
2.000000e-06,-3.760000000000,
2.000000e-06,-3.760000000000,
2.000000e-06,-3.680000000000,
2.000000e-06,-3.680000000000,
2.000000e-06,-3.680000000000,
2.000000e-06,-3.680000000000,
2.000000e-06,-3.680000000000,
2.000000e-06,-3.520000000000,
...

I guess the incremental for time could be calculated by accumulating the timebase in the first column in a spreadsheet, like this:
Time         CH1 [V]        Time (acum)
2,00E+00        -0.080000000000        2,00E+00
2,00E+00        -1.520.000.000.000        4,00E+00
2,00E+00        -3.200.000.000.000        6,00E+00
2,00E+00        -3.680.000.000.000        8,00E+00
2,00E+00        -3.840.000.000.000        1,00E+01
2,00E+00        -3.840.000.000.000        1,20E+01
2,00E+00        -3.920.000.000.000        1,40E+01
2,00E+00        -3.840.000.000.000        1,60E+01
2,00E+00        -3.760.000.000.000        1,80E+01
2,00E+00        -3.760.000.000.000        2,00E+01
2,00E+00        -3.680.000.000.000        2,20E+01
...

Of course, it'd be better if the scope exported the csv with this information, but maybe this workaround could be enough