Bug #6343

Failed to communicate, unexpected response - Icom ID-880H

Added by Jeff Pyle over 1 year ago. Updated about 1 month ago.

Status:Closed Start date:01/02/2019
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:Icom ID-880H

Description

On Windows 7 and Arch Linux I receive "Failed to communicate with the radio: Unexpected response from the radio" when trying to read an Icom ID-880H, displayed nearly immediately after I start the read. Linux is daily 20181018 installed from the AUR, and Windows is a fresh download and install of daily 20180102.

On Linux I see the following on the console at read-time:

ERROR: -- Exception: --
ERROR: Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/chirp/ui/clone.py", line 256, in run
self.__radio.sync_in()
File "/usr/lib/python2.7/site-packages/chirp/drivers/icf.py", line 620, in sync_in
self._mmap = clone_from_radio(self)
File "/usr/lib/python2.7/site-packages/chirp/drivers/icf.py", line 290, in clone_from_radio
raise errors.RadioError("Failed to communicate with the radio: %s" % e)
RadioError: Failed to communicate with the radio: Unexpected response from radio

ERROR: ----------------
ERROR: Clone failed: Failed to communicate with the radio: Unexpected response from radio
ERROR: --- Exception Dialog: Failed to communicate with the radio: Unexpected response from radio ---
ERROR: None

ERROR: ----------------------------

On Windows, the Icom software works fine.


Related issues

duplicates Bug #2277: download from ID-880H results in "unexpected response fro... Feedback 01/31/2015

History

Updated by Bernhard Hailer about 1 month ago

  • Status changed from New to Feedback
  • Target version set to chirp-daily

Have you been able to resolve this on your own since you submitted this?
Have you tried with a recent version since you submitted this?

This could be a cable / driver / connector issue. Please refer to these Wiki articles:
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.

Updated by Bernhard Hailer about 1 month ago

  • Status changed from Feedback to Closed

Duplicates #2277. Please follow and post there. Thanks!

Also available in: Atom PDF