[ICOM] Computer Can't Talk to Radio
cwman at juno.com
cwman at juno.com
Thu Jul 23 17:08:38 EDT 2009
Thanks, Larry.
73,
Fred/NA2U -- CWMAN...I'D RATHER WORK CW!!!
Yeah...but it's a DRY heat.
"Wretched excess is just barely enough." -- Mario Batali (from Heat by Bill Buford)
---------- Original Message ----------
From: Larry Young <k4lxv at bellsouth.net>
To: ICOM Reflector <icom at mailman.qth.net>
Subject: Re: [ICOM] Computer Can't Talk to Radio
Date: Thu, 23 Jul 2009 08:54:09 -0700 (PDT)
Fred: Here is a web site that gives complete info on the CI-V and how to trouble shoot it when there are problems. http://www.plicht.de/ekki/civ/
Larry K4LXV
--- On Wed, 7/22/09, Jim Hargrave <w5ifp at gvtc.com> wrote:
From: Jim Hargrave <w5ifp at gvtc.com>
Subject: Re: [ICOM] Computer Can't Talk to Radio
To: "ICOM Reflector" <icom at mailman.qth.net>
Date: Wednesday, July 22, 2009, 9:59 PM
Fred,
What are your com settings?
I would suggest you use set the com port and radio CI-V baud rate to 4800 or
9600. Another potential problem is the Poll rate. I would try it at 500 ms
for starters. A fast poll rate sometimes result in data collisions.
Do not use Autobaud. Most programs do not support the autobaud routine.
Another option turn off the CI-V "Transceive" function in the radio. You may
be experiencing data collisions.
Some CI-V adapters require that RTS/DTR be set high because they depend on
the computer for power. Try that in your port settings and see if that
helps.
* 73's Jim W5IFP *
>-----Original Message-----
>From: icom-bounces at mailman.qth.net
>[mailto:icom-bounces at mailman.qth.net]On Behalf Of cwman at juno.com
>Sent: Thursday, July 16, 2009 10:58 PM
>To: icom at mailman.qth.net
>Subject: [ICOM] Computer Can't Talk to Radio
>
>
>Using Pro III. I have checked all radio parameters, and DX4WIN
>parameters. Checked device manager for Com1 settings.
>EVERYTHING appears to be in order yet radio continues to
>time-out when I try to grab a spot. I can't get it to work
>with other programs (Writelog or N1MM). Yes, I have checked to
>make sure the CI-V is plugged into the correct radio jack.
>Someone has suggested that my CI-V might be dead. I've tried
>all jacks, no go. Power light is on.
>Have any of you had a CI-V fail? How would I check it (except
>to simply give it up for another)?
>73 and thanks,
>
>Fred/NA2U -- CWMAN...I'D RATHER WORK CW!!!
>Yeah...but it's a DRY heat.
>"Wretched excess is just barely enough." -- Mario Batali (from
>Heat by Bill Buford)
>
>____________________________________________________________
>Get your dream car or truck. Click here.
>http://thirdpartyoffers.juno.com/TGL2141/fc/BLSrjpTLa8wRSqebi9n5
Z402oZeZeffXj8Wh6O3oQVOWdzSVNYjcwSaYGqc/
----
Your Moderator: Dick Flanagan K7VC: icom-owner at mailman.qth.net
Icom Users Net: Sundays, 1700Z, 14.316 MHz
Icom FAQ: http://www.qsl.net/icom/
To support QSL/QTH.net: http://www.qsl.net/donate.html
----
Your Moderator: Dick Flanagan K7VC: icom-owner at mailman.qth.net
Icom Users Net: Sundays, 1700Z, 14.316 MHz
Icom FAQ: http://www.qsl.net/icom/
To support QSL/QTH.net: http://www.qsl.net/donate.html
----
Your Moderator: Dick Flanagan K7VC: icom-owner at mailman.qth.net
Icom Users Net: Sundays, 1700Z, 14.316 MHz
Icom FAQ: http://www.qsl.net/icom/
To support QSL/QTH.net: http://www.qsl.net/donate.html
____________________________________________________________
Paying too much for your business phone system? Click here to compare systems from top companies.
http://thirdpartyoffers.juno.com/TGL2141/fc/BLSrjpTQZan3lCPLhXtZKHHr4fk6agrVRVjxpTkxOPXD4ALCcZpO2fImOcQ/
More information about the Icom
mailing list