> On Mar 3, 2019, at 13:52, Black Michael via wsjt-devel
> wrote:
>
> On ICOM rigs hamlib assumes split is always on VFOB to cover rigs without
> status commands...as does FLRig (and perhaps others).
Kenwood is the same way, and I’m not sure I would want to alter that.
Gary - AG0N
Both conditions need to fixed. VFO-A needs to be set as selected VFO and VFO-B
set to the split freq at all times. Otherwise a tune instigated from an
external source will be on the wrong frequency.And yes...I know you can click
Tune in WSJT-X and then VFO-B gets set...but that leaves the ampl
I'm not talking about altering the split on VFOB behavior.
I'm referring to the fact that if VFOB is active on the rig that VFOA does not
get set at all. So having WSJT-X simply make VFOA the active VFO would fix the
problem and split would still be on VFOB.
Mike
On Sunday, March 3, 2019
If VFO-B is the active VFO and you switch bands on WSJT-X only VFOB gets
set...VFOA does not change..
The same is true if VFO-A is the active VFO; VFO-B does not get set with a
band change until you transmit.
I just hit WSJT-X's "Tune" button for a second when switching bands. Works
fine on the
Also when switching bands should set VFO-B too for split operation if
appropriate.
Mike
On Sunday, March 3, 2019, 2:56:29 PM CST, Black Michael via wsjt-devel
wrote:
Found an undesirable behavior that I think can be easily fixed.
On ICOM rigs hamlib assumes split is always on VFOB to
Found an undesirable behavior that I think can be easily fixed.
On ICOM rigs hamlib assumes split is always on VFOB to cover rigs without
status commands...as does FLRig (and perhaps others).
If VFO-B is the active VFO and you switch bands on WSJT-X only VFOB gets
set...VFOA does not change...so
On 3/2/19 7:35 PM, Tag Loomis (Tag) wrote:
Hi Tag,
I wouldn't consider it a bug, more of a known action, but I could be
wrong of course.
It's probably a feature.
It would be interesting to see if our expected behaviour can be
performed with Ctrl and double click, if I understand well point
