| |
VK7AX > LINHAM 10.07.08 04:20l 96 Lines 3324 Bytes #999 (0) @ WW
BID : VK7AX-1007LE
Read: GUEST
Subj: Re: gMFSK ?
Path: IZ3LSV<IK2XDE<DB0RES<ON0BEL<N9ZZK<CX2SA<VK7AX
Sent: 080710/0220Z @:VK7AX.#ULV.TAS.AUS.OC #:48832 [Ulverstone] FBB7.00g $:VK7A
From: VK7AX@VK7AX.#ULV.TAS.AUS.OC
To : LINHAM@WW
From: Erik Jakobsen <erik_ja(AT)mail.tele.dk>
Date: Wed, 09 Jul 2008 08:38:19 +0200
To: Dave Platt <dplatt(AT)radagast.org>
CC: linux-hams(AT)vger.kernel.org
Dave Platt wrote:
>
> I found that I was having problems a few years ago with a Kenwood
> TS-2000 under similar circumstances. rigctl seemed to work OK, but
> hamlib-equipped applications couldn't read out or control the
> frequencies or modes.
>
> The problem turned out to be one of command turnaround time. The
> TS-2000 requires some amount of "quiet time" after the port has been
> opened, and after it has sent the response to a command, before it's
> ready to receive / recognize / act on the next command.
>
> When you run rigctl, human reaction time and typing speed limitations
> provide far more than the required time. When you run hamlib-equipped
> software, it will often issue commands with little or no delay
> between, and this tends to overwhelm the rig's microprocessor. The
> net result is that commands are not recognized properly by the rig,
> and either elicit no response at all or a "Hunh? Say what?" error of
> some sort.
>
> My recollection is that there is a usable workaround. The rig
> definition tables in the hamlib drivers have a "post_write_delay"
> value which can be set to a suitable number of milliseconds, to slow
> down the software's issuing of back-to-back commands.
>
> I set the TS-2000 post-write delay to 50 milliseconds, and it made a
> world of difference.
>
> You may need to download the Hamlib source code, tweak the driver for
> the rig to include a suitable amount of delay, and rebuild the
> libraries. If this fixes your problem, please submit a patch to the
> Hamlib maintainers so that it can be incorporated into the next release.
>
>
>
Many tnx Dave for your fast reply :-)
I use openSUSE 11.0 and would uninstall hamlib.
Then there was nothing to do but also let fldigi leave its install.
After I installed hamlib, and the after again I would install the fldigi
rpm again.
But it would also install the hamlib rpm.
Then I downloaded the fldigi tarball.
But it tells me:
# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles..no
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking for C++ compiler default output file name...
configure: error: C++ compiler cannot create executables
See `config.log' for more details.
What am I to do now
Erik OZ4KK
--
******************************************************************
ABOVE IS A CROSS POST TO THE PACKET RADIO NETWORK IN AN EFFORT TO
PROMOTE FURTHER INTEREST IN HAM SOFTWARE USING LINUX OPERATING
SYSTEMS AND PACKET RADIO
Courtesy Tony VK7AX VK7AX(AT)VK7AX.#ULV.TAS.AUS.OC
******************************************************************
Read previous mail | Read next mail
| |
