Project

General

Profile

Actions

Bug #4611

closed

Chirp wont finish clone

Added by Shawn Loucks almost 8 years ago. Updated about 4 years ago.

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

0%

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

Description

I can clone from my radio to chirp, but I can not clone from chirp to the radio.

After entering the data, and I try the clone process, the clone freezes half way. I have tried to leave it for an hour, and it doesn't move. I downloaded the most recent chirp, the cord is plugged in all the way into the radio, radio is on.

Radio is a UV-5R
I am using windows 10
64 bit


Files

debug.log (31.5 KB) debug.log Debug log from #4649 Bernhard Hailer, 04/08/2020 12:38 PM

Related issues 1 (0 open1 closed)

Related to Bug #4649: Chirp stalls when cloningClosed03/19/2017

Actions
Actions #1

Updated by Jim Unroe almost 8 years ago

  • Status changed from New to Feedback

Is it programming cable with a Prolific chip? If yes, then have you downgraded the device driver to v3.2.0.0 (the auto installed device driver is incompatible with counterfeit chips)?

"Drivers & USB Cables":http://www.miklor.com/COM/UV_Drivers.php

Jim KC9HI

Actions #2

Updated by Shawn Loucks almost 8 years ago

Unsure how to check to see if it has a Prolific chip. Assuming it didn't I follow the instructions on downgrading the driver device yesterday. It gets about 1/2 and just pauses. After letting it pause for a hour or so. I unplugged the cable, looked at the radio and the programmed frequency's and names were in the there without the clone finishing.

Actions #3

Updated by Jim Unroe almost 8 years ago

Step 11 in the link above shows you how to find the Driver tab in Device Manager which shows you the chip vendor and installed driver version.

Jim KC9HI

Actions #4

Updated by Jim Unroe almost 8 years ago

Confirm that you have a Prolific chip and if you do confirm that you have the v3.2.0.0 device driver installed. If confirmed and the failed upload still happens, then attach a debug log of the failed upload.

Jim

Actions #5

Updated by Shawn Loucks almost 8 years ago

After looking at step 11 on the site, it is a prolific. In the driver tap is says its driver version 3.8.3.0. I did have to change the driver to v3.2.0.0 to read on chip, and that's what I was using when the clone pauses.

Actions #6

Updated by Jim Unroe almost 8 years ago

Start CHIRP, do an upload that fails, close CHIRP and attach the debug.log here.

Detail for locating the debug.log file are on the "How to report issues":http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues page.

Jim

Actions #7

Updated by Shawn Loucks over 7 years ago

I added debug.log file in the issue page

Actions #8

Updated by Jim Unroe over 7 years ago

Where is it?

Jim

Actions #10

Updated by Bernhard Hailer over 4 years ago

  • File debug.log debug.log added
  • Target version set to chirp-legacy
  • Chirp Version changed from 0.4.0 to daily

I closed #4649 and copied the debug log here.

Actions #11

Updated by Bernhard Hailer over 4 years ago

  • Model affected changed from UV-5R to Baofeng UV-5R

Has this been resolved?
The log does not say much, it probably should be collected again in a fresh attempt.

Actions #12

Updated by Bernhard Hailer about 4 years ago

  • Status changed from Feedback to Closed

No more feedback.

Actions

Also available in: Atom PDF