Re: [wsjt-devel] VFO-B behavior
> 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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] VFO-B behavior
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 amplifier in-line with too much power to tune and for some could fry the amplifier. Mike On Sunday, March 3, 2019, 4:59:00 PM CST, Paul Kube wrote: 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 IC-7300 with tune-on-PTT enabled. 73 Paul K6PO On Sun, Mar 3, 2019 at 12:56 PM 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 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 it appears to do a reverse split and tuning can, of course, be way off depending on where VFOA is sitting. Once you click transmit VFOA does get changed but by then it can be too late for your tuner. I believe all that we need to do is make VFOA the active VFO when switching bands before any frequencies are set. Is there any reason not to make VFOA the active one? de Mike W9MDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] VFO-B behavior
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 IC-7300 with tune-on-PTT enabled. 73 Paul K6PO On Sun, Mar 3, 2019 at 12:56 PM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > 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 it appears to do a reverse split and tuning > can, of course, be way off depending on where VFOA is sitting. Once you > click transmit VFOA does get changed but by then it can be too late for > your tuner. > > I believe all that we need to do is make VFOA the active VFO when > switching bands before any frequencies are set. Is there any reason not to > make VFOA the active one? > > de Mike W9MDB > > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] VFO-B behavior
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 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 it appears to do a reverse split and tuning can, of course, be way off depending on where VFOA is sitting. Once you click transmit VFOA does get changed but by then it can be too late for your tuner. I believe all that we need to do is make VFOA the active VFO when switching bands before any frequencies are set. Is there any reason not to make VFOA the active one? de Mike W9MDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] VFO-B behavior
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 it appears to do a reverse split and tuning can, of course, be way off depending on where VFOA is sitting. Once you click transmit VFOA does get changed but by then it can be too late for your tuner. I believe all that we need to do is make VFOA the active VFO when switching bands before any frequencies are set. Is there any reason not to make VFOA the active one? de Mike W9MDB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Unexpected Behavior
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 10.1.9.2 in Special Mouse Commands of the user guide. Best wishes, Claude (DJ0OT) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
