Moreover most rigs with targetable frequency do not have a "set freq on current
VFO"....newer Icom's are an exception to that.Rigs that do NOT have targetable
frequency only have that (a lot of older rigs).
So the idea of doing the vfo swapping works non-targetable rigs but not
targetable ones.
Hamlib supports 254 rigs now and I'm seeing more edge cases of behaviors partly
due to speed ups in the serial I/O. Knob twiddling has been a problem for a
long time when users start twiddling knobs.The only knob twiddling I really
care about supporting is for satellite doppler work since that is computer
controlled and critical to operations.Other cases get support if possible but
generally at lower priority.
Currently hamlib just reports whatever the rig claims is the current VFO and in
some cases a simulated answer and I'm not inclined to overrule the rig answer
but provide a better VFO method to start using RX/TX VFO options instead of
VFOA/B and Main/Sub.
Mike W9MDB
On Saturday, November 13, 2021, 04:15:54 AM CST, Bill Somerville via
wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
Sam,
WADR before you suggest re-engineering the way WSJT-X controls rigs via
Hamlib I think you should take some time to review the Hamlib library
API. Note that the client API does not require client applications to
know what rig is being controlled or to issue low level CAT commands.
https://github.com/Hamlib/Hamlib/wiki/Documentation
73
Bill
G4WJS.
On 12/11/2021 23:11, Sam W2JDB via wsjt-devel wrote:
> Hi,
>
> The problem that I can see cropping up is that on some rigs you can not
> change the frequency of the Sub VFO until it becomes the Main VFO when
> the rig status changes to TX.
>
> You (WSJT-X) might be able to use a workaround by issuing a swap
> VFO command change the TX frequency (if needed) on the new
> Main VFO and then issue another swap VFO command.
>
> At this point you can start the TX process and let rig then takes care
> of the correct VFO swap. Mike will not need any convoluted code to
> track which is the Main VFO or Sub VFO.
>
> Just my two cents on this problem.
>
> 73,
>
> Sam W2JDB
>
>
>
> -----Original Message-----
> From: Bill Somerville via wsjt-devel <wsjt-devel@lists.sourceforge.net>
> To: wsjt-devel@lists.sourceforge.net
> Cc: Bill Somerville <g4...@classdesign.com>
> Sent: Fri, Nov 12, 2021 4:56 pm
> Subject: Re: [wsjt-devel] VFOs reversing
>
> On 12/11/2021 18:09, Black Michael via wsjt-devel wrote:
> > This is on an Elecraft K4.
> > When transmitting in split mode VFOA=Rx and VFOB=Tx and one changes
> > the Tx frequency WSJT-X assumes since VFOB is the current VFO that it
> > reverses roles and sets VFOA frequency instead.
> > If VFOB is active and split and ptt=on then VFOB is still tx. I
> > really don't know if this applies to all rigs though.
> >
> > Mike W9MDB
>
> Mike,
>
> to deal with that sort of behaviour either all rigs must do the same
> thing or WSJT-X will have to determine the rig and decide if the current
> VFO changes (as reported by Hamlib) when transmitting split on a rig by
> rig basis. Given that a number of rigs cannot be queried for the current
> VFO I would think that the best option for Hamlib is not to change the
> current VFO when transmitting split.
>
> 73
> Bill
> G4WJS.
_______________________________________________
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
