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

[Chris B. <ry...@cr...>]

Take this perhaps as another step of debugging rather than any kind of fix

On the basis that the last few bytes in the status return are undefined, they 
can't be used for anything.

So I downloaded the source of 1.2.10 (which I don't pretend to understand to 
any degree as my software skills are 20+ years old and I never did do any C). 
I looked around a bit to find were the get status command was issued in 
ft747.c, observed the parameter for the no. of characrers expected and edited 
the file ft747.h to change

#define FT747_STATUS_UPDATE_DATA_LENGTH      345

to

#define FT747_STATUS_UPDATE_DATA_LENGTH      344

in an attempt to fool hamlib. Then recompiled and ran ldconfig.

rigctl now runs without a timeout error message and F, M, T commands work. 
Clearly I should expect a buffer overflow somewhere as I suspect the rig really 
is sending 345 characters and I don't know where the buffer space is 
defined/allocated.

hth

Chris g3wie