Bug #2079

Uploading on IC-V82 hangs at 50%

Added by Jesse Knott over 5 years ago. Updated about 1 month ago.

Status:Feedback Start date:11/26/2014
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:MacOS
Model affected:Icom IC-V82

Description

When I attempt to upload to my V82 the progress bar gets to about 50% and hangs. Checking the About page it says this is version 0.4.1 of Chirp

I have checked the logs and there are no errors reported there, and no error dialogues are presented at any point in the process.

I have tried doing a simple download then upload with the same results.

Steps to reproduce.
Launch Cirp
Connect cable to computer
Connect radio to cable
Power on Radio
Click "Download" from the radio menu
Click "Upload" from the radio menu

I am running the current driver from Prolific and my cable appears to be a genuine Prolific chip.
OS Mac OS10.10.1 Yosemite on a Macbook Pro

MacBook Pro.spx - HW Configuration for the laptop (4.1 MB) Jesse Knott, 11/26/2014 06:33 pm

debug.log - Copy of debug.log (10.9 kB) Jesse Knott, 11/26/2014 06:33 pm

History

Updated by Jesse Knott over 5 years ago

I have tried and reproduced this issue using a different V82 and using the daily build as well.

Updated by Bernhard Hailer 4 months ago

  • Status changed from New to Feedback
  • Target version set to chirp-daily
  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from IC-v82 to Icom IC-V82

Have you tried with a recent version since you submitted this?
If you haven't, and if you're still having this issue, please provide another debug log - perhaps it will tell us more. Thanks!

Updated by Bernhard Hailer about 1 month ago

Icom radios are a bit finicky with Chirp. They currently don't work well with FTDI.
MacOS is a bit finicky with USB to Serial chips. It more or less likes only FTDI.
So, you're in a catch-22 situation.

Please check whether one of these documents help:
CableGuide
CableGuide FTDI OEM Cables
RTSystemsCablesAndMavericks (if you're running MacOS)
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.
You must have the KK7DS Python runtime for Mac OSX installed.
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 Jesse Knott about 1 month ago

Hello, I'm sorry, I though I had updated this thread. I seem to have tracked down part of the problem at least. I recently tried programming my icoms again on a windows computer and ran into the same issue once again. It turned out that it was due to the radios were the European version. So the firmware is different and will not match any sanity checks the code would be running. If I ensured that it was the American version it worked fine, but the European versions (I have 2 of each) were exhibiting the same issue.
My guess it has to do with the different feature sets on the two radios(European doesn't have the NOAA, and uses a different frequency range) if you have any tools or methods for burning the fw bin I'd be happy to send you the bin for the European version when I get back home again. Or you may already have it, not sure.
At any rate CHIRP works great for all my other radios and the American Icoms.

Thanks!
Jesse

Updated by Bernhard Hailer about 1 month ago

Ah, thanks for the feedback! The European radios probably can be made work with relative ease. First thing you should do is to capture a debug log (and you did that already - thanks) as described in How To Report Issues. The second is to provide an image of the radio in question.

Also available in: Atom PDF

prevent spam