> nobody had a GPS time sync (which I find almost unbelievable). Boggles the mind.
On Wed, Feb 15, 2023 at 10:20 AM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > TimeFudge will not correct a 15-second error. > > Their clock was apparently 15 seconds off and nobody had a GPS time sync > (which I find almost unbelievable). > > Heck...my watch I've had for 50 years is more accurate than that and > TimeFudge would have fine-tuned it. > > Mike W9MDB > > > > > > > > On Wednesday, February 15, 2023 at 10:06:58 AM CST, Henryk Majcher via > wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote: > > > > > > Hi Fred > > The software "TimeFudge" by Mike W9MDB fixed such a problem. > This is time synchronisation to other stations (they have accurate time). > The DX expedition does not need GPS or the internet to do time > synchronisation. > > 73 > Henryk SP3E > > śr., 15 lut 2023 o 13:22 Fred Carvalho via wsjt-devel < > wsjt-devel@lists.sourceforge.net> napisał(a): > > GM to all > > > > *This concerns F/H operation in 3Y0J* > > > > During the DXpedition the team announced multiple times that they were > using WSJT DXPedition Mode (F/H). However, FOX was most of the time in ODD > periods and accepted reports in any spot in the channel. QSY below 1000Hz > was not necessary. My QSOs with them were always like that. It took me some > time to understand how to work them, which I think was the same to most of > the callers. BTW, I have never seen FOX out of sync. The worst that I can > remember was 0.4s. > > > > Many thought – myself included- that they were not using WSJTx, but some > other multistream DXP mode application. However one of the operators > confirmed to me that they have used WSJT software. > > > > After the expedition they have stated that : “ We had issues with the > FT8 due to we did not have any device to sync against, and our clock was 14 > seconds off - which meant we at some time were TX odd, while we thought it > was even.” > > > > Well a simple GPS device connected to one of their notebooks would have > prevented the problem above. > > > > So my questions to the developers are: > > > > a) Is it really possible that lack of sync would lead them to TX in > ODD periods as FOX ? > > > > b) How come QSY below 1000 HZ was not necessary for the Hound to > finalize the QSO with them? > > > > This is very intriguing to many of us. Some clarification on what > happened is very much appreciated > > > > Thanks Fred PY2XB > > > > -- > > Fred - PY2XB > > > > > > PY2FXH, PY2FXH/W2, PY2FXH/9, PY2XB/0, F/PY2XB, ZX2XB, PT7BXB, > PY2XB/PY0F, PQ0F, VP5/PY2XB, PW2IO (SA-071), ZX8W (SA-060), PY2XB/1 > (SA-029), 8P9XB, PQ8XB (SA-045), ZX2S (SA-028), PR7XB > W4/PY2XB, 3D2XB, PY22XB,PY0FX, W2/PY2XB, W9/PY2XB, VE3/PY2XB, PY2XB/5 > > Team member : PW2M (SA-071), PX8J (SA-041), T30PY - T30SIX, PT0S, 9M0W > > > > > > _______________________________________________ > > 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 > -- --w8lvn--
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
