Thank you, it was the decisive factor, now it works again. de Henrik OZ1EVM

#FT8

I had same problem above 17m band. Putting toroid core on the audio cables next to the PC audio inputs/outputs solved problem for me. Of course, my antenna is problem (Delta for 80 tuned with automati

#FT8

Thanks!

#FT8

Bob, The problem is due to 1.9.0-rc2 and its popup Release Candidate Warning window. Until the next WSJT-X release (which alters the Window title naming that causes incorrect JTAlert docking) you will

#FT8 #HRD

Thanks very much Laurie!

#FT8

How long is "after a while", is it more than one or two RX periods? By design, JTAlert will not alert on new decodes immediately after a Band Change as the decodes could be for the old band or the new

#FT8

Yes. See the JTAlert Help file "Tutorial" topic regarding setting up JTAlert for the Chase and the need for, at a minimum, Monthly Scan Log operations. de Laurie VK3AMA

#FT8

Thanks Michael for the help. The information you provided got me headed in the right direction. I renamed the config.sqlite file. The WSJT-X - JTAlertx program still hung. Would not even create a fres

#FT8

hi Laurie, thanks for the explanations. Yes, you're right, found SSB QSO from last year (btw call is KG6JOI, not JUI :-) ) 73s, DK8ZZ 2018-02-08 11:42 GMT+01:00 HamApps Support (VK3AMA) <vk3ama.ham.ap

#FT8

Well that's a pretty safe assumption at any time. Bob - wd6dod

#FT8

C'mon guys, it only takes a minute. Make the Q and move on. Maybe the other guy needs YOU! Besides, this isn't even a contest, and it lasts all month / year. Kick back and enjoy!

#FT8

Ken, Open the Decodes History Window. It displays the current and old decodes along with the alerts they generated. It includes the majority oh the Callsign tooltip of the main JTAlert window. You wil

#FT8

My response went to support@hamapps.groups.io and you saw it because it went to the list. I just pointed out something that would help out a fellow ham. I did not claim to be any type of support. 73,

#FT8

Laurie, I usually use the WSJT-X logger for short term contacts then upload to LotW. From there I download my full LotW report and reupload this to the WSJT-X/JTAlert every few weeks. So I was able to

#FT8

What exactly is an "ignored call sign"? If you don’t want someone alerting you. As an example someone you know does not QSL, you can ignore them. What exactly is a "directed call sign" ? Someone calli

#FT8

Bob, Sorry, a vertical layout for the JTAlert window is not an option and wont be implemented within the current JTAlert V2 code. The still under development JTAlert V3 (still months away from release

#FT8

To be sure, Mike, JTAlertX is not the problem. JTAlert macros work just as well with FT8 as they did with JT65 and JT9. Thank-you for finally acknowledging that there is a problem with WSJT-X. By post

#FT8

Session log is on the way. It was really weird. I have never seen that before. B4 has always shown up before transmitting but this time, it did not appear until I answered his CQ. Did not wait until a

#FT8

OM, Visit the Logging section of the JTAlert Settings. Look under Logging Options group, the last checkbox, "Log seconds in time_on and time_off values" needs to be enabled. de Laurie VK3AMA

#FT8

Got this from Tom: Settings -> Manage Settings -> Logging and make sure “Log full name returned from XML lookups” is ticked Tom That fixed it. Just didnt have some settings correct. Bob

#FT8 #HRD