[Elecraft] K2 Info 080 Error while attempting computer contro

[david]

The K2 cables are not standard RS-232 cables. They only have pins 2,3,
and 5 connected.  This is documented in the manuals,  you should review
the manuals carefully to make sure you have constructed the cables
correctly.

INFO 080 according to the manual indicates a problem with the I/O
controller or possibly the AUX bus.  See appendix E of the K2 manual.

I know I'm just telling to you to "RTFM" but the Elecraft documentation
is pretty good.  You can always download an up-to-date copy of any
manual from the Elecraft web site.



> Message: 27
> Date: Sun, 02 Oct 2011 09:11:14 -0400
> From: "Eugene Balinski" <eugeneb at nni.com>
> Subject: [Elecraft] K2 Info 080 Error while attempting computer contro
> To: <elecraft at mailman.qth.net>
> Message-ID: <web-389585780 at admin.nni.com>
> Content-Type: text/plain; charset="windows-1252"
> 
> All,
> 
>   Trying to get my K2/100/KAT-100 operation with N1MM.
>   Bought the Elecraft USB-Serial adapter. Installed the
> driver from the FTDI web site. Seems to be operational.
>   
>    Connected the cable to the computer (device found, etc).
>  Connected the other end to the radio/antenna tuner serial
> cable, powered up the radio, and get the "INFO 080" error.
> Cycled the power, same issue.  
> 
>    Also, and the antenna tuner will not power up while the
> computer cable is connected. The serial cable is  the "Y"
> configuration running from the radio to the tuner and then
> to the db-9 where the serial- usb converter is connected.
> Turning off the radio, removing the cable and re-powering
>  the tadio returns the radio to normal ops.
> 
>     I disconnected the antenna tuner portion of the cable
> and still get the same error. Reconnect everything without
> the serial-usb converter in the line and all works
> normally.
> 
>     This is not a stock serial cable. It is supposedly
>  one made especially for this application i.e K2 "special
> cable". I guess I will start by ohming out the cable. 
> 
>    Any other ideas would be appreciated.
> 
> 73
> 
> Gene K1NR
> 
> K2 6XXX