On 26/12/2019 17:40, DX Jami via wsjt-devel wrote:
My point is WSJT-X should allow "non-standard" call signs.
Danny,
WSJT-X goes to a lot of trouble to support "non-standard" callsigns, but
there is no free lunch. The non-standard callsigns supported by WSJT-X
in MSK144, FT4, and FT8 modes are greatly expanded from prior protocols
but it takes just 28 bits of the message payload to encode a WSJT-X
standard callsign and a much larger 58 bits to add non-standard
callsigns up to 11 characters long. To provide what you demand, which is
basically a request to make more callsigns "standard", would potentially
take two times 58 bits, plus another 15 bits for locators or reports,
plus 1 for 'R' acknowledgement messages, plus another three to allow
free text messages and contest formats etc. That's a total of 135 bits
which is nearly twice the size of payload as currently used. That would
require more bandwidth, a faster symbol rate, a longer transmission
time, or some combination of all three, to obtain similar sensitivity.
That is a high price to pay for a small percentage of the total QSO
messages used on the bands.
Non-standard call users, and note you are only one by choice, can
operate these modes with the limitation that sending a grid square is
not simple, and you cannot work another station with a "non-standard"
callsign as easily as one without.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
