Hello all. I have discovered another issue with version 2.0. I do not know if it existed in previous versions.
I use the feature called "Enable logged contact ADIF broadcast", with port 2333, to send contact information to my logging program (not N1MM). This works very well, but I recently tried enabling the NA VHF Contest format and found that the ADIF send does not work. Disabling contest mode allows ADIF send to work again. So, it looks like either nothing is sent when contest mode is enabled, or maybe it is sent to a different port. I did check, and no message of any kind is received by the logging program, so it is not just a case of a different format. Thanks for any help. 73, Russ K2TXB > -----Original Message----- > From: Joe Taylor <[email protected]> > Sent: Saturday, December 15, 2018 1:31 PM > To: WSJT software development <[email protected]> > Subject: Re: [wsjt-devel] Version 2.0 issues with JT65 > > Russ -- > > You're calling some displays "bogus decodes", and evidently they are > bogus. But you appear to have all the knobs turned up to maximum > aggressiveness. Most if the displayed messages are flagged with "?", > which you may interpret as "caveat emptor", or some such. > > Probably you saved "KF4FCO EM70" in your callsign database. How many > other calls are there? > > The message "CQ KF4FCO EM70 OO" is clearly nonsense, so you could > reject it out of hand. > > When we've had time to pay careful attention to some of these anomalies, > and especially when more people are using WSJT-X for their EME > operations, we'll clean up some of these peculiarities. In the > meantime, you'll need to use some common sense if you want to use very > aggressive decoding settings. > > -- Joe, K1JT > > On 12/15/2018 13:04, Russ wrote: > > Bill, Joe, Charlie, whoever is interested; here is a new wrinkle to the > > problem. > > > > I was operating MSK144 on 2 meters. Got done and decided to switch to > JT65 > > to see if the false decodes would start to happen. It didn't right away, so > > went away for a while leaving it running. When I got back I had two > decodes > > showing in the average box: " CQ KF4FCO EM70". This was the last good > > decode that I got on MSK144 ! I DID click to Clear Averages before this > > happened. Here is all.txt. You can see the four good decodes and my CQ > > around 1530, and then two bogus decodes of the same call, at 1743, some > time > > after I had switched to JT65. While I was typing this a local started up > > calling CQ on the frequency I am on. And now there are six instances of the > > same decode showing on the JT65 screen. > > > > 1523 -30 2.0 1327 ## CQ KF4FCO EM70 OO O d20 > > 1527 -30 6.1 1550 # CQ KF4FCO EM70 ? d20 > > 1539 -30 4.7 1598 # CQ KF4FCO EM70 ? d20 > > 1544 -30 6.2 1436 # CQ KF4FCO EM70 ? d20 > > 181215_154645 Transmitting 144.15 MHz MSK144: CQ K2TXB FN20 > > > > 1743 -30 6.2 1368 # CQ KF4FCO EM70 ? d20 > > 1748 -30 6.0 1595 # CQ KF4FCO EM70 ? d20 > > > > And Joe suggested checking the average window. For the period in question > > it had only one entry: > > > > . 1727 -1.2 -1.09 1399 * > > > > That is 16 minutes before the first bogus decode and does not appear to be > > related. > > > > 73, Russ K2TXB > > > > > > > > _______________________________________________ > > 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 _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
