Project

General

Profile

Actions

Bug #11691

open

Re: fimding the port #

Added by Steven Eizenberg 3 days ago. Updated 1 day ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/18/2024
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
Yaesu FT-65R HT
Platform:
Windows
Debug Log:
I read the instructions above:
Yes

Description

For a Yeasu FT- 65R HT. I can program the HT manually. But not via the cable to my laptop. I can't find the port #. "See the screen capture bellow in the DropBpx link

https://www.dropbox.com/scl/fi/kbi0nm0sn3htohetoj0le/chirp.jpg?rlkey=b604hutm74hxzw99f7crftraq&st=2blevfxe&dl=0

How do I find the port #
How do I fix this problem?


Files

chirp.jpg (7.32 KB) chirp.jpg Steven Eizenberg, 11/18/2024 12:19 AM
Actions #1

Updated by Steven Eizenberg 3 days ago

BTW this is for Windows 10 64bit

Actions #2

Updated by Dan Smith 3 days ago

Per the IssueInstructions you indicated you read, please include a debug log by following these instructions: How_To_Report_Issues.

Actions #3

Updated by Jim Unroe 1 day ago

The screen capture provided seems to indicate that you may be running an unsupported version of CHIRP. Ignoring that for the time being, no port number when running Windows is usually an indication that a compatible device driver is not installed. This happens when the programming cable was manufactured with a Prolific type USB-to-Serial chip and Windows is using the a recent device driver provided to them by the chip manufacturer. Supplying the debug log as instructed by How_To_Report_Issues should help to confirm this. The workaround most Prolific chip based in Windows is to download, install and manually select the older, but compatible, Prolific v3.2.0.0 device driver. A link to the driver and instructions for manually selecting it are available here.

Actions

Also available in: Atom PDF