Discussion in 'Amateur Radio News' started by KB7TBT, Jun 9, 2019.
Must be running Windows...
...ntp(d) is standard in Debian Stretch. Yay Linux!
DX Commander has a nifty feature to take care of this. - Set radio UTC time on startup or selection, and at the beginning of each hour.
There is a way the time sync can be done in Linux using a u-blox7 GPS/Glonass device. In one of his demos, OH8STN used this and described it's use (for those not wanting to stay with Windows).
73, Larry WB8LBZ
El Paso, TX
The ntp service is also standard in Windows 10. The link below covers pretty much every option available.
ntpd is standard in every Linux distro as far as I know. Not every distro activates ntpd by default.
KB9RLW is demonstrating modern day amateur radio by taking advantage of the computer interface the Icom radios come with these days and "home brewing" a solution. Kudos! I don't know why I didn't think of doing this!
Accurate time was important to hams a few years ago before the logging requirement went away (within a minute). Then there was a period where time wasn't all that important. Then Joe Taylor comes along and accurate time is important again (within a second).
When there was a threat of NIST zeroing out the budget of the (getting old) NIST-F2 clock using the (even older NIST-F1) clock as a backup last year, there was a frenzy of postings about it. The NIST-F2 is the most stable (of the two) with a drift of less than 4 nanoseconds per year. (That's pretty darn accurate!)
The Navy has dozens and dozens of atomic clocks syncing up with each other and GPS satellites (with at least two atomic clocks on each satellite for redundancy/error checking). All together, their drift is a few picoseconds per year. That's about 1,000 times more accurate than NIST.
So I set up an NTP server (using Fedora) and hooked it up to a GPSDO with a PPS. Now I point all my other computers to it. My time hack is within a couple of milliseconds now.
Every once in a while, I saw the clock on my 7300 off by a minute or so. And of course, twice a year, I'd have to add an hour to it or subtract an hour from it. And if you disconnect power for a week or so, it loses time because the clock battery is a lithium and needs power applied to keep it charged.
Now, KB9RLW shows us how to take our computer time and put it into a 7300 without having to wait for the second hand to hit the top of the clock or the beep from WWV. I think that's absolutely fantastic!
Now, instead of trying to transcribe his code from the video, I'm looking for it to copy/paste somewhere on the net. Or, maybe I'll just write my own code. Although my 7300 doesn't need accurate time to USNO resolution... why not?
Using a u-blox USB GPS receiver works and is within a second (no PPS, data transfer time...), so that would be good for most. Pointing your computer to windows.time would be good for most also.
Heck, my radio doesn't even have a clock! Interesting video though.
I'm not sure if the 7300 is the same as the 7610 as far as the time is concerned, but I have my 7610 hooked to the internet using the ethernet jack on the back. The clock is spot on, but if it does need updating, I just hit the NTP update button in the menu and it's done. No need for any of this.
My 7300 never needs adjusting. It is always right on. I never really use it however. I don,t even change it for Daylight saving. I always have my computer running next to my rig so by habit, I use the clock on the computer. I do all paper logging except for contesting. I later manually enter contacts into eqsl, except for contesting which is a compute file upload. I just checked the clock now, it is still right on. Also note, I leave the radio off when not in use, but leave the power supply on always.