ADIF Monitor

[wa4ban]

On my Windows 10 PC I have Log4OM set up to ADIF monitor my WSJTX log file. When I make FT8 contacts and later launch Log4OM, it picks up the FT8 contacts and displays them in the Recent QSO's list. I like this because it also shows my FT8 contacts as Worked Before.

Recently I set the apps up on a Windows 11 PRO laptop. Log4OM works great. WSJTX works great. But, Log4OM is not bringing in the FT8 contacts from the WSJTX log file on the laptop. I have the path to the file set correctly on the laptop installation.

Update: I copied the4 missing qso's from the WSJTX log file and pasted them into a new adi file and imported that into log4om. Then I made some FT8 contacts and log4om immediately pulled them in. Don't know why that fixed it, but it is working now.

[G4POP]

On my Windows 10 PC I have Log4OM set up to ADIF monitor my WSJTX log file. When I make FT8 contacts and later launch Log4OM, it picks up the FT8 contacts and displays them in the Recent QSO's list. I like this because it also shows my FT8 contacts as Worked Before.

Recently I set the apps up on a Windows 11 PRO laptop. Log4OM works great. WSJTX works great. But, Log4OM is not bringing in the FT8 contacts from the WSJTX log file on the laptop. I have the path to the file set correctly on the laptop installation.

Update: I copied the4 missing qso's from the WSJTX log file and pasted them into a new adi file and imported that into log4om. Then I made some FT8 contacts and log4om immediately pulled them in. Don't know why that fixed it, but it is working now.

Cant understand why your not using the prescribed UDP method of transfer and real time lookup, your way you dont know if you worked the station before until you log it in WSJT whereas with UDP you see the WB4 status as the call is entered.

However as always its the users choice!

[wa4ban]

I think my original reasoning was the ADIF method prevented having to have Log4OM running at the same time I was running WSJTX and GridTracker. I was thinking about memory and speed of the PC. I typically only used the Worked Before info when I was on a Phone contact.

However, after reading your comment, I switched to the UDP method and as you say it is very fast to log the QSO. And doesn't require the CAT to be connected to the radio, which is already connected to WSJTX.

When I operate phone or CW I am not using WSJTX and GridTracker, so, then I CAT from Log4OM and of course that has always been excellent.

Going forward I will be using the UDP method.

Thanks for your reply!

[G4POP]

Your next step is to use omnirig so that wsjt and log4om synchronise for CAT control -see user guide

Remember to select omnirig rig 1 or rig 2 in wsjt, not the actual radio!

[wa4ban]

I ordered a cable this morning to do just that!

[G4POP]

I ordered a cable this morning to do just that!

No cable required for UDP to link WSJT and Log4OM, unless your refering to a CAT connection via cable to enable CAT control but you must already be doing that with WSJT - Puzzled!

[wa4ban]

I ordered a cable to connect the "Remote" CI-V connector on the 7300 to the computer to enable Log4OM to also read the freq, mode, etc. of the radio. The current USB cable is used by WSJT-X. I got the idea for this from the Log4OM manual.