On 12/12/2018 20:34, Patrick 9A5CW wrote:
i suposed that only <speciall calls> shud be in the <...> but i see
when i checked my all.txt
that normaly also the callers are marked the same... is that normal
behaviour?
Part of the decodes on 30m today:
*134145 1 0.1 1135 ~ CR140AA <F1MWV> 73*
*150530 7 0.1 1699 ~ DM152ZYA <F1MWV> 73*
*152115 -10 0.2 1774 ~ OG55W <F1MWV> 73*
*081830 5 0.6 441 ~ YO/KD6SM <F6ECI> RR73
*
*090015 10 0.2 1822 ~ TC630MECCA <F6EQZ> 73
*
** 085830 -16 0.4 531 ~ *<PG3N>* TC630MECCA RR73
Didnt find any match with SP5ORS calling any special long call station
this afternoon. He was active CQing and mostly
working EUs but none of them its <SX...> or so.
Hi Patrik,
when a complex callsign is used in a message either it or the standard
one can be sent as a hash code, one of them must be. The message
generation is arranged so that each call is sent not hashed at least
once in a standard QSO. There is a further restriction that signal
reports can only be included in a message with a complex call if the
complex call is sent as a hash code.
All the examples you give above are sending 73 or RR73 rather than a
report or r-report so the message generator has chosen to hash the
simple callsign and send the complex callsign in full. The same applies
for RRR messages. CQ and QRZ messages never hash the callsign as that
would nearly always be ambiguous.
The intention is to always exchange the call in full as hash collision
can and will happen so we want to ensure that the correct callsign is
always copied at least once per QSO.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
