On 29/05/2020 16:54, Andy Durbin wrote:
I changed from 2.2.1 Win 64 bit to 2.2.0-rc3 Win 64 bit. RC3 would
not connect to OmniRig using the TS-590 file I had been using with ver
2.2.1. It also would not connect with the default OmniRig TS-590 file.
However, when I closed RC3 and re-started with the default OmniRig
TS-590 file, it connected ok. I was than able to change OmniRig back
to the revised TS-590 rig file. Shut down and re-start of RC3 gave a
normal connection to OmniRig.
It would appear there is an OmniRig connection problem the first time
RC3 is run after installation. The problem was not reproduced by
stopping RC3, starting 2.2.1, stopping 2.2.1, starting RC3.
While investigating the OmniRig connection problem I intentionally set
RC3 to use OmniRig Rig 2 which is not defined. This gave an RC3 error
- "wsjt-x.exe has stopped working". This appears to be repeatable as
follows:
Configure RC3 to use a valid OmniRig Rig 1 configuration
Verify normal rig connection
Select an undefined OmniRig Rig 2 - observe "Rig control error"
followed immediately by "wsjt-x has stopped working"
Select "close program"
Restart RC3 - program does not shut down and Rig 1 can be selected
Re-select an undefined OmniRig Rig 2 - observe "Rig control error"
followed immediately by "wsjt-x has stopped working"
The previously reported problem that my TS-590S is set to the wrong
frequency when WSJT starts is still present in RC3. (frequency
resolution test leaves TS-590 on wrong frequency).
73,
Andy, k3wyc
Hi Andy,
thanks for the issue reports. There have been minor changes to the
WSJT-X Omni-Rig interface, they were to fail more gracefully on systems
where Omni-Rig is not installed. It would seem that has caused some
issues with talking to Omni-Rig with no rig file selected. I'll see if I
can reproduce that here and sort it out.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
