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.
Bob AF9W
JTAlert logging fails if fldigi not running
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: JTAlert logging fails if fldigi not running
Hello Bob,
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.
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.
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
Re: JTAlert logging fails if fldigi not running
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
Bob AF9W
- G4POP
- Log4OM Alpha Team
- Posts: 10829
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: JTAlert logging fails if fldigi not running
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
73 Terry G4POP