Products > Test Equipment
Time sync system clock R&S RTB2004
(1/9) > >>
R.J.:
I am the proud owner of an R&S RTB2004.
Connected to the internal network of my home, using the web browser integration, remote control of this oscilloscope is very convenient.
I have now found out that when creating screenshots, the system clock of this oscilloscope does not synchronise with the system clock of e.g. the computer(s) on the network. After leaving the device switched off for several weeks, it appears that the clock is several minutes behind.
There is no possibility in the menus to synchronise this time or to synchronise it with e.g. the router acting as NTP server in the network.
The clock can only be set to a time.
This is quite a bad thing, as time synchronisation within a network is essential for many devices.

Perhaps there is a possibility of using a SCPI command to synchronise the system time to the DHCP server/router acting as an NTP server.
I have searched but cannot find a solution.

Does anyone know of a solution?

pdenisowski:
You can set the time on the RTB2000 using SCPI commands:

SYSTem:TIME <Hour>,<Minute>,<Second>
R.J.:
Thank you for replying.
But that's manual setting the time and is not in sync.
I can also set the time by using the menu.
This is not what I want to do.
pdenisowski:
Sorry, I assumed that you wanted the RTB2000 time to match the time of a computer on your network.  Is it possible to run (manually or automatically, e.g. using a cron job) a script on one of your computers that checks that computer's time and then issues a SCPI command to the RTB?  I can write an example in Python if that would be helpful.
R.J.:
Thanks for your offer.
But weird that such an elaborate device like this scope does not have by default the ability to conform to a system time within an environment it is in. A system time is the most important parameter when it comes to things that are somehow interconnected, dependent on each other and evidence to/about each other.
The menu for TCP parameter settings should also provide an option to retrieve a system time according to the NTP protocol from the DHCP server so that the oscilloscope's system time has a reference.
Then there is no room for error in a script that would have to run on some PC.

Am I the only one who has experienced this "problem" and is now finding out?
Navigation
Message Index
Next page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod