Hi Jay,
On 9/20/2017 5:08 PM, Jay Hainline wrote:
Joe and all. Curious because I am not a big contester. My understanding is the
reason for the extra coding is for producing the message sent for TX3 with both
calls plus R Grid. If it’s a problem with extra characters involved, why can't
you just condense the standard message to send a single call of the station you
are working with R Grid? Wouldn’t this save the effort of having to use extra
coding in the software for converting an odd ball grid to something that makes
sense? Then no matter if you are in contest mode or not, everyone would see the
same message.
Example:
Current TX3 message in contest mode: K1JT KA9CFD R EN40
Replace TX3 message transmitted by KA9CFD: K1JT R EN40
Rational: A CQ with one call has already been sent, and response has been
received with both calls and a grid by the time TX3 is ready to be sent.
Yes, we could co it that way. But...
1. The message "K1JT R EN40" is not a standard JT-style structured
message. It will be transmitted as free text, but the MSK144/FT8
auto-sequencer will not process it correctly. To avoid other potential
problems, it insists on finding both calls in a valid auto-sequenced
message.
2. MSK144 QSOs often take place on a time-shared channel with pings from
several different stations being decoded in the same 15 s interval. As
many as several dozen FT8 transmissions are often decoded in a single
interval. When both callsigns appear in nearly every transmission it's
easy to keep track of what's going on, and who's working whom. With
just one callsign in a message this is much harder -- both for those
listening in and for the auto-sequencer.
-- Joe, K1JT
------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
