Hi Dave,

Thanks for the response.

If a call sign is specified in Settings which is not compliant with the
requirements of the 28-bit encoding scheme, my recollection is that with
WSPR the non-compliant callsign will code into some kind of nonsense in the
*digital* message. In any case, a non-compliant callsign will never encode
properly.

I don't clearly recall whether the non-compliant callsign does or does not
transmit properly on CW, but my recollection is that the non-compliant
callsign *did not* transmit properly on CW.

The ideal solution that would work across the various modes that WSJT-X
supports would be to permit an optional *CW ID* callsign that can be
anything reasonable -- e.g., an arbitrary string of up to 16 characters,
where any letter, digit, and the fraction-bar character would be permitted.
When a station has been legally assigned a non-compliant callsign the
operator could choose something reasonable and compliant for the callsign
to be encoded, and then the operator could separately specify the actual
assigned callsign for the CW ID.

For example, Denmark has issued a special callsign series 5P0WARD/x, where
apparently the x is a one- or two-digit suffix. An actual station spotted
is 5P0WARD/7. "5P0WARD" can't be encoded in the 28-bit encoding scheme used
by WSPR (not as a standard Type 1 message, but also not as the Type 2 or
Type 3 variants).

So in this situation the operator might choose to use a "Type 2" message --
e.g., "5P0WAR/7" --  or even a "Type 1" message -- e.g., "Q07WAR" (as the
ITU regulations don't use a Q callsign for any country), but then in CW
transmit the actual assigned legal callsign of "5P0WARD/7".

It seems to me that callsigns that don't comply with the WSJT-X model are
becoming more common, so it would be nice if any station -- regardless of
the particular station ID requirements of the competent jurisdiction -- can
always legally ID the station in Morse CW.

David / K7DB
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to