This would be quite useful based on my recent observations on 6m. We all
suffer when someone inadvertently transmits across two periods. I have
on occasion sent something like
PA0XX CLOCK or indeed DL0XX, ON0XX and G0XXX of course :-)
It normally works but it feels wrong because the station does not know
who the message is from. I don't like doing it and it really is a last
resort. Other problem is TX distortion/overmodulation/wide signals.
Messages to cover that would be useful, after all no one want to radiate
a bad signal or cause unnecessary interference do they? We need a better
expression than PA0XX WIDE, it seems too confrontational.
I do hope that when conditions on 6m get even better that alternative
frequencies are used.
73
Conrad PA5Y
On 2018-05-15 11:43, Mark Turner via wsjt-devel wrote:
Having just watched another station sending a "CHK TIMING" message in
FT8, which is obviously not likely to succeed...
I was wondering if a non-timing-critical "message" could be added to
the protocol, e.g. four continuous tones - or some such combination
that is unlikely to happen randomly, but could still be interpreted by
someone (and/or the software) who's clock was too far out - maybe a
big "CHECK YOUR PC CLOCK" message could be displayed in their client
:)
Regards, Mark
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
