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 server process to create a trace log called
OmniRig.log in the same directory. Run a minimal test to reproduce one
of the issues and send me that file attached to a PM please?
73
Bill
G4WJS.
On 20/11/2019 19:59, Zeev Stadler wrote:
Hello Bill,
None of the programs is running in elevated mode and the problem exists.
See
https://user-images.githubusercontent.com/1304610/69273411-fb01cb00-0be0-11ea-95de-78effc5197bc.png
for a screenshot
73
Zeev
4X5ZS
On Wed, Nov 20, 2019 at 9:48 PM Bill Somerville <[email protected]
<mailto:[email protected]>> wrote:
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 "Elevated" option. This will add a new detail
column with values of "Yes" or "No" for each process's elevated
status. Check that wsjtx.exe, OmniRig.exe, and the Log4OM
processes are running without elevation.
Note that there several ways to run a process with elevated rights
including explicitly running as Administrator or checking the
"Properties->Compatibility->Run this program as an administrator"
option in either the program executable, or shortcut used to start it.
As I stated before, none of the relevant programs should be run
with Administrator rights, it is not necessary and only creates a
security risk. If any process is running with elevated rights it
will be blocked from interoperating with other processes that do
not have elevated rights. Elevated rights are only needed to
access protected files and directories and other protected system
resources, none of which are needed for basic user applications
like log keeping, CAT control, audio streams, or accessing remote
network resources.
73
Bill
G4WJS.
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 update from rig", and WSJT-X is unable to communicate with
the rig.
Please let me know how can I further help clarify the problem.
73
Zeev
4X5ZS
On Tue, Nov 19, 2019 at 5:31 PM Zeev Stadler
<[email protected] <mailto:[email protected]>> 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
<http://www.dxatlas.com/OmniRig/>". 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 started
Log4OM 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
<https://4z1kd.github.io/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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
