Re: [Hamlib-developer] FT747GX timeout problem - solved?
Library to control radio transceivers and receivers
Brought to you by:
n0nb
Menu
▾
▴
Re: [Hamlib-developer] FT747GX timeout problem - solved?
|
From: Stephane F. <f8...@fr...> - 2010-03-29 18:03:49
|
Chris Bryant skribis: > On Sunday 28 Mar 2010, you wrote: > > 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 Thanks for confirming the libltdl-dev issue. On a side note, that means we have to fix that problem before thinking of releasing hamlib 1.2.11. > 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.... Indeed, but unstable versions needs courageous beta-testers for the good of everybody. It's very true for Hamlib also. > 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 If you're into some more testing today, download the monday snapshot, it has been improved with: - cached update data - passband width in get_mode - added set_mem/get_mem - various fixes and cleanup Attn hamlib devs: I've added a generic function rig_check_cache_timeout() in the frontend (src/misc.c), inspired by the ft817 code. This should make the caching of status easy to handle in various backends. Maybe the ft817, ft857, and the ft897 could be converted to save for some code size. Look at yeasu/ft747.c or tentec/paragon.c (newly fleshed out!) for an example. Is there any rig that should get status caching? ft757gx, ft767gx ? There's also a function rig_force_cache_timeout() in the frontend that can be used in any backend_set_* function that could modify the current status. This may allow longer cache duration (c.f. comment in yaesu/ft817.h about FT817_CACHE_TIMEOUT). > 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 ........ -- Stephane - F8CFE |
