[ICOM] 706mk2g CI-V

[Jim Miller KG0KP]

Yes I have scopes.  Thanks.  First off, I didn't even know there was "enable 
the transceiver's "CI-V Transceiver" menu item". So will definitely check 
that and then follow your steps.  Thanks.  I didn't know what it goes 
through when it is trying and if it needed to go through a connect protocol 
or something first.

Getting late (early) and won't get a chance to look at it until late 
tomorrow at the earliest (except maybe to sneak down and check the menu 
setting.  Will have to get the book to find that too.

Thanks again es 73, de Jim KG0KP


----- Original Message ----- 
From: "Dave AA6YQ" <aa6yq at ambersoft.com>
To: "ICOM Reflector" <icom at mailman.qth.net>
Sent: Sunday, May 13, 2012 12:07 AM
Subject: Re: [ICOM] 706mk2g CI-V


>>>>AA6YQ comments below
>
> -----Original Message-----
> From: icom-bounces at mailman.qth.net
> [mailto:icom-bounces at mailman.qth.net]On Behalf Of Jim Miller KG0KP
> Sent: Thursday, May 10, 2012 10:50 AM
> To: ICOM Reflector
> Subject: [ICOM] 706mk2g CI-V
>
>
> OK, I am not ready to believe the CI-V port on my 706MkIIG is bad.  It 
> used
> to work and now it doesn't.  Windows 7 Home - USB to CI-V (was prolific) -
> 706MkIIG.
>
> I was installing other programs - do not know exactly when this 
> not-working
> CI-V thing started.  I am looking for some way to prove whether the CI-V 
> is
> bad or not.
>
> The other option is the USB driver for the CI-V or the USB to CI-V "cable"
> itself.
>
> I bought 2 new cables from different places (one was FTDI and the other
> Prolific) and they went and found new drivers (Windows 7) and now I cannot
> get any other drivers to load manually.  So I do know the original driver
> that was working has unfortunately been replaced,.
>
> How can I isolate this problem to the bad component?  I don't mind paying
> for what I need but do not want to pay for a lot of stuff I don't need 
> (more
> new CI-V cables, repair for 706, when it is really the driver).
>
>>>>Do you have an oscilloscope or logic analyzer? If so, you can
>
> 1. enable the transceiver's "CI-V Transceive" menu item
>
> 2. attach your scope or analyzer probe to the transceiver's "CI-V" signal
> (its a TTL open-collector bus)
>
> 3. using its front panel, QSY the transceiver; you should see async data
> (start bit, 8 data bits, stop bit(s)) on the "CI-V signal"
>
>>>>If this works, then connect the transceiver's CI-V signal to a CI-V 
>>>>level
> converter (CT-17 or equivalent), connect the level converter to a serial
> port, fire up a CI-V control application that works when the transceiver's
> "CI-V transceive" mode is enabled (e.g. DXLab Commander), and configure 
> the
> application's COM port settings to the appropriate baud rate, word length,
> etc.
>
> 4. using its front panel, QSY the transceiver; the application's frequency
> display should track the transceiver's frequency
>
>>>>If you get this far, this then "outbound CI-V" is working. To test
> inbound CI-V, use the control application to continuously change the
> transceiver's frequency; if the transceiver's frequency doesn't actually
> change, use the oscilloscope or logic analyzer to see if there is async 
> data
> on the "CI-V signal" while the application is attempting to change the
> transceiver's frequency. If there is no async data, the COM port or USB
> adaptor or CI-V interface is likely broken; if you see async data but the
> transceiver doesn't QSY, likely the transceiver's CI-V interface is 
> broken.
>
>    73,
>
>        Dave, AA6YQ
>
> ----
> 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
>