On Thu, 16 Feb 2023 16:28:23 +0000 Andy Durbin via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
> I was very surprised to hear the reports of a large clock error > causing their TX on the wrong cycle. It seems that one of their two laptops had a 14 second time error early in their 8 days on Bouvet, by the last few days they had ironed this out and both were pretty much synced to the correct time. I heard them for a few hours total on 17m at about 1700 to 1900 UTC during the few days before they went QRT, however despite trying to find a quiet spot above 1000Hz offset (which may have not been quiet at their end of course) I wasn't able to work them during a couple of hours of trying. To get a bit more on topic for this list, perhaps Joe and the other developers can think of a way of identifying and correcting these errors with only simple operator intervention. I think the difficulty is that with so few bits in each transmission there are none spare to indicate even/odd or indeed time errors. -- Brian G8SEZ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
