Bug #9885
closedCHIRP error "radio not responding" (Bug #9187) Baofeng UV-5G
0%
Description
Attempting to clone UV-5G into :
CHIRP Release: CHIRP daily 20220515 (for Windows)
Radio: Baofeng UV-5G (GRMS) 715-100-UV5X
Cable: BaofengTech PC04 FTDI Cable single pin
Ports (COM & LPT): USB Serial Port (COM5)
CHIRP command: Download from Radio
settings: COM5 / vendor=Radioddity / model=UV-5G
Message: cloning in process
Error: radio did not respond
Bug #9187 - indicates the above has been resolved
Files
| COM Port Selected Doesn_t Exist.png (6.26 KB) COM Port Selected Doesn_t Exist.png | Error - Selected port (COM3) does not exist. | ||
| FTDI FT232R.png (28.6 KB) FTDI FT232R.png | Device Manager - FTDI programming cable assigned COM7. |
Updated by Jim Unroe almost 2 years ago
- Status changed from New to Feedback
Most likely you don't have a completed connection between the programming cable and the speaker/mic socket of the radio. For example, leave the cable unplugged from the radio and attempt a download, the same error message will appear. Try putting some pressure on the plug during the cloning process.
Once you get a working connection, CHIRP should work fine for you.
Jim KC9HI
Updated by Jim Unroe almost 2 years ago
Also, is the PC04 a typo? The PC04 programming cable is for mobile radios. The PC04 programming cable won't work for UV-5R like radios such as the UV-5G. For your radio you need a PC03 programming cable.
Jim KC9HI
Updated by John Lopez almost 2 years ago
My bad on PC04.
I tried a MIRKIT Model 3 Premium RED (2 prong) as well.
Error now: could not open port COM5 [Error 2]
The system cannot find the file specified.
Updated by Jim Unroe almost 2 years ago
- File COM Port Selected Doesn_t Exist.png COM Port Selected Doesn_t Exist.png added
- File FTDI FT232R.png FTDI FT232R.png added
John Lopez wrote:
My bad on PC04.
I tried a MIRKIT Model 3 Premium RED (2 prong) as well.
Error now: could not open port COM5 [Error 2]
The system cannot find the file specified.
Typically an [Error 2] indicates that the COMx port selected (COM5 in your case) does not exist. When you plug in a different programming cable that has a chip from a different chip vendor or it is an FTDI type chip, a different COMx port is assigned to it. CHIRP always remembers and selects the previously used COMx port number no matter if it is present or not. You must change the Port: selection to the correct COMx port yourself. The new COMx port will usually be the bottom one in the drop down list. The top one is the previously used COMx port. Another way to determine the which COMx port has been assigned to your programming cable is to use the Device Manager application.
Jim KC9HI
Updated by Bernhard Hailer almost 2 years ago
- Target version deleted (
chirp-legacy) - Model affected changed from UV-5G to Baofeng UV-5G
Did Jim's input help?
Updated by Bernhard Hailer about 1 year ago
- Status changed from Feedback to Closed
No more feedback by submitter.