WSJT-X frequency not tracking SmartSDR

Al Peterson

This used to work before upgrading and I must have missed a setting somewhere. I recently upgraded to Log4OM2 (v: 2.4.0.0), WSJT-X (v: 2.1.2), JTAlert (v: 2.15.11) and SmartSDR (v: 3.1.8). I operate FT8 exclusively and everything is working with the exception of the frequency being updated in WSJT-X. The correct frequency is in the log. I can change bands from WSJT-X and SmartSDR follows properly. If there is a DX operation on a non-standard frequency, I used to be able to change the frequency in SmartSDR and everything would follow. 
I'm using SmartCat for the command / control interface and DAX for the audio. 

w5ap

I also can't get JTAlert v2.15.11 to log automatically to Log4OM. Can someone tell me how to setup the UDP ports?  

Al Peterson

I found the solution to my problem buried in the Log4OM2 configuration. Change the settings from "hamlib" to "Omnirig" and add a 2nd CAT interface (serial) 

Al Peterson

Open the JTAlert settings, find Logging / Log4OM
ADIF msg: 2236      Control: 2241

Go to Log4OM settings, Software Integration / Connections
Add a UDP Inbound ADIF message on port 2236

Dave Garber

Patrick

Patrick

Exactly!!

Patrick

I use Profiles primarily to change bands, frequency, modes.  I have had no problems with this.   I found that the PC is the most likely culprit in these issues.  And more precisely the Registry files in particular.  My computer acted inconsistently until I started making sure that the registry ran cleanly.  Getting rid of old registry files helps keep the apps happy and consistent.  I use “CleanMy PC” to do various PC maintaining functions.