On 02/08/2017 14:16, Dan Malcolm wrote:
I have not seen this before. I am running WSJT-X 1.7.1-devel r7972.
I had a FT8 QSO with NP3DM. Just off my frequency was another QSO
going on with K5GA and VE3FON. No problem as the decoder seemed to
handle both QSO’s separately. When logging time came however, VE3FON
was logged to Log4OM no NP3DM. See attached screen captures. The
logging chain starts with WSJT-X and WSJT-X is only offering VE3FON.
The last line of wsjtx.log is this line:
*“2017-08-02,12:50:00,2017-08-02,12:52:15,VE2FON,,14.075312,FT8,-01,-19,20,FT8
Sent: -01 Rcvd: -19,”*
Hi Dan,
this is a slightly tricky situation to deal with. We accept any message
with the word 73 as a sign off that triggers logging but in this case it
also picked up the callsign even though the message was not for you.
This behaviour is only when the decode is +/- 10Hz of your frequency and
it just crept in. Looks like we will have to detect that it is a
standard 73 message but not for you, that will stop it sending 73 to a
station that you didn't work as well.
We make hard work for ourselves by having such a good decoder that can
disentangle signals on top of each other.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
