<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Nov 29, 2013 at 3:00 AM, Chris Suleske <span dir="ltr"><<a href="mailto:suleske@gmail.com" target="_blank">suleske@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">I've successfully made cables for both a Baofeng UV-3R and UV-5R using a CP-2102 USB board. Total cash outlay for each, about $3.<div>
<br></div><div>Now I'm moving on to my real radio, an Icom IC-T90A. I found the following info:</div>
<div><br></div><div><a href="http://highfields-arc.co.uk/constructors/other/opc478.htm#usb" target="_blank">http://highfields-arc.co.uk/constructors/other/opc478.htm#usb</a><br></div><div><br></div><div>But it has not produced fruit with the Icom CS-T90A software. Specifically, it errors "Cannot access COM port." If I remove the cable / diode from the header and jump TX and RX pins together, the CS-T90A software responds differently, indicating "No answer from the transceiver." So, I know the software and the CP-2102 are talking. There's a note in the instructions above about connecting the CTS and RTS pins together... which I can't do on the 2102 board I have. The pins are on the IC of course, but not connected to anything on the board. The diode I used appears to be good and electrically, the cable seems sound. Any ideas?</div>
<div><br></div><div>BTW, I found a treasure trove of info on T90A programming, courtesy of Eric Behr at NIU. I plan do dig into the following when I have a little more time:</div><div><br></div><div><a href="http://www.math.niu.edu/~behr/Ham/Files/ic90memory.pdf" target="_blank">http://www.math.niu.edu/~behr/Ham/Files/ic90memory.pdf</a><br>
</div><div><br></div><div><a href="http://www.math.niu.edu/~behr/Ham/Files/Icom_T90A-Memory_Map.pdf" target="_blank">http://www.math.niu.edu/~behr/Ham/Files/Icom_T90A-Memory_Map.pdf</a><br></div><div><br></div><div>I would love to be able to easily port all the frequencies between my rig and my sons' rigs.</div>
<div><br></div><div>Chris, W1CAS</div></div>
</blockquote></div><br></div><div class="gmail_extra">Chris,</div><div class="gmail_extra"><br></div><div class="gmail_extra">What I found out by using CP-2102 modules to make programming cables for my UV-5R (and other radios) is that the module ports are not consistently labeled. Some labels indicate "what the port is, receiver or transmitter" and other labels indicate "what the port connects to on the device".</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">This webpage shows modules with both types of labeling</div><div class="gmail_extra"><a href="http://www.miklor.com/COM/UV_Technical.html#progcable">http://www.miklor.com/COM/UV_Technical.html#progcable</a><br>
</div><div class="gmail_extra"><br></div><div class="gmail_extra">If the TX means "I am the module's transmitter" and RX means "I am the module's receiver", then they would connect this way</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">module | plug</div><div class="gmail_extra">TX - Cathode</div><div class="gmail_extra">RX - Anode - Sleeve<br></div><div class="gmail_extra"><div><br></div></div>
<div class="gmail_extra">If the TX means "connect me to the device's transmitter" and RX means "connect me to the devices's receiver", then they would connect this way</div><div class="gmail_extra">
<br></div><div class="gmail_extra">module | plug</div><div class="gmail_extra">RX - Cathode</div><div class="gmail_extra">TX - Anode - Sleeve<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">So if it doesn't work connected the first way, try connecting it the second way.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Jim KC9HI</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div>