Hi Zeev,
ok, thanks for checking that. The next step is to get a diagnostic log
from OmniRig. To turn on debug logging in OmniRig you must modify the file:
"%AppData%\Afreet\Products\OmniRig\OmniRig.ini"
Add the following to the top of that file:
[Debug]
Log=1
that will cause the OmniRig
Hi Zeev,
I still suspect one of relevant processes is running with elevated
rights. You can check directly using Windows Task Manager. Start Task
Manager, switch to the "Details" tab, right-click any column heading and
press the "Select columns" button, in the window that pops up check the
Bill,
Yes, I've tried the non-administrative runs too. In fact, none of the
possible combinations enabled both programs to communicate with Omni-Rig.
73
Zeev
4X5ZS
On Wed, Nov 20, 2019 at 8:01 PM Bill Somerville
wrote:
> On 20/11/2019 17:52, Zeev Stadler wrote:
> > Hello Bill,
> >
> > Below
On 20/11/2019 17:52, Zeev Stadler wrote:
Hello Bill,
Below I have described to scenarios.
In "Option 1" WSJT-X has an intermittent communication problem with
Omni-Rig, but Log4OM is unable to communicate with the rig.
In "Option 2" WSJT-X produced en error: "OmniRig: timeout waiting for
Hello Bill,
Below I have described to scenarios.
In "Option 1" WSJT-X has an intermittent communication problem with
Omni-Rig, but Log4OM is unable to communicate with the rig.
In "Option 2" WSJT-X produced en error: "OmniRig: timeout waiting for
update from rig", and WSJT-X is unable to
On 20/11/2019 17:19, Zeev Stadler wrote:
I would appreciate a word from the developers - should we expect to
have WSJT-X in parallel with other programs that use Omni-Rig?
Hi Zeev,
you have not told us exactly does not work yet. If you get an error
message from WSJT-X, what does it say
I would appreciate a word from the developers - should we expect to have
WSJT-X in parallel with other programs that use Omni-Rig?
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Zeev,
Sorry if I misled you or anyone else. I run Log4OM, N1MM+, and WSJT-X all
at the same time. Perhaps it is N1MM+ that is passing the freq. info to
Log4OM. Running all 3 works for me. I will be quiet now. KV4ZY QRT.
Doug Bates KV4ZY
Sent from my Verizon mobile phone.
On Tue, Nov 19, 2019,
On Tue, Nov 19, 2019 at 7:08 PM Doug Bates wrote:
> Freq. info is passed to Log4OM via UDP as well as the logging. Read the
> Log4OM manual.
>
Hi Doug,
I followed the manual, but I do not see the frequency information in Log4OM.
The settings in both WSJT-X and Log2OM refer to 'ADIF UDP' which
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
wrote:
Hello Doug,
Getting the log from WSJT-X to
On 19/11/2019 17:38, Zeev Stadler wrote:
Ideally, one should just turn-off "Enable Tx" on WSJT-X to operate to
SSB on the rig.
Hi Zeev,
the recommended procedure is to leave "Monitor" mode in WSJT-X by
pressing the "Monitor" button on the WSJT-X main window, press it again
to resume active
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.
73
Zeev
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
13 matches
Mail list logo
