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

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

* On 2010 27 Mar 14:28 -0500, Mark Pilant wrote:
> I managed to locate a copy of the manual online:
> 
>      <http://hamradio.lakki.iki.fi/new/Documents/Manuals/Yaesu/base&portable/Yaesu%20FT-747GX%20users%20manual.pdf>

Thanks for that.  Added to my collection.

> Starting on page 26 at the CAT commands.  On page 27, Reading Transceiver
> Status, it does indeed say 345 bytes should be transferred.

Note also that in column 1 at the bottom of page 26 it mentions "767"
as the model as well.  Oops!

> Since Chris seems to be seeing only 344, this suggests a couple of things:
>     1)   The manual is incorrect :-)

My first guess.

>     2)   For some reason, the last byte is not being sent (pretty unlikely)
>     3)   The first byte is being missed

I think Chris has shown he's getting the first byte by his message of
yesterday.

>     4)   ??
> 
> Probably the easiest way to figure out whether 2 or 3 is the case, it should
> be possible to take the data Chris has returned and see how it matches up
> with the manual.  This should make it real obvious if the first or last byte
> is missing.

Also, the backend code parses the data per the manual so an offset
error will show rather quickly.

> As for the length being incorrect, I expect this would take getting samples
> from several rigs to see what is being returned.  It may also be possible to
> use another program to see what information they receive and whether the
> amount is 344 or 345 bytes.

There is a 747 locally, I'm not sure if he has an interface for it.  I
can ask at work on Monday as we share the same office.  :-)

> Just some thoughts (from a quasi-lurker :-)

Always welcome to read the thoughts of anyone who wishes to chime in.

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