Occasionally, I like to head out in the truck and run JT65, or even let WSPR run a while from some remote or hilltop location.
The laptop I use for mobile op happens to have a pretty crummy clock – it can easily loose several seconds per day. (Of course this is not a problem when at home and connected to the net – I use Dimension4 to keep clock synch.) I imagine that the internal clock in many laptops suffers from this same problem – and as you know this makes any type of timed operation difficult or impossible when mobile.
To address this issue, I made a little windoze app that synchronizes the laptop clock to “0” seconds when a button is clicked. - See attached image...
One button syncs to the current second - I use it for JT65 operation – listen for when everyone else starts TXing, click the “Zero to CURRENT Minute” button, and next time around JT65 will be close enough to decode and be decoded.
The other button syncs to an even second – I use it for WSPR operation - listen for when everyone else starts TXing, click the “Zero to EVEN Minute” button, and next time around WSPR will be close enough to decode and be decoded.
Both functions work quite well, but as you can imagine, it’s not hard to be “off” by an integer minute or a few integer minutes. This doesn’t really matter for JT65. But for WSPR, this will put good decodes, but possibly with the wrong minute value, into the WSPR database. In fact, the decodes shown in the attached screenshot are in the WSPR database, but are 2 minutes off – bad me!
I am thinking of releasing the app for download. Mobile JT65 and WSPR is fun. I have no problem releasing the JT65 version – being off a minute or 2 is not an issue. But, if I do release this little app with the WSPR “Zero to EVEN Minute” button, then eventually bad times are going to end up in the data base. Probably not many, but it will happen.