On 18/12/2018 06:12, JF2DKK wrote:
Exact sequence of steps required to reproduce the problem
1 receive JA4DBY callsign
2 receive CQ 8N0400N
3 Tx2 Transmitting <8N0400N> JF2DKK +19
4 Tx3 receive JF2DKK <8N0400N> R-20
5 Tx4 8N0400N <JA4DBY> RR73 <<< At this time the call sign is replaced.
Hi OM,
this is a known issue, be assured the correct information was sent on
air, the defect is that the printing of your received message (5) above
is wrong. It is because the hash code of the call JA4DBY is the same as
that of your call JA2DKK and WSJT-X has stored the hash code from a
previous message that contained the call JA4DBY (it could have been some
time before). This defect will be fixed for the next release.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
