There are many places to check to keep usb active you need to go into device manager and check usb ports but also the usb root hub section of this also and turn off power management hope this helps

#BugReport

Steve I was beginning to believe I had an isolated issue because none of my friends said they had it. Now I'm learning its not uncommon. I don't think I have RF in the shack. Mine acts ups regardless

#BugReport #FT8 #txaudio

I have also been struggling mightily with Mac OS Big Sur, USB interface III. and ICOM 7000. Worked perfectly (WSTJ-X FT-8 and WSPR) before upgrade to Big Sur. I also loaded the latest version of WSTJ-

#BugReport #mac #Cat_RigControl

Jim N7US sent me his configuration and that approach solved my problem: In WSJT-X, don't use CAT PTT, use RTS PTT via a COM port. In Microham Router, check PTT box for that COM port. Now, rig band/mod

#BugReport #Cat_RigControl

Hi Michael. thanks for the issue report, this is fixed for the next release and the default -a path will be honoured. 73 Bill G4WJS.

#BugReport

Bill, I don't have time to move the mouse, scroll it down, decide who to call and double-click on it in the couple of seconds we have. Especially with an essential tremor. Double-click is a problem if

#BugReport

I've checked it with v.2.3.0-rc3 and it has been solved! Thanks! Works perfect. Sorry for spamming :)

#BugReport #wsjt-x-crashing

I have the same issue with my Mac and KX3. Bill, this seems to be the same problem that I reported to you in email ~3 days ago! 73, Kevin VE7ZD

#mac #BugReport #FT8

V2.2.2 crashes when using band hopping for me. 73s Bill WA8VIH EL98

#BugReport

Ooops! I know this version won't make it until then, but just to let you know so that you can fix it for the GR... As I was going back through my settings to ensure everything was the same, I noticed

#BugReport

I just installed WSJT-X 2.3.0- rc3 and initial tests show that the problem I had with rc2 is still there in the new RC. When I am in MSK144 after the first TX Cycle I get a pulsing interference on 144

#BugReport #Cat_RigControl

Hi all, The reason of popping up th e"Log this QSO" dialog, is the incorrect reaction of WSJT-X when receiving unsolicided R-Reports, or receiving R-Report confirming "old" reports. It happens if a st

#BugReport #ContestMode

I made several RU contacts today with decode set to Fast and not one crash! Thanks John Gieringer KL7NW

#wsjt-x-crashing #BugReport

Hi, *This for you information only. It's temporary solved for me.* Yesterday I was fighting with other issues of the GUI, but after this was solved I had a new problem. When trying to transmit, either

#BugReport #linux

Have you checked the timeout timer of your radio? I assume it has one, as most newer ones do. Gary - AG0N

#BugReport

Tried using FST4W last night on 630m for the first time with WSJT-X Ver 2.3.0 rc2. With t/r duration greater then 300 sec program would terminate when the period started. I disabled the watchdog timer

#BugReport

Thanks Bill! I figured someone was on it! But, I work in I.T. myself and people always assume we know about all the problems so I figured it was worth reporting. 73 /randy

#BugReport

found that the Decode button was grayed out on that as well when configured for WSPR or FST4W. Normal, except when it is decoding. 73 Alan G4ZFQ

#BugReport

The thing is that there have been sequencing errors creeping in. Here's another where I should have been going to CQ but a 73 was sent.

#BugReport

Mattia, This is a common error message about the ADIF log file. Locate the ADIF log file and do this, Find the first line where it says: WSJT-X ADIF Export<eh> change it to: WSJT-X ADIF Export<eoh> Sa

#BugReport