[Hamlib-developer] Bug: Yaesu FT-736r

[Dave B <g8k...@go...>]

Hi.

Just tried Hamlib 4.5.1   Built and installed into ~/Local/bin just 
fine.  (Linux Mint 19.3 64 bit)

Using it with Gpredict, and a small Python "shim" (to simulate 
data/value read-backs from a radio that doesn't provide them) with 
Hamlib 3.3 after Bill G4WJS made a source code adjustment he called 
"lazy rigctld()"  that allowed Gpredict to not only seize the radio and 
use it, but when the "Disengage" feature was activated, where it dropps 
the connection with Hamlib, the radio would be "released" from CAT 
control, allowing front panel use again.

(Often needed when changing between birds, so "tweak" the rig, so it 
would not have a hissy fit trying to enable same band duplex satellite 
working!  Especially if the rig only has 2m and 70cm capability.)

Anyway, I find that like the earlier version 4's  Hamlib 4.5.1 does not 
release the radio, when the last "client" has disconnected from 
rigctld.  Otherwise everything works.

I have just built a fresh instance of the modified 3.3 code, to make 
sure I have the sources with that change, and indeed it seems I do, as 
that works again just fine.

Looking back in emails, Bill said this in reply to a query as I was 
going to ask some other Linux/FT736 users to try it, but he had pulled 
it from his personal repo', as it had been merged with the official 
source...

(This was March 21st 2018)
"I deleted my branch because it has been merged into the official Hamlib 
repository. The changes are also in the latest WSJT-X beta release 
v1.9.0-rc3."

Sadly, it seems not to feature in Hamlib 4.x after all  :-(

I am "not good" with other people's C (or C/C++) code, especially code 
spread over dozens of source files.  But if someone can point me at what 
might have changed, maybe I can revert it?   I can't see any significant 
difference between the 3.3 and 4.1.5 instances of the FT736 sources, so 
it must be elsewhere.

If anyone else would like a copy of the modified 3.3 sources to compare 
with, no problem, I can send a tar.gz file anywhere.

Enough for now.

Any hints etc welcome.

73.  Dave G8KBV


-- 
Created on and sent from a Unix like PC running and using free and open source software: