FWIW, I've had some problems lately with Omnirig 1.19, WSJT-X 2.1.2 and
Swisslogforwindows. The radio is a FT-1000MP. Using "fake it", the radio did
not return to the listening frequency on VFO A, but stayed on the Tx frequency.
Trying a fallback to Omnirig 1.16 and 1.18 did not solve the proble
On 12/18/19 1:24 PM, Black Michael via wsjt-devel wrote:
The only reason you would HAVE to run Mode=Rig Split on WSJT-X is if
your rig doesn't behave well on Fake It.Generally speaking rigs will
behave a bit better in Rig Split.
Sometimes, Split=FakeIt works better than Split=Rig. We have to exa
Turns out it was a bug in the FLRig backend in hamlib.
Testing the fix now
de Mike W9MDB
On Wednesday, December 18, 2019, 11:25:24 AM CST, Saku
wrote:
Black Michael via wsjt-devel kirjoitti 18.12.2019 klo 13.43:
> Not a collision.try it yourselfset rig to VFOA USB-D and V
Black Michael via wsjt-devel kirjoitti 18.12.2019 klo 13.43:
Not a collision.try it yourselfset rig to VFOA USB-D and VFOB
to USB. Then press Tune on WSJT-X. It will frequently not change
VFOB to USB-D.
I did 46 times. No problem.
[saku@hamtpad tmp]$ cat /etc/
Bill,
My mistake. You are absolutely right. I have changed "Settings->Radio-Mode"
to "None" and forgot about it.
This was done because selecting "IC-7300-DATA" as Omni-Rig's "Rig type" and
selecting "Data/Pkt" as WSJT-X's "Radio-Mode" forced the transceiver to use
the 1.2Khz "FIL2" IF filter rath
Bill,
Okay, okay I misunderstood the original post. I have used and continue to
use both methods. Fake It has proven easier to implement for me so I
mostly use that but Rig Split you are correct works, too. But I will
suggest there is some confusion in terms that pops up from time to time.
You
That was what I meant by not behaving well on Fake It.Of course your
explanation is much better :-)
Mike
On Wednesday, December 18, 2019, 07:10:48 AM CST, Bill Somerville
wrote:
On 18/12/2019 12:24, Black Michael via wsjt-devel wrote:
> The only reason you would HAVE to run Mode=Rig S
On 18/12/2019 12:24, Black Michael via wsjt-devel wrote:
The only reason you would HAVE to run Mode=Rig Split on WSJT-X is if
your rig doesn't behave well on Fake It.
Generally speaking rigs will behave a bit better in Rig Split.
Mike,
you might want to reword that paragraph. Using SPLIT on t
Johnny,
are you deliberately trying to confuse here? First you say using SPLIT
on a rig has no place with FT8, then here you say you do exactly that.
Make up your mind!
73
Bill
G4WJS.
On 18/12/2019 12:51, John Kludt wrote:
Mike,
I always run Fake it or Rig split - great feature and yes, it
On 18/12/2019 12:13, John Kludt wrote:
Zeev,
I don't really understand your point - why are you setting the rig for
spilt operation? I sometimes worry that the use of the word "split"
immediately brings to mind the "Up 1 KHz" CW mindset. I work FT8
"spilt" all the time but I never ever put
Mike,
I always run Fake it or Rig split - great feature and yes, it keeps the
signals clean and preseves power just like ti is supposed to. I run my Tx
bandpass up to 3000 - I could go higher but most of the older rigs struggle
so not much point.
John
On Wed, Dec 18, 2019 at 7:27 AM Black Micha
This extract from the User Guide Section 4.2 might help to explain why Split
mode is useful:
---
Split Operation: Significant advantages result from using Split mode (separate
VFOs for Rx and Tx) if your radio supports it. If it does not, WSJT-X can
emulate such behavior. Either method will res
The only reason you would HAVE to run Mode=Rig Split on WSJT-X is if your rig
doesn't behave well on Fake It.Generally speaking rigs will behave a bit better
in Rig Split.
If you are saying you don't run Fake It either then you are risking harmonics
and/or power loss. Split and Fake It both pre
Zeev,
I don't really understand your point - why are you setting the rig for
spilt operation? I sometimes worry that the use of the word "split"
immediately brings to mind the "Up 1 KHz" CW mindset. I work FT8 "spilt"
all the time but I never ever put the radio itself in "Split" mode. All
"spl
Not a collision.try it yourselfset rig to VFOA USB-D and VFOB to USB.
Then press Tune on WSJT-X. It will frequently not change VFOB to USB-D.
FLRig is the rig conrtoller, FLDigi talks to FLRig, WSJT-X talks to FLRig,
Log4OM talks to rigctld talking to FLRig, local utility talks to FLRig
Zeev,
that's not correct. WSJT-X will control the mode of your rig if you wish
it to. The options available in the "Settings->Radio-Mode" group
determine the mode used on your rig:
"None" - WSJT-X does not attempt to control the rig's mode,
"USB" - WSJT-X sets the rig mode to U
Black Michael via wsjt-devel kirjoitti 18.12.2019 klo 0.47:
Band change seems to work all the time but externally changing
frequencies (from Log4OM) seems to cause this situation sometimes.
de Mike W9MDB
Hi!
Looks like a collision when 2 programs tries to access same rig port.
Start a rigct
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
23 matches
Mail list logo
