Hi Mike,
comments in line below.
On 12/12/2018 16:09, Mike Maynard wrote:
I am starting to understand some...
It is tricky to explain without a full explanation of the finest details
of how messages are source encoded (packed) into the available payload bits.
I do not get though, why on a cq it cant be included (or at least
operator choice?). I do understand its not going to fit on a reply to
someone elses cq, but there are other places it could be put.
The place it will not fit is the message payload, it simply cannot be
sent. This is because the CQ which takes up the space of one basic
callsign and a complex callsign like your /M call use up almost all the
available payload bits, there are not enough remaining to encode a grid
square. What may be confusing is that both the word CQ and your /M call
are short but that is not relevant here since both are reduced to unique
numbers that have a fixed width. For example all standard callsigns are
encoded as a unique 28-bit number so A1A and GM4WJS both take exactly
28-bits of payload. A1A/M, K2GC/M, GM4WJS/PJ4, and YP4XMAS are all
complex callsigns that take more than 28-bits of payload space.
For a work around.... is there a 'Token' I can use to put in a field
that will pull the grid from settings? I have a script that runs
against the GPS to give me my current grid square and inject it into
WSJT. If there was a 'Token' (variable.... what ever you want to
call it) that I could insert into one of the message fields that says
"hey, put the current grid square here" I am sure I could make it work.
We don't currently support message "macro" insertion, I doubt it will be
added due to the 13 character restriction on free text messages which
would undoubtedly cause many support issues when truncated messages get
sent.
Thanks for listening to me complain....
No problem Mike, we do understand that there are both winners and losers
when changes like we have just made happen. We strive to have more
winners than losers and in this case you are not blocked from using
WSJT-X at all even though you may have to operate in a slightly
different way. You can still operate using the full callsign that you
are legally required to use and many others who were barred from using
WSJT-X by such a restriction can now use it.
Mike
K2GC (sometimes /M!!)
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
