Try using FLRig and rigctld instead.
FLRig to your rigrigctld to FLRigLog4OM to rigctldWSJT-X to FLRigFLDigi to FLRig
I have all of these running at once.
de Mike W9MDB
On Tuesday, November 19, 2019, 11:43:38 AM CST, Zeev Stadler
<zeev.stad...@gmail.com> wrote:
Hello Doug,
Getting the log from WSJT-X to Log4OM is already taken care of.
The goal of having both WSJT-X and Log4OM connected to Omni-Rig is to have one
Log4OM profile for both SSB and Digi modes. Ideally, one should just turn-off
"Enable Tx" on WSJT-X to operate to SSB on the rig.
73Zeev4X5ZS.
On Tue, Nov 19, 2019 at 7:08 PM Doug Bates <kv4z...@gmail.com> wrote:
The Log4OM manual has specific instructions on getting WSJT-X logging functions
to use UDP to communicate with Log4OM. Omni-Rig is used as "radio" FOR WSJT-X
only. Freq. info is passed to Log4OM via UDP as well as the logging. Read the
Log4OM manual.
On Tue, Nov 19, 2019, 10:38 AM Zeev Stadler <zeev.stad...@gmail.com> wrote:
This is my first post here. I've tried the Yahoo group, but that did not help.
Hopefully the developers here can shed some light on the expected behavior.
Omni-Rig main feature is "multithreading: multiple programs, written by
different authors in different languages, can control the radio via Omni-Rig at
the same time". I therefore expected that WSJT-X would be able to run in
parallel with Log4OM when both programs use Omni-Rig. So far I failed to do so.
Can these programs work simultaneously with Omni-Rig?
Option 1: First WSJT-X completes its initialization and then Log4OM is
startedLog4OM would not connect with Omni-Rig. During the startup of Log2OM,
WSJT-X's rig-control indicator would turn orange or it will show a rig-control
error. These errors are easy fixed by a retry.
Option 2: First Log4OM completes its initialization and then WSJT-X is started
WSJT-X show a Rig Control Error "OmniRig: timeout waiting for update from rig"
Similar behavior is seen when trying to run SWJT-X simultaneously with
HolyLogger.
On the other hand, Log4OM and HolyLogger are happy to work simultaneously with
Omni-Rig. In addition, changes in the rig's frequency are reflected in both
loggers. This is true for changes made directly on the rig and when the
frequency is changed using Log4OM.
I'm using WSJT-X latest version (v.2.10.0) and Log4OM latest version (1.40.0.0)
on a Windows 10 Home PC. The behavior described above is when all programs are
run as administrator, as suggested in the Yahoo group.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
