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

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

On Sunday 28 Mar 2010, you wrote:
> Chris Bryant skribis:
> [...]
> 
> > ../libltdl/libltdlc.la ../lib/libmisc.la -lm  -ldl
> > libtool: link: cannot find the library `../libltdl/libltdlc.la' or
> > unhandled argument `../libltdl/libltdlc.la'
> 
> Looks like there's a problem with the embedded libltdl.
> To workaround that, if by any chance you're running a debian/ubuntu
> system, can you install libltdl-dev ? On the command line, this is
> something like "sudo apt-get install libltdl-dev"
> Then, you will have to run the hamlib configure script again, and make.
> 

Ok Stephane, that fixed it, thanks. I'm using debian unstable here, to be sure 
to get the latest libraries as I've found problems with amateur radio s/w 
using late versions of libraries in the past. Now that Ubuntu is mainstream, 
and developers tend to use it as a default test platform, I will switch to 
that because debian unstable is like it says, not stable....

I ran up rigctl -m 105 -r /dev/ttyS0 and it seemed quite happy with no timeout 
on the read of 344 chars, then a timeout on the potential extra char as 
expected. I did a little bit of testing, and it seems ok. I'll do some more 
detailed testing tomorrow. Here's the -vvvvv output fyi. VFO A is on 7045 LSB 
and VFO B is on 14076 AM

ft747:ft747_init called      
rig:rig_open called          
ft747:rig_open: write_delay = 5 msec 
ft747:rig_open: post_write_delay = 5 msec 
ft747: read pacing = 0                    
TX 5 bytes                                
0000     00 00 00 00 0e .....
TX 5 bytes
0000     00 00 00 00 10 .....
RX 344 bytes
0000     00 00 07 04 50 00 13 00 00 07 04 50 00 50 00 08        
....P......P.P..
0010     00 14 07 60 00 42 00 17 50 10 00 10 00 00 00 10        
...`.B..P.......
0020     00 10 00 10 00 00 00 10 00 10 00 10 00 00 00 10        
................
0030     00 10 00 10 00 00 00 10 00 10 00 10 00 00 00 10        
................
0040     00 10 00 10 00 00 00 10 00 10 00 10 00 00 00 10        
................
0050     00 10 00 10 00 00 00 10 00 10 00 10 00 00 00 10        
................
0060     00 10 00 10 00 00 00 10 00 10 00 10 00 00 00 10        
................
0070     00 10 00 10 00 00 00 10 00 10 00 10 00 00 00 10        
................
0080     00 10 00 10 00 00 00 10 00 10 00 10 00 00 00 10        
................
0090     00 10 00 10 00 00 00 10 00 10 00 10 00 00 00 10        
................
00a0     00 10 00 10 00 00 00 30 00 10 00 10 00 00 00 10        
.......0........
00b0     00 10 00 10 00 00 00 10 00 00 00 00 00 00 00 00        
................
00c0     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00        
................
00d0     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00        
................
00e0     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00        
................
00f0     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00        
................
0100     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00        
................
0110     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00        
................
0120     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00        
................
0130     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00        
................
0140     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00        
................
0150     00 00 00 00 00 00 00 00                                ........

read_block: timedout after 0 chars
ft747: vfo status = 0
ft747: VFO = A
Opened rig model 105, 'FT-747GX'
Backend version: 0.4, Status: Alpha




Chris g3wie