Re: [Hamlib-developer] FT747GX timeout problem - (disgusting) workaround

[Nate B. <n0...@n0...>]

* On 2010 27 Mar 16:08 -0500, Chris Bryant wrote:
> 
> Yes, I have the user manual which is the only data I've ever found on the 747 
> CAT. The service manual just covers hardware. The user manual clearly specifies 
> inter-byte spacing of 50 - 200 mSec and I wonder if a decimal point got lost 
> somewhere and they meant to say 5 - 20. It also clearly specifies 345 bytes of 
> status data are returned in response to the 00 00 00 00 10 command, so that 
> could be wrong as well. But has no-one else spotted this before? It's 
> immediately obvious if you try rigctl.

There's the rub, is anyone actually using the 747 these days with
Hamlib?  As our code doesn't "phone home" or anything of the like, it's
impossible to tell whether anyone actually uses it.  Also, even though
the 747 code is some of the oldest in Hamlib, if it doesn't get used,
it doesn't get tested.

The difference between MixW and Hamlib may well be the difference in
why MixW works and Hamlib didn't.  Of course we can't examine the MixW
code, but it's possible that it is not as strict looking for the byte
count on the wire as Hamlib.  That's just conjecture on my part.

The worst case is what do we do if we find that some rigs report 344
bytes and others 345?

And, no, your work-around is not disgusting!  It's a valid fix to your
problem.  Now we need to test other 747s to see what's going on.

73, de Nate >>

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://n0nb.us/index.html