Julius,
Easy answer (but not really 'silly') - the KPA100 has no bandswitch or other
controls - it gets its information from the K2, so the K2 must have a path
to communicate with the KPA100. There are 4 signal lines on the KIO2
connector that contain the signals required.
I might point out that the presence of these signals IS the reason one
should NEVER connect a regular 'computer' serial cable directly to the K2
KIO2 connector - it will cause REALLY BAD things to happen to the K2 if
RS-232 level voltages are applied to these 4 pins.
A 2 to 3 foot cable should be no problem - if I recall, KI6WX tested with a
10 foot cable.
Also, plan to replace the minature 15 uH inductor on the KIO2 AUX2 board
with one that can handle more current. Any 15 uH choke rated for about 100
ma should do nicely, or wind your own on a FT23-43 core (9 turns = 15 uH) or
a FT37-43 core (6 turns = 15 uH) - the wire size is not critical, use the
leftovers from your K2 build.
73,
Don W3FPR
----- Original Message -----
OK, this may be a silly question but... Why do I need
a KIO to run the KPA100 remotely? In my case, I just
want to have the PA in a seperate enclosure to keep it
in a better ventilated area of my congestion (maybe 2
or 3 feet away from the K2). Is this too long of a run
for the I/O cable or RF?
_______________________________________________
Elecraft mailing list
Post to: [email protected]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
