Set data file clock

morgan_flint

Hello, Jing, in fact, the file name has a meaning, it's related to the time the system has been on: DSO_MM_dd_hh_mm_ss.BMP where MM=month, dd=day, hh=hour, mm=minute, and ss=second.

The system must have an internal clock set at Linux epoch time (01/01/1970 00:00:00) on startup. It would be a good idea to add the possibility to set it up, for example under the "utility" menu. Obviously, as there isn't real-time clock hardware in the DSO, it would reset to epoch time on startup but, if you're going to make several captures, the convenience of having them correctly labeled would compensate for the hassle of entering in the menu after powering it up

morgan_flint

Hello again, Jing

After installing Keysight IO Libraries Suite 2022, I decided to investigate if there was a possibility to set time and date with SPCI commands. After some googling I found the command SYSTem:TIME? (not documented in the SCPI manual for DSO2000 series) was working correctly, returning something like 1970;1;1;0;10;48 (depending on the up time). But the usual syntax for setting time like SYSTem:TIME hh,mm,ss didn't work. After a more specific Google search, I found SCPI Remote communication control manual for DSO4000BC, where SYSTem:TIME? was explained on page 78, along with the SYSTem:SET:TIME command.

So I tried this command with the syntax explained there and bingo! the time and date could be set to the present time!
I think this is very convenient as, if you don't set the time/date, it will be more difficult to sort, find or classify the captures in the future, unless you rename them by hand on the fly.

I'm attaching a capture of the Keysight Interactive IO dialogue and another capture of the file browser showing a screen saved to USB with the name correctly showing the present time as well as the file modification date.