Hi Karl, due to the nature of MS QSOs I would recommend not having the "Settings->General->Disable Tx after sending 73" option checked. 73 Bill G4WJS.

#raspberryPi #BugReport

Hi Carlos, When the other stations sends "RR73" your QSO is finished. Your do not need to send anything back. Both of you can log the QSO. Only if they send "RRR" do you need to send a 73. 73 -- Larry

#raspberryPi #BugReport

Hi, I have a suggestion and a question. When I answer a CQ call in MSK144 the Auto Sequenz runs down. When I send R+07 I get back the RR73 from the other station, and my TX is disabled when receiving

#raspberryPi #BugReport

I'm seeing the same behavior here. I have the Call 1st box checked so when calling CQ and someone replies the standard messages DO update to the calling station's callsign. Until Gary reported this I

#BugReport

Hi I just installed WSJT-X v2.3.0 0c42df on my Windows 7 system. It seems that after pressing the erase button on the main screen WSJT-X has stopped displaying any Transmitted info, My call sign and g

#BugReport

Thanks for the swift reply Bill

#BugReport

Bill knows about this, its a regression that will be fixed in next release: https://wsjtx.groups.io/g/main/message/22948 Neil, KN3ILZ

#BugReport

Can confirm that this happens on FT8. I have not tested the other modes yet. Maybe something didn’t get set right, and it thinks that Tx4 is set to “RRR” instead of “RR73”? Mike K8WU

#BugReport

Hi Steve, thanks for the issue report. I noticed this regression just after the WSJT-X v2.4.0 RC2 release was published :( I am working on a fix for the next release. You can work around it by not re-

#BugReport

Noticed a small problem with V2.4.0 rc2, just want to check if anyone else has noticed the same or if its just my setup, when completing a contact I send RR73 and log the contact via the popup box, th

#BugReport

Modes FT8 and FT4 Distro Raspberry Pi 32 bit The standard messages displayed are from a previous QSO attempt. Clicking on a callsign does not generate standards messages for the callsign just clicked

#BugReport

Mode FT8 Distro Raspberry Pi 32 bit Completing qso with RR73 (TX4) auto seq then moves the radio button down to CQ (TX6). I rearm the enable TX button to call CQ again. The other station sends his 73

#BugReport

Is NOT going to sleep, fat fingrs Wyndell Resistance is NOT futile, it's Voltage divided by Current

#BugReport

I would suggest that you try shutting down WSJT-X **before** you put the computer to sleep.

#BugReport

Make sure your comm port is going to sleep oir it will cause issues with he programs attached to them that are running. 73 de Wyndell K5WJF

#BugReport

#BugReport: WSJTX only decodes alternate frames on wake up. At night, after working with WSJT-X (v2.30) and Grid Tracker with an IC-7300, I put my Windows 10 computer to sleep rather than shutting it

#BugReport

RC2 installation went fine on W10. Made a Q65-30A QSO OK on 6m using a TS-590SG. Switched configuration to the Icom 9700. Tried FT8 and it was OK. Tried Q65-30B on 144.170 and after one CQ it turned o

#BugReport

This reminded me of the time I started work. I was part of a team developing a fast multiply/divide unit for a mainframe computer. The divide algorithm was based an iteration that started with a looku

#BugReport

Glenn, the short engineer's answer must be that the various variants of WSJT-X (and similar programs) will give approximately the same answer when running on different hardware. Underneath, there is s

#BugReport

TU, Bill ! 73 Am 04.03.2021 um 17:38 schrieb Bill Somerville:

#BugReport