CHIRP

Not compatible in what way? With a properly configured programming cable it should work by choosing Vendor: Baofeng and Model: UV-5R

Jim KC9HI

Giorgio,

The Radio did not respond message could be caused by several things.

1. The most common is an incompatible device driver is installed. This usually happens when the chip in the programming cable is detected by Windows as a Prolific type chip. Nearly all Prolific type chips in programming cables are unauthorized copies. The device driver automatically installed by Windows, when a Prolific type chip is detected, is intentionally incompatible with unauthorized chip copies. Which chip it is can be determined in most cases by using the Windows Device Manager application. A workaround is to download, install and select the older Prolific v3.2.0.0 device driver. How to do this is provided on the Miklor Drivers & USB Cables":https://www.miklor.com/COM/UV_Drivers.php page. Another workaround is to get a programming cable manufactured with a different USB-to-Serial chip (FTDI, Silicon Labs, WCH, etc).

2. There is a poor or incomplete connection between the 2-pin plug of the programming cable and the socket of the radio. Sometimes there is interference between the case and the plastic shell of the plug that cause an interference that prevents the pins of the plug from being fully inserted. When this is the cause, sometimes it is possible to trim some plastic from the plug's shell to reduce or eliminate the interference. The "Miklor Radio did not respond FAQ":https://www.miklor.com/COM/UV_ErrorMess.php#error1 page covers this.

3. The wrong COM port is being selected. This may likely your issue since you are selecting COM1. On my desktop computers COM1 is assigned to the serial port on the motherboard. Nothing is ever connected to it. So even though it shows up in CHIRP, I would never choose it to program any radios. As mentioned earlier, you would use the Windows Device Manager application to determine exactly which COM port number as been assigned to your programming cables (depending on the chip inside, each programming cable may be assigned its own COM port number).

4. The wrong model is being selected. This would result in sending the wrong "magic" string to the radio. But this is not the cause in your situation. After downloading and testing the Radioddity factory programming software for the UV-5R EX, the "magic" sent by this software is the same "magic" sent my CHIRP when the Vendor: Baofeng / Model: UV-5R is selected.

5. Not as common, and unlikely since you are trying 3 programming cables, is a defective programming cable.

To show more clearly show that this is a cable/driver/connection issue, you can try to download from the radio without the programming cable connected to the radio. The same Radio did not respond error will be the result. Another way to show this would be to try the Baofeng factory programming software, which is available from links on the "Miklor UV-5R Factory & VIP Software":https://www.miklor.com/uv5r/UV5R-Software.php page. The cloning process will generate a Fail connect with transceiver error due to the same cable/driver/connection issue.

Jim KC9HI

Jim Unroe wrote:

Giorgio,

The Radio did not respond message could be caused by several things.

1. The most common is an incompatible device driver is installed. This usually happens when the chip in the programming cable is detected by Windows as a Prolific type chip. Nearly all Prolific type chips in programming cables are unauthorized copies. The device driver automatically installed by Windows, when a Prolific type chip is detected, is intentionally incompatible with unauthorized chip copies. Which chip it is can be determined in most cases by using the Windows Device Manager application. A workaround is to download, install and select the older Prolific v3.2.0.0 device driver. How to do this is provided on the Miklor Drivers & USB Cables":https://www.miklor.com/COM/UV_Drivers.php page. Another workaround is to get a programming cable manufactured with a different USB-to-Serial chip (FTDI, Silicon Labs, WCH, etc).

2. There is a poor or incomplete connection between the 2-pin plug of the programming cable and the socket of the radio. Sometimes there is interference between the case and the plastic shell of the plug that cause an interference that prevents the pins of the plug from being fully inserted. When this is the cause, sometimes it is possible to trim some plastic from the plug's shell to reduce or eliminate the interference. The "Miklor Radio did not respond FAQ":https://www.miklor.com/COM/UV_ErrorMess.php#error1 page covers this.

3. The wrong COM port is being selected. This may likely your issue since you are selecting COM1. On my desktop computers COM1 is assigned to the serial port on the motherboard. Nothing is ever connected to it. So even though it shows up in CHIRP, I would never choose it to program any radios. As mentioned earlier, you would use the Windows Device Manager application to determine exactly which COM port number as been assigned to your programming cables (depending on the chip inside, each programming cable may be assigned its own COM port number).

4. The wrong model is being selected. This would result in sending the wrong "magic" string to the radio. But this is not the cause in your situation. After downloading and testing the Radioddity factory programming software for the UV-5R EX, the "magic" sent by this software is the same "magic" sent my CHIRP when the Vendor: Baofeng / Model: UV-5R is selected.

5. Not as common, and unlikely since you are trying 3 programming cables, is a defective programming cable.

To show more clearly show that this is a cable/driver/connection issue, you can try to download from the radio without the programming cable connected to the radio. The same Radio did not respond error will be the result. Another way to show this would be to try the Baofeng factory programming software, which is available from links on the "Miklor UV-5R Factory & VIP Software":https://www.miklor.com/uv5r/UV5R-Software.php page. The cloning process will generate a Fail connect with transceiver error due to the same cable/driver/connection issue.

Jim KC9HI

Problem found. it was a problem with the baofeng connector too short. I have removed plastic from the connector or now it works perfectly. thank you all