Thanks for the feedback Bill !
I appreciate it.
73
Phil, F5FDV
Envoyé: dimanche 23 décembre 2018 à 19:04
De: "Bill Somerville" <[email protected]>
À: [email protected]
Objet: Re: [wsjt-devel] Bug when responding to K3ZK CQ
De: "Bill Somerville" <[email protected]>
À: [email protected]
Objet: Re: [wsjt-devel] Bug when responding to K3ZK CQ
On 23/12/2018 16:16, [email protected] wrote:
> Something strange happened when I tried reply to a K3ZK's CQ.
> As usual, I double clicked on the CQ messsage to set up the QSO
> information.
> In the "Gen msg" window the sequence <K3ZK> ZS1/F5FDV appeared as
> expected but, when I turned "Enable Tx" on, the sequence <NQ6C>
> ZS1/F5FDV appeared in the "Rx Frequency" window.
> I turned "Enable Tx" off and on again with the same result.
> So I gave up and after several QSOs with other OMs that went well, I
> responded again to another CQ of K3ZK. The same issue happened again.
Hi Phil,
this is a known issue with WSJT-X v2.0.0, it is related to the use of
hash codes to represent callsigns in messages when making QSOs with
stations with complex callsigns like yours. The phenomenon is due to a
hash code collision where two of more callsigns map to the same hash
code, in this case K3ZK and NQ6C. The correct message is being
transmitted but the print of it at your end is inserting the wring
callsign, one that was inserted into the hash table from some previous
message. You may have been able to proceeded with the QSO, taking care
to check that the correct callsign is logged.
A fix for this issue is being worked on for the next release. You do
have a workaround, by closing down WSJT-X and restarting you will clear
the hash table and messages should print correctly, at least until
another hash collision occurs.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> Something strange happened when I tried reply to a K3ZK's CQ.
> As usual, I double clicked on the CQ messsage to set up the QSO
> information.
> In the "Gen msg" window the sequence <K3ZK> ZS1/F5FDV appeared as
> expected but, when I turned "Enable Tx" on, the sequence <NQ6C>
> ZS1/F5FDV appeared in the "Rx Frequency" window.
> I turned "Enable Tx" off and on again with the same result.
> So I gave up and after several QSOs with other OMs that went well, I
> responded again to another CQ of K3ZK. The same issue happened again.
Hi Phil,
this is a known issue with WSJT-X v2.0.0, it is related to the use of
hash codes to represent callsigns in messages when making QSOs with
stations with complex callsigns like yours. The phenomenon is due to a
hash code collision where two of more callsigns map to the same hash
code, in this case K3ZK and NQ6C. The correct message is being
transmitted but the print of it at your end is inserting the wring
callsign, one that was inserted into the hash table from some previous
message. You may have been able to proceeded with the QSO, taking care
to check that the correct callsign is logged.
A fix for this issue is being worked on for the next release. You do
have a workaround, by closing down WSJT-X and restarting you will clear
the hash table and messages should print correctly, at least until
another hash collision occurs.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
