Bug #8969
closedRadioddity GA-510
0%
Description
When I try to “Download from Radio”, the Port is blank. I’ve tried Com1 to Com10, but get “Can’t open port (error 3)”. Please help. Thanks, Bob
Updated by Bernhard Hailer about 3 years ago
- Status changed from New to Feedback
- Model affected changed from GA-510 to Radioddity GA-510
This isn't a Chirp bug, nor a Feature or New Model request.
This is a question best asked on the "mailing list":http://intrepid.danplanet.com/mailman/listinfo/chirp_users.
You might get (much) quicker feedback there.
Having said that: it's likely a cable / driver / connector issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
If there's no solution to be found in any of them, please read: How To Report Issues and provide a debug log. Thank you!
Windows notes: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php
MacOS notes: this OS is apparently very picky about USB to Serial cables. From what I heard, only (genuine) FTDI-based cables can be made work.
On older MacOS versions, you must have the KK7DS Python runtime for Mac OSX installed. I don't have information yet what to do on new versions (like Big Sur).
Big Sur is a problem on its own, because basically all USB drivers need to be rewritten. FTDI is still working on it.
Also see MacOS Tips!
Linux notes: Linux generally is quite good with USB to Serial converter drivers. The most likely cause for grief is a connector which doesn't provide good electrical contact.
Bluetooth notes: connections often suffer from timing issues, please try a cable instead.
Updated by Bernhard Hailer about 3 years ago
Bob, please let us know what you find. Thanks!
Updated by Jim Unroe about 3 years ago
Hi Bob,
Most likely you are selecting the wrong port and/or you don't have a compatible device driver correctly installed.
Using Windows you don't need to "try" all the ports. The Windows Device Manager application allow you to just watch for the new entry that appears when you plug the USB end of the programming cable into the computer. The added COM port is the one and only port you need to choose. Anything that was present prior to that is irrelevant.
If you are using a programming cable with a Prolific chip, then the device driver that is automatically installed by Windows is not compatible. You must download, install and select the older Prolific v3.2.0.0 driver.
If you are using a programming cable with a WCH CH-340 chip, I have recently seen where Windows erroneously uses the Prolific driver. In that case you have to download the driver from the chip vendor and install it.
I used to advise against it, but I am more and more inclined to recommend that Windows users just go ahead and manually install the various common programming drivers (FTDI, WCH, Silicon Labs and Prolific) before plugging in their programming cable for the first time. For the links to all the drivers and instructions for the Prolific driver installation, visit the "miklor.com":https://www.miklor.com/COM/UV_Drivers.php website.
Jim KC9HI
Updated by Bernhard Hailer almost 3 years ago
- Status changed from Feedback to Closed
No more traffic on this ticket.