Do not understand all the ragging about other people’s incorrect computer time. It’s their problem, not ours (mine). I simply avoid them and they miss out on a contact. Now that out of adjustment time is flagged, it’s a non issue.
BTW if all returns are flagged as out of sync it’s your computers problem, not the rest of the world. I agree, let’s not turn a fantastic application into bloatware like Apple’s I-tunes and versions of Windows. Fantastic field day on FT8. Regards and 73s Frank VE3FBZ London Amateur Radio Club www.larc.ca > On Jun 24, 2019, at 06:00, Hasan al-Basri <hbasri.schie...@gmail.com> wrote: > > I also agree with Fred, why do we constantly focus on reinventing the wheel? > > WWV or other world time services and a mouse click will even work. A Cheap > CASIO watch has NIST time in it for $30. (works well Stateside). > > The GPS dongles are dirt cheap and some even come with time setting software. > Another good program for setting time from GPS is NMEATime2, which I use. > > Let's not turn WSJT-X into Bloatware just because people can't seem to set > their own clocks from readily available sources. I'm not disputing the > problem, (FD particularly is full of incompetent first time, ill-trained > digital ops who have the thought, "oh, wouldn't this be fun, I'll show the > guys what a cool mode this is"). > > I just don't agree with constantly trying to make up for poor operating > practices with software solutions. > > In WSJT-X, not setting one's clock when only a cursory RTFM, as well as > minimal effort and investment are required is, to my mind, poor operating > practice. > > ...and BTW, get off my lawn. :-) > > 73, N0AN > > Hasan > > >> On Mon, Jun 24, 2019 at 4:11 AM Tom Melvin <t...@tkrh.co.uk> wrote: >> All >> >> This posting by Fred gets my vote - easy, fool proof and does not distract >> the dev team. >> >> >> -- >> 73’s >> >> Tom >> GM8MJV (IO85) >> >> >> >> >> >>> On 24 Jun 2019, at 09:27, Fred Price <n...@hotmail.com> wrote: >>> >>> You are all overthinking the problem. There are programs to set your >>> computer clock by a GPS dongle. A good plug in dongle from Amazon is $12USD >>> and the program I use BktTimeSync is a free download. >>> Also if the dev group keeps adding more n more WSJT will become bloatware. >>> I'd rather see improvements in what is in the software already. If you want >>> a color to denote a time that is getting out use JTAlert, it already has >>> that in it. >>> >>> On Jun 24, 2019 4:07 AM, "DG2YCB, Uwe" <dg2...@gmx.de> wrote: >>> A very good idea to set up time beacons, Reino! I like this approach! >>> >>> >>> However, as a short-term solution IMO dev team should find a way to use the >>> EXISTING data set of DT values for a pop-up saying that very likely time is >>> not synced correctly, plus an option to correct time by one click. Look the >>> following example. Only one station has a DT value which is totally out of >>> the average. Would be easy to detect such things by any well programmed >>> algorithm. Even the old JT65-HF software had two additional buttons, where >>> one could simply set PC clock + or – some 100 ms (until +- 2.5 s). Was very >>> helpful for fieldday activities. Just click on + or – as long as most of >>> the other stations have DT around 0. Simple approach, but worked 100%. >>> >>> >>> >>> 73 de Uwe, DG2YCB >>> >>> >>> -----Ursprüngliche Nachricht----- >>> Hi, >>> >>> >>> We are amateurs and could provide another time distribution experiment >>> especially during Field Day events. I mean setting up time beacon or >>> beacons that send e.g. every 15 s a short pulse, say 100 ms, on the base >>> carrier frequency e.g. 14.080 MHz. Timing of that pulse could be 'minute >>> mark - 1 s' or something similar agreed time. It would allow manual PC time >>> setting in the same manner as time marks of standard frequency stations. >>> That transmission would not disturb any FT8 message as nobody should >>> transmit at that time. It could be more useful, if the beacon frequency is >>> set to 1 kHz up (14.081), then you could hear it without detuning VFO and >>> disturbing you normal operation. Well, you could get same information from >>> dT values providing there are enough time accuracy in other stations and >>> you timing is good enough for decoding. >>> >>> >>> Of course those beacons should be carefully synchronized to an accurate >>> time reference e.g. GPS. Depending on local regulations also a station >>> identity shall be sent at regular intervals using some applicable >>> modulation perhaps just before the time tick. I think that voluntary >>> stations would provide this service as needed. >>> >>> >>> You could automate the time setting with a suitable program, if that could >>> be made safely and reliably (perhaps the pulses needs to be modulated for >>> identification), but that's next step if ever considered useful. >>> >>> >>> 73 Reino oh3ma >>> >>> >>> >>> >>> _______________________________________________ >>> >>> wsjt-devel mailing list >>> >>> wsjt-devel@lists.sourceforge.net >>> >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> wsjt-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
