Wow, that IS significant! I didn’t hear them on many sequences except for one day on 17M at home and later with K5CS at the BAT station. We didn’t notice their clock being off and copied them well, but if they were 14.x seconds off, it would look good but they would be on the wrong sequence. I don’t even want to think about what that would do to F/H operation. However, if we were locked to the proper sequence by being in hound mode, we shouldn’t copy them if they had shifted <>15 seconds. Of course, we aren’t transmitting if we don’t copy them, so we should decode them on either sequence unless they were too far off in time for decoding. .
They should have had JTsync. It sets your clock by monitoring and averaging FT8 traffic. However, if your computer clock was <>15 seconds off, it would lock onto the wrong sequence. I guess…..this is getting way over my head. Makes my head hurt. I like CW!
Dennis/RZ
dit dit
On Feb 15, 2023, at 9:37 AM, Scott Branyan <[email protected]> wrote:
>> We had issues with the FT8 due to we did not have any device to sync against, and our clock were 14 seconds off - which meant we at some time were TX odd, while we thought it was even.<<