[chirp_users] Another way Chirp can be tripped up by the OS

[Stephen Hersey]

I've just started using Chirp with a Baofeng UV-5R and a USB serial adapter
that Amazon claims is from Baofeng. The adapter has a genuine Prolific chip
(or a darn good counterfeit), and Windows 7 Pro 64-bit recognizes it as a
serial port; in addition, I can connect TxD to RxD at the radio plugs, open
PuTTY, and see looped-back characters I have typed on the console. So far,
so great.

However, neither Chirp nor baoclone could open the serial port the USB
adapter was assigned to: COM19. Hmmm, 19? Sounds way high for a serial port
enumeration. I reassigned the USB adapter to the vacant COM2, and hey
presto! Both utilities are able to talk to the radio.

Sooo, beware of high-numbered COM ports.

Incidentally, is it normal for the UV-5R to key up when the serial cable is
present? I'm going to make a practice of always having a dummy load
connected when programming this radio.

Regards,
Steve

-- 
Steve Hersey N1XNX
n1xnxham at gmail.com
-----
Each of us has strengths and talents that others don't. Whether innate or
learned, these are gifts -- and a gift not shared is a sad and lonely
thing. Using our gifts for the benefit of all is an ethical obligation for
every intelligent being. (The magic only works if you pass it on!)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20140327/b893d1f5/attachment.html