[ICOM] IC-706MKIIG & CT-17

[gfiber at comcast.net]

Alan,

I have a few thoughts on the trouble.

Check the cable you are using between the interface and radio.
It MUST be a MONO connection. A stereo connection does not work for CI-V.
If you have a Stereo cable you can get a Stereo to Mono adaptor and that will work.

In Icom the Stereo connection is used for cloning or at least was when I worked there.

If not a headache in loosing your stored memory information I would reset the radio and let the software find the radio. 

Most software today has the Icom default settings. Icom used to default at 1200 baud, slow yes but it works and once you get it going then increase the speed.
Getting software, radio, com ports at default will help eliminate troubles.

Your Idea of temporarily trying a known com port is a good one. I would do that first since you know it works. That will take any concerns of a com port issue away.

What are you using for the Serial port interconnection cable between the computer and CT-17? Is it a AT modem cable, 9 pin to 25 pin cable?
I think the CT-17 only requires pins 1-8 and 20 be connected. So an AT Modem cable should work fine. You do not use a Null Modem cable.

I hope some of this helps.

Gary K8IZ


 -------------- Original message ----------------------
From: "N5PA" <n5pa at n5pa.com>
> Jim:
> 
> I have powered the rig off and on several times with no success.  I am going
> home at lunch and try a couple more settings and if that does not work I
> have one of the interface cables from the N9 in Arkansas and I will try
> that.  I will try some other serial ports, also.  I have a ByteRunner serial
> card with 8 ports on it with a spider cable.  It has COM ports 4 through 11.
> I do not know if WriteLog will support anything past COM4, though.  I will
> have to look into it.  DX4WIN goes up to COM8 and I am using that port for
> controlling my RigBlaster Pro with Radio Interface to my Yaesu FT-1000MP
> MK-V on COM1.  I will give it another shot at lunch and then try the other
> cable and see what happens.  I might put it on COM1 temporarily because I
> know that port works.
> 
> 73,
> Alan, N5PA
> 
> 
> -----Original Message-----
> From: W7RY [mailto:w7ry at centurytel.net] 
> Sent: Monday, June 12, 2006 11:30 PM
> To: 'ICOM Reflector'
> Subject: RE: [ICOM] IC-706MKIIG & CT-17
> 
> Power off the rig and then back on again with the logging program
> running?
> 
> Jim W7RY
> 
> 
> -----Original Message-----
> From: icom-bounces at mailman.qth.net [mailto:icom-bounces at mailman.qth.net]
> On Behalf Of W7RY
> Sent: Monday, June 12, 2006 9:29 PM
> To: 'ICOM Reflector'
> Subject: RE: [ICOM] IC-706MKIIG & CT-17
> 
> I dunno then... Do you have a breakout box to see if you're getting data
> in or out of the port?
> 
> Change comm. ports?  Is the comm. port being used by another device?
> 
> 73 and good luck
> Jim 
> W7RY
> 
> 
> 
> -----Original Message-----
> From: icom-bounces at mailman.qth.net [mailto:icom-bounces at mailman.qth.net]
> On Behalf Of N5PA
> Sent: Monday, June 12, 2006 8:21 PM
> To: 'ICOM Reflector'
> Subject: RE: [ICOM] IC-706MKIIG & CT-17
> 
> Well, I changed the baud rate to 4800 and then 9600 and DX4WIN and
> WriteLog
> still do not see the radio.  It times out trying to connect to the
> radio.
> The hex address is set to 48 and it still does not work.
> 
> Alan Clark, N5PA
> 4025 Craft Lane
> Laurel, MS  39440-1268
> E-Mail: n5pa at n5pa.com
> URL: http://www.n5pa.com
> 
> 
> 
> ----
> 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/
> 
> ----
> 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/
> 
> ----
> 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/
> 
> 
> 
> 
> ----
> 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/