To add on to this,
Try communicating with the radio using the OEM software.
If you are able to successfully communicate with radio using the oem software, but are unable to using chirp, then it could be a chirp issue.

If you are unable to communicate with your radio using oem software, then it is certainly not a chirp issue, but perhaps a cable, driver, or radio issue.

-J

From: Jim Unroe <rock.unroe@gmail.com>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Sent: Tuesday, January 7, 2014 10:33 AM
Subject: Re: [chirp_users] Baofeng UV-5R programming

On Tue, Jan 7, 2014 at 11:06 AM, kdufour . <kdufour@gmail.com> wrote:
am running 2.0.2.1 for XP



If you are running this driver on XP and getting the "radio did not respond" error, then there are two possibilities. Either the programming cable is not fully plugged into the radio (the most likely cause) or the programming cable is defective (possible but not as likely).

Many users swear that their programming cable is fully plugged in but are amazed when they give it a wiggle and a firm push and notice it go in just a little further. See the "Errors and Error Messages" page on the miklor.com website.


Jim KC9HI 

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users