Project

General

Profile

Actions

Bug #9930

closed

Com Port Issue

Added by Michael Harrell almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
06/28/2022
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Windows serial
Platform:
Windows
Debug Log:
I read the instructions above:

Description

The Com Port options available for me to use in Chirp are COM1 and COM4. The Cable is COM3. Is there a config file I can edit on Chirp to use COM3?


Files

Actions #1

Updated by Michael Harrell almost 3 years ago

Update: When Chirp loads it gives me 2 options. COM1 and COM4. I can manual edit to COM3, but when I try to download from the radio I get the following message.

could not open port COM3: [Error 433] A device which does not exist was specified.

I have attached a screen capture of my device manager to show that the USB to Serial is functioning on COM3.

Actions #2

Updated by Jim Unroe almost 3 years ago

  • Status changed from New to Incomplete

Michael Harrell wrote:

Update: When Chirp loads it gives me 2 options. COM1 and COM4. I can manual edit to COM3, but when I try to download from the radio I get the following message.

could not open port COM3: [Error 433] A device which does not exist was specified.

I have attached a screen capture of my device manager to show that the USB to Serial is functioning on COM3.

What is the version of the Prolifc driver installed in your computer? Have you done the required manual downloading, installation and selection of the older Prolific v3.2.0.0 device driver? In virtually every case where a Prolific chip based programming cable is use with Windows, the driver that is automatically installed is incompatible. The Prolific v3.2.0.0 (v2.0.2.1 for Windows XP) driver is required. See the Miklor "Cables and Drivers":https://www.miklor.com/COM/UV_Drivers.php page.

Jim KC9HI

Actions #3

Updated by Michael Harrell almost 3 years ago

The version I am running is V3.9 and I am running Windows 11. When using the v3.2.0.0 driver, the message in the device manager states that it is not supported.

Updated by Jim Unroe almost 3 years ago

Michael Harrell wrote:

The version I am running is V3.9 and I am running Windows 11. When using the v3.2.0.0 driver, the message in the device manager states that it is not supported.

In addition to installing the v3.2.0.0 driver, you have to go into Device Manager and choose the driver version that you want Windows 11 to use. You seem to have missed the steps in the directions where you select the driver. Assuming the Prolific v3.2.0.0 driver has been installed, perform the following steps...

Note: The attached screen captures are from Windows 10 so the "not supported/phased out" message is slightly different from what you will see for Windows 11 but the process to select the driver is exactly the same.

1 Double-click the entry for your programming cable
2 Click the Driver tab
3 Click the [Update Driver] button
4 Click Browse my computer for drivers
5 Click Let me pick from a list of available drivers on my computer
6 Choose the Prolific USB-to-Serial Comm Port Version: 3.2.0.0 [7/31/2007] and click the [Next] button
7 Click the [Close] button

Note: Every once-in-awhile Windows 11 Update will decide that you need to be using the latest device driver and your programming cable will no longer be recognized and stop working. Most of the time you can just repeat steps 1 through 7 to select the older working driver. But there are times that Windows 11 Update will remove the v3.2.0.0 driver. When that is the case you will have to install the v3.2.0.0 driver again and then repeat steps 1 through 7.

Jim KC9HI

Actions #5

Updated by Michael Harrell almost 3 years ago

Ok, had to reboot my computer. There was a Windows update that was pending. For some reason I had to let that complete and then update the driver. Now it is working.

Actions #6

Updated by Jim Unroe almost 3 years ago

Michael Harrell wrote:

Ok, had to reboot my computer. There was a Windows update that was pending. For some reason I had to let that complete and then update the driver. Now it is working.

Good catch. I am glad to see that you have it working.

Jim KC9HI

Actions #7

Updated by Bernhard Hailer over 2 years ago

  • Status changed from Incomplete to Closed
  • Model affected changed from (All models) to Windows serial

Resolved.

Actions

Also available in: Atom PDF