On 07/07/2017 14:43, Black Michael via wsjt-devel wrote:
For Bill....
The easy way to test functionality is to remove set_vfo from dummy.c
in hamlib and test with that and rigctld.
WSJT-X will fail. So it's just changing the set_vfo capability logic
to match get the get_vfo logic.
Bill's hamlib has been updated for the rigctld side to fix that side
of the problem. The set_vfo.patch is the WSJT-X side of the equation.
This showed up on the FT-891/991 not having vfo capabilities.
de Mike W9MDB
Hi Mike,
I have committed a change based on your patch r7818. I had to change it
a fair bit to get it working on other rigs and to not force a set VFO
operation for all at startup. I have tested with a mock dummy rig and
rigctld as you suggest, I had to disable both get and set VFO to
reproduce an error.
You may wish to review my change and maybe send a version to whoever had
the initial issue with the FT-991 and rigctld.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
