Project

General

Profile

Actions

Bug #6537

closed

cannot find path

Added by Richard de Castro about 5 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/03/2019
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng UV-5R
Platform:
Windows
Debug Log:
I read the instructions above:

Description

UV5R radio, latest version of chirp (Daily 20190303) Windows 10 (two separate machines/installs), get this error message. Tried deleting prolific driver and replace, tried deleting chirp.config

"An error has occurred. Could not open port (error 3) The system cannot find the path specified.

No port shows up in chirp when trying to read from radio.

Findcomport doesn't find any com port.

debug log:

2019-03-03 12:11:12,638] chirp.ui.mainapp - INFO: Skipping existing stock config
[2019-03-03 12:11:12,638] chirp.ui.reporting - DEBUG: Checking for updates
[2019-03-03 12:11:12,825] chirp.ui.reporting - DEBUG: Server reports version daily-20190303 is latest
[2019-03-03 12:11:39,201] chirp.ui.mainapp - DEBUG: User selected Baofeng UV-5R on port
[2019-03-03 12:11:39,201] chirp.ui.reporting - DEBUG: Reporting exception
[2019-03-03 12:11:39,201] chirp.ui.inputdialog - ERROR: --- Exception Dialog: could not open port : [Error 3] The system cannot find the path specified. ---
[2019-03-03 12:11:39,201] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirp\ui\mainapp.pyo", line 731, in do_download
File "serial\serialwin32.pyo", line 30, in init
File "serial\serialutil.pyo", line 260, in init
File "serial\serialwin32.pyo", line 56, in open
SerialException: could not open port : [Error 3] The system cannot find the path specified.

[2019-03-03 12:11:39,201] chirp.ui.inputdialog - ERROR: ----------------------------

Thanks!

Actions #1

Updated by Jim Unroe about 5 years ago

  • Status changed from New to Feedback

You are most likely selecting the wrong COM port (perhaps your programming cable got assigned a different port number) or you have a programming cable with a Prolific type USB-to-TTL chip and you need to select the Prolific V3.2.0.0 device driver again.

Jim KC9HI

Actions #2

Updated by Bernhard Hailer almost 4 years ago

  • Status changed from Feedback to Closed
  • Model affected changed from (All models) to Baofeng UV-5R

No more feedback by submitter.

Actions

Also available in: Atom PDF