Hi Bill, Thank you forpointing me to the Hamlib documentation, and yes, I do understand thatthe Hamlib library removes the requirements of knowing the exactcommands needed to control any rig that Hamlib supports. While I have onlydone a cursory read through, I believe I did find the function calls that WSJT-X might be calling when "Split=Rig" is specified as it changesfrom RX to TX with the possibility of the need to change the TX offset. In any event, Icertainly was not trying to tell you to re-engineer your code, just apotential workaround based on my experience of writing my own code totrack/control various rigs with different capabilities. My apologies if it was taken the wrongway. As always, thank youagain for all your previous help and support. 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: Sat, Nov 13, 2021 5:11 am Subject: Re: [wsjt-devel] VFOs reversing 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.
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
