Hello,

I've been chasing my tail on this for far too long! Searching this forum hasn't yielded an applicable answer.
Here's the situation:

1. For various reasons, when using FT8, I like the flexibility of choosing between two radios. I have WSJT-X configured for Radio A and Radio B, with all the config and log files in separate directories in: C:\Users\...AppData\Local\WSJT-X - Radio A, and ...\WSJT-X - Radio B.

2. I created a hard link between the two wsjt_log.adi files located in the two directories as illustrated above. This link is functioning perfectly. Regardless of which Radio / WSJT-X combo I'm using, the current QSO is logged to both wsjt_log.adi files. Without fail.

3. Here's the rub. When I point LOGic to the Radio A .adi file, the QSO is logged ONLY when using the Radio A combo. When I point LOGic to the Radio B .adi file, the QSO is logged ONLY when using the Radio B combo. If I point LOGic to BOTH .adi files, this creates duplicate QSOs in LOGic! Grrr!!

To make it more interesting, up until about 6 months ago, I used JTDX for all FT8 QSOs with the same setup using two radios. (On the rare occasions using WSJT-X, I manually imported the ADIF files into LOGic.) I created a hard link between THOSE two .adi files and pointed LOGic to only one of them. For about three years that setup worked perfectly.

It was only after I got tired of the lack of JTDX development that I switched exclusively to WSJT-X for the new digital modes. That's when the current fun began!

Anyone have suggestions?

TIA,

Jim - WS6X

Tnx, Dennis,
The two ADIF files are identical. Because of the hard link, either Radio / WSJT-X combo, posts to the ADIF file in BOTH directories. That is why LOGic imports duplicate QSOs if I point to both ADIF files.
Since this hard link function was working before, I'm going to try another approach. I'm going to remove the hard link, and start over from scratch, creating a new hard link and eventually copying the full log back into the hard linked target ADIF file.
(The reason I have to have identical ADIF files in two WSJT-X directories -- one for each radio -- is to ensure that JT Alert reports the "worked B4" status correctly for every decoded callsign.)
Thanks again,
Jim

Hi Brad,

Thanks for your input. Yes, you understand my setup correctly - except for one detail. When I only point LOGic to one of the WSJT-X adi files, only the radio / WSJT-X combo that posted the QSO ends up in the LOGic log. The QSOs posted by the OTHER radio / WSJT-X combo do NOT end up in the LOGic log, even though the two .adi files are hard linked. The "head scratcher" is that I had this setup working fine several months ago.

BUT... this has become a moot point. Over the weekend I solved the problem with another approach.

Since I ALWAYS have JT-Alert running when I use WSJT-X, I decided to use the JT-Alert feature that creates its own ADIF log file. I simply point LOGic to that file, and now all WSJT-X QSOs, regardless of the Radio / WSJT-X combo, are automatically logged in LOGic. This is a sweet setup!

So, in reality, I now have three ADIF files updated with every WSJT-X QSO I make. One from each radio, plus the JT-Alert file. Plus the auto-feed to LOGic.

The only downside? My 80-year old memory has to "remember" to boot JT-Alert every time before I attempt a QSO in WSJT-X!

Thanks again!

Jim - WS6X