Bug #9023
closedAn error has occurred. Could not open port (error 3) The system cannot find the path specified.
0%
Description
I am trying to sync a Baofeng UV-5R+ radio and there are no ports to choose from.
From looking at this article, (https://www.usb-drivers.org/ft232r-usb-uart-driver.html#google_vignette)I've tried searching legacy hardware through the device manager on my computer, but there are no named COM ports that come up. See screenshot attached
I've tried copying and pasting and manually typing in the port for where I find the cable I'm using, and FT-232R but still not working.
I've also tried putting in the locations of the USB ports (see screenshot attached).
I've tried just typing in COM1, COM2, COM3, etc.
Tried putting in BF-F8HP as model number since it says on chirp to use that if I have a UV-5R+
Tried unhooking cable, making sure radio turned all the way up, not on an active channel, etc.
I have a MS-surface pro 5
Files
| Capture2.JPG (149 KB) Capture2.JPG | |||
| Capture.JPG (63.4 KB) Capture.JPG | |||
| Capture3.JPG (47.1 KB) Capture3.JPG |
Updated by Jim Unroe over 3 years ago
- Status changed from New to Feedback
From what it looks like, you don't have a compatible device driver installed for your programming cable. Since CAPTURE.jpg shows an entry for an FT232R USB UART, it would stand to reason that your programming cable has an FTDI type chip inside. This would indicate that you should download and install the latest driver from the FTDI website.
The "miklor.com":https://www.miklor.com/ website has links to most of the more common USB-to-Serial chip vendors, including Future Technology Devices International (FTDI), on their "Drivers and USB Cables":https://www.miklor.com/COM/UV_Drivers.php page.
Jim KC9HI
Updated by Chris Cooper over 3 years ago
I have had the same issue with CHIRP in the past. I ended up manually entering COM4 as the selection and it worked every time.
Updated by Bernhard Hailer over 3 years ago
- Model affected changed from (All models) to Baofeng UV-5R+
Brian, have you been able to resolve your problem? If not, please read: How To Report Issues and provide a debug log. Thank you!
Updated by Bernhard Hailer over 3 years ago
- Status changed from Feedback to Closed
No more feedback by submitter.