Project

General

Profile

Actions

Bug #2277

open

download from ID-880H results in "unexpected response from radio"

Added by Rob Locher almost 10 years ago. Updated over 4 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/31/2015
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Icom ID-880H
Platform:
Linux
Debug Log:
I read the instructions above:

Description

When I try to "Download from Radio" with my ID-880H, I get an error almost immediately: "Failed to communicate with the radio: Unexpected response from radio". I'm running Ubuntu 14.04 and the 2015-01-23 daily build of Chirp. I use the same USB-to-serial converter to troubleshoot hardware devices regularly using minicom, so I'm confident it's not a permissions problem. I'm able to use the Icom software to program the radio (after booting the netbook into Windows, ugh), so I don't think it's an issue with the radio or the cable. I checked to see that I have the latest firmware for the radio; there haven't been any updates.

The daily build version in a separate folder didn't create a debug.log, so I attached the debug.log created by version 0.4.0 from the PPA. The bug seems to happen with both versions of CHIRP.

P.S. Thanks for CHIRP! What wonderful software!


Files

debug.log (4.96 KB) debug.log Rob Locher, 01/31/2015 06:14 PM

Related issues 2 (0 open2 closed)

Has duplicate Bug #6343: Failed to communicate, unexpected response - Icom ID-880HClosed01/02/2019

Actions
Has duplicate Bug #6673: Traceback while trying to clone Icom ID-800HClosed04/08/2019

Actions
Actions #1

Updated by Tom Hayward almost 8 years ago

  • Status changed from New to Feedback

Just stumbled across this report and read the log. The radio didn't respond at all when Chirp tried to read it. Like if it was turned off, cable not connected, or you selected the wrong serial port. Not sure what could be done on Chirp's end to fix this.

Actions #2

Updated by Bernhard Hailer over 4 years ago

Have you been able to resolve this on your own since you submitted this?
Really looks like a problem with your cable.

Actions #3

Updated by Bernhard Hailer over 4 years ago

  • Status changed from Feedback to Closed

Reopening; perhaps this helps:
Some Icom radios are known to deny cooperation with FTDI cables (even genuine ones). Please try a cable with a genuine Prolific chip.
Unfortunately cables with fake "Prolific" chips make the vast majority of cables on the market; genuine Prolific cables are on the more expensive side.
Please let us know whether this hint helps!

Actions #4

Updated by Bernhard Hailer over 4 years ago

  • Status changed from Closed to Feedback
Actions

Also available in: Atom PDF