WSJT-X, JTAlert, Log4OM v2

G4IUA

I’m setting up a new installation of SmartSDR 3.1.11  – WSJT-X – JTAlert – Log4OM v2.  All latest release versions.

 WSJT-X and JTAlert on their own work exactly as expected when selecting FlexRadio 6xxx as the radio in WSJT.  I have full control over the radio and WSJT reports frequency and I can select bands.  However I’ve now just set up Log4OM v2 and I’m having real issues.

 I’m unsure about the use of OmniRig (v2.1).  The Log4OM documentation insists on using OmniRig, and in an earlier setup I know I used to use it successfully although with the earlier version v1.  However I just cannot get things to work at all now, and as soon as I select OmniRig2 in WSJT the radio reacts erratically, spontaneously going into TX and I have intermittent control using the WSJT-X Test CAT button.  Then OmniRig reports ‘Rig Failure.  Rig is not responding’. Sometimes it shuts down WSJT and it requires a reboot to start it again.  Note that this is on a brand new ‘clean’ installation of W10.

 It seems when selecting FlexRadio 6xxx, WSJT has all the data and control it needs (frequency, PTT, ADIF) and communicates that to JTAlert and presumably should to Log4OM as well.  I don’t understand why OmniRig is involved at all but I see that others have managed so I’m even more baffled.   I’m definitely out of my comfort zone in this area and would appreciate advice from others using this configuration. 

 Jeff – G4IUA

Ross Slater

K0FLY

K0FLY

Jeff:  I interface WSJT-X to the FLEX using net server TCP protocol not Omnirig.  I use OmniRig to interface LOGOM to the FLEX.

Gayle

G4IUA

Ross Slater

G4IUA

G4IUA

K0FLY

G4IUA

Good idea Gayle.  When I'm happy with a setup I take pictures of each relevant page or I screen-save them. It's all too easy for things to go wrong, inadvertently make changes, Windows 10 updates screwing up things, etc. 

Actually I do have a slight problem now (after things WERE working!).  Logging correctly, Log4OM is now showing frequency, etc. but JTAlert stopped displaying.  Interesting as the title bar shows the mode, band, identifies Log4OMv2 but - sadly - no callsigns.  I've been thru the Log4OM setup time and time again but no success so I've posted the issue in the Log4OM forum.  It's one of those things: with so many apps sharing comms between them it's difficult for a novice to work out where the problem lies.  Any immediate ideas?

G4IUA