Actually I never checked Log4OM but Log4OM2 does look like you can select the contest ID and it may well parse it. I just didn't think to even check for that. Mike

#FT8

Laurie I did try to get prefix alerts of only Africa using the filter provided by JTAlert. Sound alerts are heard. No alert is seen .Other continent filters work OK.. Please repair this problem. I nee

#FT8

I get the same message if DXKeeper does not upload the QSO to Club Log. I get a message from DXKeeper that the upload failed. Have to click OK on that message. Do you have Club Log upload selected in

#FT8

JT Alert V 2.16.7 keeps shutting down when I start the program. sometimes after 3-4 times, it will stay active.... Then in about 10 min, it freezes up. Only way to get out of program is to use task ma

#FT8

Thank you Laurie I have found that it is easier to locate the WAE entities which are mostly small islands by searching for their GRID/LOCATORS. Amos 4X4MF

#FT8

The missing decode coloring is due to a defect in WSJT-X 2.2.0, it is triggered by a "+" symbol in the decode message. This was reported 5 days ago to this group in this message https://hamapps.groups

#FT8

Hi Laurie, thanks for the reply. I understand and I'll be waiting for next release. A question: Can I delete any previous choice (I mean: DXCC, WAS States, Zones ....) and restart with a clean alert c

#FT8

Thank You! I had been searching for this for a couple weeks. Even my Elmer wasn’t able to find how he showed the signal strength on his computer to help me. Thanks again Bruce Beatty NØBHB

#FT8

Gert, Your in the database as "MN" because there is an override for your callsign in the code, overriding the FCC reported State. Your Callsign and several other US hams have overrides being applied.

#FT8

perhaps you could include version numbers of all three, to confirm you are current. make sure wsjt is sending udp on 2237, and the 3 boxes are checked do you get an error when it does not log??? you s

#FT8 #HRD

JTAlert records all HRDLogbook logging activity in a text file. See %localappdata%\HamApps\<your_callsign>\session\JTAlertX\HRDLogbook.trace de Laurie VK3AMA

#HRD #FT8

Sam ... go to the ARRL-LoTW@... group ... the new version of TQSL has tightened up on 'errors' that used to be ok in upload files. they can explain it to you there.

#FT8

I think this has resolved itself - possibly a qrz issue. Will test further.

#FT8 #JTDX

I've been using Hamspots for a few years with no issues but have not been doing any radio work for over a year. Prior to my shutdown, Hamspots reliably reported both calls I'd spotted as well as my ca

#FT8

yes I do Laurie,

#FT8

You could be right. Was not sure which program initiated it. I only get over to my dad's 1 or 2 times a week. So when I get there I will get the picture and post it. Bob W8RID

#FT8

Check that you have JTDX setup correctly, specifically the UDP Server section on the Reporting tab of the JTDX settings. Make sure that you are not running JTDX with elevated privileges (set to run as

#FT8

Hi - Yes, I have it running. Look at the JT Alert help file - the process should still be valid. Note that there are multiple steps that include configuring the Log4OM Communicator instead of the main

#FT8

Hi Laurie! Thank you for your reply! Disabled antivirus protection (ESET Internet Security 12.2.30.0), Reinstalled version 2.15. After rebooting, a window popped up at startup saying that some UDP con

#FT8

Don, It is the Card checkbox that is allowing the Scan to locate LoTW confirmed QSOs in the lotwreport.adi file. The problem with the Lotw file is that while it contains a list of Lotw confirmed QSOs,

#FT8