Because if you're operating 'split', which is the suggested way to operate, WSJT-X knows that you're not causing QRM and as such will not turn it off. Its up to the operator in this case

Hi Martin. It think that once you check it, if you uncheck it, it seems to not change the behavior. Like you, there are times when I want to choose who to answer and get messed up by the call 1st

My apologies. I did not intend to hijack, but expand upon it. There is a reaction to sending the RR73, which is popping up the log page as well as dropping the Enable TX. Both reactions are an issue,

Nice! Hijack my post and then answer the hijacker's question. Poor form gentlemen! <sigh>

Nope. Although that setting is there, it makes no difference whether it is checked or unchecked. The Enable TX drops as soon as I send RR73. I believe that was a change to meet some regulatory

I don't think that feature works correctly, as I've seen it discussed as a bug to be fixed in next release. (Checked or not, it disables tx after 73) 73, N0AN Hasan

Hi Mike, In settings under general/behavior there is a checkbox "Disable TX after sending 73". Leave that unchecked and I believe your TX enable button will not be disabled after you send the

To piggy back on that, shouldn't the same be true with killing the Enable TX button? Many times, in marginal contacts, I have sent RR73, the log window pops up, and the Enable TX button goes off,

I may be overthinking things, but shouldn't the logging pop-up window popup on the incoming "73" and not my outgoing "RR73?" Steve K6WW

The operative word in your sentence is "should!" As stated in my previous post, it just continues down the band. I just had an aha moment and decided to try something other than VOX. SUCCESS! I

Bill, Just a quick note in case you did not get my email to you. It has been 12 hours and no failed WSJT-X decodes with the following arrangement: WSJT-X UDP 2237 JTA 2237 (automatically found I

Steve, I had a similar issue with my ft897d. Turned out it was because I had a little RIT turned on after being on SSB for a while. Setting RIT back to 0 fixed it. Jim Bacher, WB8VSU wb8vsu@...

That may be what is intended, but I set the rig to 14.074 and then on each transmit, it jumps to 14.073, 14.072.5, 14.072, 14.0715, 14.0705, 14.0695, 14.069, 14.0685, etc. At this point, I'm so far

The automatic disable TX when you are on or close to the transmitting station is, in fact, a good thing. When running split mode, however, it is not necessary, nor even a good idea to inhibit

When in simplex mode and you call a station, WSJT-X will turn off "Enable Tx" if that station responds to another caller. That's a good feature. But this fails when operating in split mode as WJT-X

Steve, wsjt-x with CAT control shifts your transmitter frequency to keep the audio in a range that keeps your transmissions clean. After it is done transmitting your radio should return to the normal

Can you be more specific about what frequencies it goes to: changes from 14.074 to all kinds of extremes -- --w8lvn--

Markku, If you start Task Manager in Windows, you will see that Spot Collector, unfortunately, is a very heavy user of CPU power. It is, most likely, the cause of your problems. I am a devoted user

WOW, a very neat APP, works flawless! Ten digit grid and elevation too NEATO! Mack, w4ENN Sent from Mail for Windows 10

BTW, we discovered that the Windows 10 update turned off access to microphone within Privacy settings. Turned back on and voila. FYi. 73 from Seattle. Jonathan, KK7PW