I am elmering a new ham and helping him set up Log4OM with fldigi and WSJT-X. It appears that if Communicator is set up for both fldigi and JTAlert interfaces and fldigi is not running then the JTAlert logging fails. I can't test this at my home QTH as my HF station is off the air. I turned off the fldigi interface and restarted Log4OM, JTAlert, and WSJT-X and logging works fine.

JTalert can only handle WSJT-X, JTDX and two different HT65HF softwares. For each of them JTalert
uses another colour for the desktop shortcut symbol (4 different if you install it for all of the possible
JT mode softwares). JTalert can log to the Log4OM SQLite file only by using those 4 different softwares
but it can´t log Fldigi contacts to Log4OM.

Thanks, I understood that. The problem seems to be that if I configure Communicator for both Inbound and fldigi interface and fldigi is not running it will not allow JTAlert to run. Does this seem correct?

Thanks, I understood that. The problem seems to be that if I configure Communicator for both Inbound and fldigi interface and fldigi is not running it will not allow JTAlert to run. Does this seem correct?

Bob AF9W

Are you sure that you have not changed the FLDigi port number in Log4OM communicator/Settings/inbound/FLDigi interface it should be 7362

Because I have the FLDigi interface set up and JTAlert/WSJT-x works fine