Thanks Mike.
73
Bill
G4WJS.
On 07/06/2020 14:35, Black Michael via wsjt-devel wrote:
OK...it's implemented in hamlib now...you should see it in the next
release.
Mike W9MDB
On Sunday, June 7, 2020, 08:20:57 AM CDT, Chuck Reti WV8A via
wsjt-devel wrote:
Mike/Bill,
I tested “Rig"
OK...it's implemented in hamlib now...you should see it in the next
release.Mike W9MDB
On Sunday, June 7, 2020, 08:20:57 AM CDT, Chuck Reti WV8A via wsjt-devel
wrote:
Mike/Bill,
I tested “Rig" split with the FT-897D using the FT-857 setting. It works.
“Split” mode is indicated on
Mike/Bill,
I tested “Rig" split with the FT-897D using the FT-857 setting. It works.
“Split” mode is indicated on the radio’s panel, and, on the “B” VFO, the
correctly offset TX frequency is set and used in Transmit.
I’ve always used “Fake It” with the 897, since, from early on in my use of
It's not a regression...the FT857 has never had set_vfo or get_vfo enabled so
never should have worked.
The FT857 does have set/get_vfo but it uses a vfo toggle just like the FT897.
If the FT857 is working well with this we can implement the same thing for the
FT897.
Are you operating in rig
On 06/06/2020 21:33, Chuck Reti WV8A via wsjt-devel wrote:
WSJT-X 2.2.1 GA on both RaspberryPi and macOS (10.14.6)
Dreaded “RigFailure Hamlib error: Target VFO unaccessible while
getting current frequency” when Rig: Yaesu FT-897.
Have not had this issue with these settings on previous
WSJT-X 2.2.1 GA on both RaspberryPi and macOS (10.14.6)
Dreaded “RigFailure Hamlib error: Target VFO unaccessible while getting
current frequency” when Rig: Yaesu FT-897.
Have not had this issue with these settings on previous releases.
The good news is, that, if I select Rig: Yaesu FT-857,
