Laurie, FYI, a .record file exists in the .../session/JTAlert directory as opposed to the JTAlertX directory; however, that must be for an older JT-Alert version. Is the .record file created the

When running JTALERT with JTDX (rc151) I'm unable to click a station on the JTALERT decode box and bring it down to the Receive window. The only one's that respond are those calling CQ. No others

same issue here.. you can try 'livetcpudpwatch-x64.zip' from nir soft. www.nirsoft.net in my case it shows wsjtx sourcing udp packets on local port 65083 to remote port 2237 and JTAlert receiving on

Hi Laurie, FYI, I saw a highlight today that I found to be curious. Never saw the first call highlighted before. Looks like ON5YT switched transmit cycles and some were still calling and both ended up

Laurie, I do have a valid subscription which will expire in 2021 (lookups in HRD do function properly). Below is the contents of the specified directory: I don't have the .record file. Also, the

Question: What procedure can be used to filter the Decodes History window by date or time frame? The specific filtering needed is to determine how many call signs from one particular DX country were

What was the fix? Was JTDX running with elevated privileges or was it a UDP port issue? de Laurie VK3AMA

What does "log into the xml service with my account" mean? If it means you can login to the QRZ web page that does not indicate a valid XML subscription. You can have an expired

Gary, Thanks for the response - I am able to successfully log into the xml service with my account credentials. There must be a setting in JT Alert or HRD that I don't have set properly. Bob K5HX

Hi Jim,. I understand that I can use the XML lookup, but when the band is open and I'm working stations quickly, especially on FT4 I don't have the time to look up and manually type in the grid. My

When I get a QSO without the grid, and I'm using JTalert, the JTalert xml lookup shows me the correct grid and I just type it into the WSJT logging window before clicking OK.

Laurie, All my QSOs made in WSJT-X pass through JTAlert and get logged into the DX Lab Suit's DXKeeper logger. After uploading a batch of QSOs to LOTW I have noticed that the CQ and ITU Zone numbers

Make sure your subscription to the XML service hasn't expired. This is not a free service. Gary - AC6EG

Laurie VK3AMA, I did your advise and it is working properly now.Thank you very much De DV3CEP 73 and MOre Power to you.

For some reason the QRZ XML lookup and subsequent transfer of data to HRD is not working. JT-Alert communication to Ham Radio Deluxe is fine as far as QSO logging; however no QRZ XML lookup fields

The error message shown by JTAlert indicates it never received a UDP message from JTDX. Likely causes are you have another application running that has taken exclusive control

What version of JTAlert did you upgrade from? If it was several versions old, you may have an incompatible decodes database. The schema shown on the Decodes Help->About window should be

I upgraded my JTDX to 2.1.0 rc 151 and JTAlert to 2.16.8 .Before the upgrade my Decode is working but when it updated to Decode 2.16.8 it does not work anymore.Can u give me some hint on what to do

That was it Laurie, Thanks 73 Charlie be safe G4EST www.g4est.me.uk

If the Sound Test works than Alert sounds will work, they both use the same code. Likely your Alerts don't have sound file paths set. Check your Wanted Alerts in the Settings.