Recently upgraded to latest JT Alert. Crashes constantly. -Ribbon menu bar disappears and program must restarted. -Only gets one set of decodes then stops decoding -Unable to initiate help request

On startup (and after running JTDX) I receive the following, inviting me to choose between WSJT-X or JTDX. As I almost always use JTDX now how can I avoid seeing this message? The shortcut points to

Hi Mike The noise is gone this AM... It was isolated to exactly 2.5KHz BW and precisely at 50.313 to 50.3155 KHz FT8 slot only 73BobKo6Lu On 7/25/2021 6:40 AM, Michael Black

Hi Mike Noise is gone this AM... I didn't transmit... just turned on the radio and the noise was there... rebooted the computer and TS990 and still there. The curious part is that the

Hi George, Noise is gone this AM... I've been very active on 6m and never seen it before. It was only 2.5KHz wide... exactly in the 6m FT8 spectrum... very weird. Antenna is a vertical,

Hello Laurie, The Sound Play Limit was set at 'NO LIMIT', so that is not the cause. I'll continue to test various things and report back when I figure more out. I did try rebooting the Surface and

If have any AC adaptors like 24VAC for sprinkler or alarm systems those are great pickup sources from all the wiring involved (nice big antenna field on those systems). So you can choke those AC wires

On 6meters I have seen when running High Power RF gets into nearby motion activated lights, etc See instances where mix products pump some of these cheap wall warts become great RFI mixers as well If

Since it appears so strong (red bars), do you live near a hospital, clinic or any commercial establishment? Is it 24/7? If you turn your antenna, does is fade in/out? Is it just on 50.313 or up and

The callsigns list in the Main menu has been replaced by a free standing Calisigns window in JTAlert 2.50.x and later. Please click Help-> Open JT Alert 2.50 features Help File -> Callsigns Window

I cannot find any pertinent topics on this when searching the group and thought I'd ask. I upgraded this morning to 2.50.4 - I hadn't upgraded in quite some time - at least 6 months. I disabled virus

JTAlert does not use any of the WSJT-X internal logs. It doesn't read them and does not log to them. There are several reasons why JTAlert does not use the WSJT-X, but the most

You select what log to use -- but it should be the adi file. The others are not QSO logs at all. Strongly recommend you get one the logging programs though...will make your life much easier although

I never ends.... FT8 xmit stops at about 13 seconds...this is just continuous and the bandwidth is 2500 Hz... directly in 6m FT spectrum looking at my decodes, there are no particularly

Probably someone who does not have their TX audio source set correctly. Dave wo2x

Anyone else seeing this.. All other FT8 band segments are fine... and amazingly, I'm getting decodes thru this hash.... Bandwidth is limited to FT8 frequency of 50.313MHz Anyone

Laurie I only use the logger internal to WSJT-X, my apologies for not mentioning that in my earlier email. My WSJT-X log directory contains *3* log files:

Thank you, David. I found it under the callsigns menu in the Windows pop-up menu that opened after pressing the F2 key. 73... Bill

If WSJT-X is responding to JTAlert Callsign click events by setting the DXCall then JTAlert <-> WSJT-X UDP comms is working correctly. There is nothing else that can be done by

The rebuild operation accesses the log file used by your logger. The name and location of the log file will vary depending on your JTAlert settings for the enabled log. de