Thank you for the suggestions guys, but I think most of you misunderstood my issue. My complaint is the RJ-12 ON the ICD2. Not the other end of the cable. I have plenty of custom programming cables, but last couple of days I've been having to hold the RJ-12 connector on the ICD2. Lousy design. Those connectors s***. On 10/24/06, Tamas Rudnai wrote: > > The only thing is that a pin header is not polarized. Also PicKit2 has a 6 > pin connector -- it is not a problem as you can use it with the 5 pin one > but... > > Anyway, what's wrong with the RJ12? Is that something like a contact > problem > or just the bad taste of having a telephony socket on your programmer? > > Tamas > > > > On 24/10/06, Mike Harrison wrote: > > > > On Mon, 23 Oct 2006 21:46:28 -0700, you wrote: > > > > >Has anyone found a reasonable solution for dealing with the ridiculous > > RJ-12 > > >jack on the Microchip ICD2 other than to remove it, add wires and > > "install" > > >a new header of sorts? > > > > Yes - I've standardised on a Molex 5-pin header, chopping the RJ off the > > end of the cable. > > Handy hint to save time - write the pin names on the connector. > > > > > > -- > > http://www.piclist.com PIC/SX FAQ & list archive > > View/change your membership options at > > http://mailman.mit.edu/mailman/listinfo/piclist > > > > > > -- > unPIC -- The PIC Disassembler > http://unpic.sourceforge.net > -- > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > -- Shawn Wilton (b9 Systems) http://b9Systems.com <- New web page -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist