When using Omni-Rig, I believe WSJT-X Does not control the operation mode
of the IC-7300 regardless of the "Split Operation" selection.
As far as I can tell, WSJT-X assumes the user is responsible for selecting
"USB-D" for both VFO-A and VFO-B.
Here is a scenario that demonstrated this:
- Change
On Tue, Dec 17, 2019 at 2:53 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> v2.1.2
>
> We're getting an inconsistent and somewhat hard to reproduce situation
> where on an IC-7300 VFOB is not getting set to USB-D.
>
I have seen this also. My setup runs WSJT-X through
Hi Mike,
ok, so if Log4OM is in the mix I assume you are using rigctld. Can you
provide a verbose Hamlib trace of the issue?
73
Bill
G4WJS.
On 17/12/2019 23:05, Black Michael via wsjt-devel wrote:
Hamlib
On Tuesday, December 17, 2019, 05:01:25 PM CST, Bill Somerville
wrote:
On 17/12
Hamlib
On Tuesday, December 17, 2019, 05:01:25 PM CST, Bill Somerville
wrote:
On 17/12/2019 22:47, Black Michael via wsjt-devel wrote:
v2.1.2
We're getting an inconsistent and somewhat hard to reproduce situation where
on an IC-7300 VFOB is not getting set to USB-D.
It
On 17/12/2019 22:47, Black Michael via wsjt-devel wrote:
v2.1.2
We're getting an inconsistent and somewhat hard to reproduce situation
where on an IC-7300 VFOB is not getting set to USB-D.
It seems to me that WSJT-X should be setting USB-D mode to VFOA and,
when in split, to VFOB on every tr
v2.1.2
We're getting an inconsistent and somewhat hard to reproduce situation where on
an IC-7300 VFOB is not getting set to USB-D.
It seems to me that WSJT-X should be setting USB-D mode to VFOA and, when in
split, to VFOB on every transmit but it appears there's some time when WSJT-X
thinks VF
In JT65 mode B I get the following after a minute running in WSJT-X v2.1.2
on Mint 16.04. This does not appear to be happening in mode A. WSJT-X then
must close. All other modes appear to be working fine.
Subprocess Error
Subprocess failed with exit code 2
Fortran runtime error: Index '1' of dim
