OK. Understand. JTDX maintains its own LOG, but passes info to Logger32. JTDX colors derived from JTDX log. So I have a some more contacts in the Logger32 log than in the JTDX log... I think from some

#jtdx #log

Very pleased with JTDX and Logger32 for the month or so I've been using them; and with the help I've received from Dave, mm0hvu, and Arvo, es1ja. I still have one problem which, I think, may be an iss

#jtdx #log

As these questions may be about the interface between Logger32 and JTDX, I'm taking the liberty of posting in both reflectors. I have tried to look at the various manuals, guides, and reflectors, but

Eh? Roswell/NM? I get the following from my QRZ page... ------------------------------------------ ----------------------------------------------------- Bob, w3idt But played tourist in NM a few weeks

Jim, K2QB, Dave, N8DC, Like magic, the problem has gone away :-) ------------------------------------------------------------ What was happening was... 1. LOGGER32 would NOT connect to the FT5000 when

My issue with FT5000 / LOGGER32 / JTDX is mostly SOLVED. Contrary to the table I added to my "help" note, the "Handshaking" option in JTDX WAS SET to "DEFAULT". It needs to be set to NONE, as in the t

Jim, K2QB and John, N7TK, 1. Thanks for your offers to help. Two questions at the moment... re a. item 3: PORT OPEN/CLOSE, and b. JTDX configuration, item 5. 2. I'm making progress: Below the signatur

Thanks Rob, Got it working: Problem was that I didn't use "Open Com Port" :-( (and the new FT5000 settings still work with N1MM+) Now, on to finding out how to use FT8 / Logger32 Can't find much in hu

Rob, Found your old post... Am trying to set up my FT5000 with LOGGER32. New user of LOGGER32, or trying to be. Mostly for general - non-contest - use with FT8. FT5000 works fine with N1MM+ for contes