Rigol MSO 5000 NTP?

[The Doktor]

My MSO 5000 is going to be connected to my network, and I hate inaccurate clocks. Is it possible to enable or install NTP or SNTP? Bonus if it can also handle DST automatically. Google doesn't seem to be much help on this 1.

Ed

[Fungus]

Doktor, heal yourself!


From the programming guide:



Just set up a cron job to connect to the 'scope and set the time every few minutes.

[ken830]

The SCPI command documentation is inaccurate. The scope completely ignores the "seconds" value and always sets it to 0 (zero).

[tv84]

The SCPI command documentation is inaccurate. The scope completely ignores the "seconds" value and always sets it to 0 (zero).

Simple, send the command at 0 seconds.

[ken830]

Actually, now that I looked at it closer, there is something SERIOUSLY wrong with the time.

Here I am sending

Code: [Select]

:SYSTem:TIME? once per second continuously and this is the response:

Code: [Select]

:SYSTem:TIME?
1,6,44
:SYSTem:TIME?
1,6,45
:SYSTem:TIME?
1,6,46
:SYSTem:TIME?
1,6,47
:SYSTem:TIME?
1,7,48
:SYSTem:TIME?
1,7,49
:SYSTem:TIME?
1,7,50
A minutes later:

Code: [Select]

:SYSTem:TIME?
1,7,47
:SYSTem:TIME?
1,7,48
:SYSTem:TIME?
1,8,49
:SYSTem:TIME?
1,8,50
:SYSTem:TIME?
1,8,51
:SYSTem:TIME?
1,8,52
Another minute later:

Code: [Select]

:SYSTem:TIME?
1,8,46
:SYSTem:TIME?
1,8,47
:SYSTem:TIME?
1,8,48
:SYSTem:TIME?
1,8,49
:SYSTem:TIME?
1,9,50
:SYSTem:TIME?
1,9,51
A few minutes later:

Code: [Select]

:SYSTem:TIME?
1,16,49
:SYSTem:TIME?
1,16,50
:SYSTem:TIME?
1,16,51
:SYSTem:TIME?
1,16,52
:SYSTem:TIME?
1,16,53
:SYSTem:TIME?
1,17,54
:SYSTem:TIME?
1,17,55
:SYSTem:TIME?
1,17,56
A couple minutes later:

Code: [Select]

:SYSTem:TIME?
1,18,52
:SYSTem:TIME?
1,18,53
:SYSTem:TIME?
1,18,54
:SYSTem:TIME?
1,18,55
:SYSTem:TIME?
1,19,56
:SYSTem:TIME?
1,19,57
Is it keeping time wrong? Is it rolling over on the wrong second? Does the rollover second advance by one when I issue a SCPI command to read the time? What the heck is going on?!

[ken830]

Okay. I stopped issuing SCPI commands and I've been timing the clock minute rollover with my phone's stopwatch for the last 40 minutes and it appears to be slow. Each minute rolls over somewhere between 60.5 and 61.0 seconds. It's already over 22 seconds slow after 40 minutes.

[ken830]

Another update... After 2 hours, I was expecting the clock to be a whole minute slow, but it wasn't. So, I think the time-keeping is accurate, but the display isn't refreshed immediately when the minute rolls over. It's some interval >60 seconds. So, if I watch it carefully, I should be able to see the minute jump by 2. I don't know if I have the patience for that though. To test this theory, I did re-synced the time the best I could with my script right at the top-of-the-minute and for some reason, this time around, the very first minute rollover occurred about 20+ seconds after the top-of-the-minute; so about 80+ seconds after being set. So I waited about 40 minutes later and I did a "print screen" immediately after the top-of-the-minute (according to my desktop computer's clock and my phone's stop-watch) and the screenshot clearly shows the actual time (file date/time and printed at the top of the image) and the displayed time (shown on the bottom-right corner of the screen are off by 1 minute.

This file date/time is 04:57:01. The time printed on top is 04:57:00. The time displayed on the screen is 04:56
" alt="" class="bbc_img" />

The screen didn't change to 04:57 until ~33 seconds later.
" alt="" class="bbc_img" />


EDIT: And speaking of time, it seems EEVBlog doesn't auto-adjust for my local daylight-savings time adjustment that was supposed to happen a little over 2 hours ago. I guess I'll have to do that myself.