Only some are due to lack of internet. USB GPS receivers are now approx $12 USD on Ebay. I have tested a few and they work fine with NMEAtime2. Which is none simple software. The message could suggest what to do for both internet connected and off-grid users. But really, to keep the message short, it should point to a help page or file that is specific to time setting options, rather than a huge user guide, since the public no longer reads very much.
With regard to time setting software, I really can't recommend BKTtimeSync for the same reasons we are discussing this issue: It works for me but is far too complicated for the average ham, and lacks sufficient docs or help. But NMEAtime2 is really simple and just works, for using GPS. For internet users, NetTime or Dimension4 for basic users or Meinberg NTP for more advanced users. BUT!!! All of the users, both internet and GPS, need to be reminded to turn OFF windows automatic time setting before using the software's above. I see too many users whose DT is swinging wildly between plus and minus 2.5 seconds, then next at 0.2 DT. This is because they have windows trying to set time while also using the above programs to set time, and the two are fighting a tug of war. If you guys put a DT warning message in the code that points to a time help page, then I volunteer to be one of several editors for the above type of help content about time sync'ing options. Cheers, Neal N6YFM On Wed, Jun 26, 2019, 3:16 AM <wsjt-devel-requ...@lists.sourceforge.net> wrote: > Send wsjt-devel mailing list submissions to > wsjt-devel@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > or, via email, send a message with subject or body 'help' to > wsjt-devel-requ...@lists.sourceforge.net > > You can reach the person managing the list at > wsjt-devel-ow...@lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of wsjt-devel digest..." > > > Today's Topics: > > 1. Re: Clock patch (DG2YCB, Uwe) > 2. Re: Clock patch (Roeland Jansen) > 3. Re: Clock patch (Bill Somerville) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 26 Jun 2019 11:36:58 +0200 > From: "DG2YCB, Uwe" <dg2...@gmx.de> > To: "'Black Michael'" <mdblac...@yahoo.com>, "'WSJT software > development'" <wsjt-devel@lists.sourceforge.net> > Subject: Re: [wsjt-devel] Clock patch > Message-ID: <004801d52c02$b33f1430$19bd3c90$@gmx.de> > Content-Type: text/plain; charset="utf-8" > > I?ve not yet seen the results, but your this approach really looks like > something which could bring a substantial progress regarding the timing > issue. > > > > Reason why I am supporting a warning message is that, besides field days, > I saw dozens of OMs/YLs who are not aware at all that system time of their > PCs needed to by synced. Alone two examples yesterday. Contacted both. > Seemed to be both are ?old? men, with no computer skills. One replied the > following: ?I am no longer a very young man (84 years old) who tries to > tamper with the new methods; with a total ignorance of the English > language??. If we like it or not: That?s the reality! Of course we could > let FT8, FT4, etc. be something only for the tiny community of > well-educated, scientifically trained OMs with good to excellent computer > skills. But if we want to make QSOs with more OMs/YLs, then WE need to do > something which helps THEM to overcome the hurdles. > > > > 73 de Uwe, DG2YCB > > > > Von: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > > Gesendet: Mittwoch, 26. Juni 2019 06:19 > An: WSJT Software Development > Cc: Black Michael > Betreff: [wsjt-devel] Clock patch > > > > This patch shows a message if 80% of DT values are >= 0.5 seconds. > > > > https://www.dropbox.com/s/8j7qao9wa4wmzdm/clock.patch?dl=1 > > > > I picked the 50% point of FT4's 1 second tolerance but perhaps a slightly > larger value might be appropriate. > > > > I think most, if not everybody, can get the > 20% < 0.5 seconds without a > problem. > > > > Even with my rather extreme latency of 300-400ms I don't trigger this. > > > > de Mike W9MDB > > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 2 > Date: Wed, 26 Jun 2019 11:55:47 +0200 > From: Roeland Jansen <roeland.janse...@gmail.com> > To: WSJT software development <wsjt-devel@lists.sourceforge.net> > Subject: Re: [wsjt-devel] Clock patch > Message-ID: > < > caj2u8oytzmmcmcauqppc9d3hk+6jxw1nxnvht-5auv5t5wt...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > I did not look at the patches Mike sent but: > > https://time.is/ > > gives you how good/bad the time is. If you start up: do check like this > and refuse to go on if the timeskew is too large. > Add a link how to fix in the message and you force people to fix it. > > (not that people read notices) > > just my bad idea. > > > On Wed, Jun 26, 2019 at 11:41 AM DG2YCB, Uwe <dg2...@gmx.de> wrote: > > > I?ve not yet seen the results, but your this approach really looks like > > something which could bring a substantial progress regarding the timing > > issue. > > > > > > > > Reason why I am supporting a warning message is that, besides field days, > > I saw dozens of OMs/YLs who are not aware at all that system time of > their > > PCs needed to by synced. Alone two examples yesterday. Contacted both. > > Seemed to be both are ?old? men, with no computer skills. One replied the > > following: ?I am no longer a very young man (84 years old) who tries to > > tamper with the new methods; with a total ignorance of the English > > language??. If we like it or not: That?s the reality! Of course we could > > let FT8, FT4, etc. be something only for the tiny community of > > well-educated, scientifically trained OMs with good to excellent computer > > skills. But if we want to make QSOs with more OMs/YLs, then WE need to do > > something which helps THEM to overcome the hurdles. > > > > > > > > 73 de Uwe, DG2YCB > > > > > > > > *Von:* Black Michael via wsjt-devel [mailto: > > wsjt-devel@lists.sourceforge.net] > > *Gesendet:* Mittwoch, 26. Juni 2019 06:19 > > *An:* WSJT Software Development > > *Cc:* Black Michael > > *Betreff:* [wsjt-devel] Clock patch > > > > > > > > This patch shows a message if 80% of DT values are >= 0.5 seconds. > > > > > > > > https://www.dropbox.com/s/8j7qao9wa4wmzdm/clock.patch?dl=1 > > > > > > > > I picked the 50% point of FT4's 1 second tolerance but perhaps a slightly > > larger value might be appropriate. > > > > > > > > I think most, if not everybody, can get the > 20% < 0.5 seconds without a > > problem. > > > > > > > > Even with my rather extreme latency of 300-400ms I don't trigger this. > > > > > > > > de Mike W9MDB > > > > > > > > > > _______________________________________________ > > wsjt-devel mailing list > > wsjt-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 3 > Date: Wed, 26 Jun 2019 11:15:52 +0100 > From: Bill Somerville <g4...@classdesign.com> > To: wsjt-devel@lists.sourceforge.net > Subject: Re: [wsjt-devel] Clock patch > Message-ID: <4c971df3-778b-86c6-a947-49c4ed9d7...@classdesign.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 26/06/2019 10:55, Roeland Jansen wrote: > > I did not look at the patches Mike sent but: > > > > https://time.is/ > > > > gives you how good/bad the time? is. If you start up:? do check like > > this and refuse to go on if the timeskew is too large. > > Add a link how to fix in the message and you force people to fix it. > > > > (not that people read notices) > > > > just my bad idea. > > Hi Roeland, > > doesn't that miss the point that many of the poor time sync situations > are where the user has no Internet connectivity? > > 73 > Bill > G4WJS. > > > > > ------------------------------ > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > ------------------------------ > > End of wsjt-devel Digest, Vol 64, Issue 164 > ******************************************* >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
