On 02/01/2017 17:57, Bill ND0B wrote:
I suspected something like this but am still looking into it / getting up to speed. This was why I specifically suggest this apply only to the CQ message as being the shortest, it might, take on something like this and did coach it with “if it will fit” This will be an excellent opportunity for me to learn the ins and outs of packing in this new protocol.
HI Bill,the CQ message does have an obvious set of permutations that are not used. Joe recently added the interpretations of E9AA thru E9ZZ as CQ AA thru CQ ZZ on the assumption that the E9 prefix will never be issued. I think this leaves E9AAA thru E9ZZZ still spare and available for interpretation, which is 26x26x26 permutations. The only thing I am not sure of is if that is still true if the caller has a type 2 or type 3 compound callsign.
From the above you should see that the CQ message is just a "<his-call> <my-call> <grid>" message with special meanings being applied to certain <his-call> and <grid> combinations. "<his-call> <my-call> <report>" messages use "<his-call> <my-call> <grid>" with spare space in the <grid> component encoding to signify reports etc.
I hope I am right here but I think I have the general principles correct. 73 Bill G4WJS.
------------------------------------------------------------------------------ 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
