Hi Boris, You may also disable AP and will get less that kind of false decodes of type a2. Unfortunately due that you will miss also some real decodes due that. 73, Reino OH3mA PS. I would prefer more

#BugReport

Hi Bill, I understood you. In previous versions, I used the normal decoding level. In this version, it is deep: There was false decoding again today: Returned to normal decoding level. In this case, t

#BugReport

Hi Boris, as has been said before, if you are not getting occasional false decodes then the decoder is not working at the optimal sensitivity. Another way of looking at this is, if the decoder sensiti

#BugReport

Sorry .. forgot the screenshot to enclose... Hi everybody, A problem with WSJTX 2.4.0-rc4 on my raspi with raspibian buster. I start wsjtx via autostart entry: @wsjtx the last entry in the autostart f

#BugReport #linux

FWIW ... it happens. You can recognize this by 1. The report of -24 ... or lower 2. The reply being in a contest format 3. The question mark and A Priori tag at the end. Not unusual. Neil, KN3ILZ

#BugReport

Hi everybody, A problem with WSJTX 2.4.0-rc4 on my raspi with raspibian buster. I start wsjtx via autostart entry: @wsjtx the last entry in the autostart file Since-rc4 I have the following issue: whe

#BugReport #linux

GD! False decoding occurred in WSJT-X v.2.4.0-rc4: 210328_212230 3.573 Rx FT8 -24 1.5 500 UX8IW Z92UND/R R BL83 ? a2 73 Boris UX8IW -- Борис Романов -- Борис Романов

#BugReport

Thanks. I had Auto Clear Avg turned on but Enable averaging was not on.

#BugReport

Turn on Autoclear Avg after decode and that will work around the problem for now. Make sure Enable Average is on. 73, N0AN Hasan

#BugReport

I'll attach a screen shot below. K7MAC called me and decoded twice on the same sequence on the same frequency about 4 seconds apart (EME delay is not turned on). You can see in the TX window that appa

#BugReport

Hi Cliff, so I can see what is happening put the attached file into the WSJT-X configuration files directory (on MS Windows that is te same directory as the log files directory - "Menu->File->Open log

#BugReport

WSJTx v2.3.1 Error(s) OnSplit=Rig Stops transmiting with this error: Rig Control Error Do you want to reconfigure the radio interface? Details: Hamlib error: Target VFO unaccessible rig.c(4187):rig_se

#BugReport

Hi to all, Thanks für the new two program versions. On 2.4.0-rc4 I found out that in MSK144 the call is not copied to the standard messages wehen doubleclick on a CQ call. You have to double click the

#linux #BugReport #MSK144

Thank you so much for your comments Bill. I´ll try in upcoming releases, hopefully the bug will get fixed. Please notice that in former versions this issue didn´t show. Maybe I´m sort of of a purist,

#BugReport

Hi Hector, sorry you are having issues, it is due to some recent changes that seem to be revealing a problem with some CAT commands on the FTdx3000. There will be a new release soon that should improv

#BugReport

Hello group, My apologies if I didn´t add the proper tag. Name here is Hector and call LU4AHR, QRV in Buenos Aires (GF05sk). I´m currently using v2.4.0-rc3 but since v2.3.0 (and all versions in betwee

#BugReport

RFI will cause that in my shack as well. Everything was fine for quite a while then I must have moved some cables because xmit on 10 meters would cause it to drop out. I redressed some cables and the

#FT8 #BugReport

Hi Marv I am running a TS590s as well and I have seen that behaviour as well. It is not new and I saw it in earlier editions as well. It is not always there, but when it comes up, it is very annoying.

#BugReport

Thanks, will give it a shot.

#FT8 #BugReport

Looks & sounds like an RFI issue. Single band WSJT-X issues are almost always a sign of RFI. Install ferrites on all of your interconnecting coax's, your lines to & from the MFJ, the KB & mouse, monit

#FT8 #BugReport