The QSOs are still kept in the WSJT-X logfile in ADIF format. You can load those QSOs via Inport into the HRD logbook.

It appears that the readback from JTAlertX from a remote HRD Log Server (latest version) is failing. The log is written successfully to the remote HRD Log server but the verification step is failing.

#HRD

I have the same issue with 2.12.1 — actually I like having 30 seconds of decode. Running Windows 10 64 bit on a dual core 2.7 GHz machine with 8Gb — lots of spare CPU and memory. Perhaps turning on th

Laurie: I upgraded to 2.12.3 and the clearing problem is still there. I tried various combinations of row and columns for the decode slots to no avail. Not a serious issue, in my view. I can send you

Laurie: Disabling the receipt of Text Messages fixes the clearing issue!

Using Windows Defender on Windows 10 64 bit without the April 2008 update (which causes driver issues).

Consider leaving callsign clearing for FT4 at 15 seconds. Seems to work fine as is. Maybe highlighting latest FT4 decodes in bold font? Great program!

TX will not occur if the station is in QSO (which is the behaviour one would expect). Great job Laurie on FT4 support!

Any word on this false positive? Really do not want to turn Windows Defender off ...

Thank you for the update.

I am having a configuration issue with WSJT-X v2.1.2, JTAlert 2.16.3.beta 002 and HRD 6.7.0.269 logging FT4. WSJT-X logs directly into HRD with no problem with the correct Mode (MFSK) and Submode (FT4

#HRD

It looks like a Mode mapping issue in JTAlert. Laurie, if you need a trace log, please let me know.

#HRD

Thank you Laurie for the info. RTFM, oh dear! Now need to figure why some fields such as Name are not being updated by HRD when logging QSO. Same problem as PC1Y.

#HRD

Your patience and expertise is noted and appreciated. At this point in time, we hams have the benefit of a great hobby with great tools. Be safe and healthy!

Good job Chuck. With other packages such Malwarebytes, you can configure white lists for files or entire directories. Check you anti-virus vendor’s documentation if you are still experiencing false po

On Wed, Apr 8, 2020 at 08:14 AM, John Peck wrote: On Wed, Apr 8, 2020 at 08:14 AM, John Peck wrote: On Wed, Apr 8, 2020 at 08:14 AM, John Peck wrote: On Wed, Apr 8, 2020 at 08:14 AM, John Peck wrote:

Crawl before you walk. Start by getting WSJT-X working. There is excellent docs produced for this package. WSJT-X produces an ADIF log. Master that system well. Next, get HRD logging from WSJT-X direc

#FT8 #HRD

I ran into the same problem after updating to the latest release of Windows 10 64 bit (2004). My generic cheapo external USB audio stick would not get recognized by Windows. I ordered a similar USB de

10 meters was wide open during FD with FT4 and CW signals coming in from all over the USA. JTAlert worked very well although some ADIF fields such as “Class“ did not propagate to HRD