confusing timestamps

Forum for discussing PicoScope version 6 (non-automotive version)
Post Reply
stevenvh
Newbie
Posts: 0
Joined: Mon Feb 09, 2015 3:02 pm

confusing timestamps

Post by stevenvh » Sun Mar 22, 2015 2:33 pm

I have this stored data, 200s/div, 100kS:

0.00000000 0
0.01999960 0
0.03999920 0
0.05999880 0
...
19.95959989 0
19.97959949 0
19.99959908 0
20.01959868 1
20.03959828 1
...
1999.89990963 0
1999.91990923 0
1999.93990883 0
1999.95990843 0

The value of 1999.93990883 is the 100 000th sample, so its timestamp should be 2000.00000. The actual value is 30 ppm off. Maybe not a big deal, but the data is now more difficult to read. It also raises the question: where does it get those numbers? If all you have is one clock, which clocks the samples, shouldn't every sample be dead on, no matter what the clock's deviation might be? Are there two competing clocks in play here?

Martyn
Site Admin
Site Admin
Posts: 3225
Joined: Fri Jun 10, 2011 8:15 am
Location: St. Neots

Re: confusing timestamps

Post by Martyn » Tue Mar 24, 2015 1:40 pm

You would need to look at View->Properties to check exactly what sample interval the scope was set to.
Martyn
Technical Support Manager

Post Reply