New Model #5435


ID-51A Plus (Anniversary edition)

Added by Matt Wallace over 6 years ago. Updated almost 4 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Equipment Loan/Gift Offered:
I read the instructions above:


N.B.: My understanding is that the ID-51A Anniversary edition is equivalence classed with the ID-51A Plus, if this is incorrect and the anniversary edition is not supported please close the issue with my apologies.

I'm receiving the error "Failed to communicate with the radio: Unexpected response from radio" when downloading from the radio.

The following stack trace is presented:
[2017-12-10 16:07:22,383] chirp.ui.common - ERROR: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/", line 249, in run
File "/usr/lib/python2.7/dist-packages/chirp/drivers/", line 619, in sync_in
self._mmap = clone_from_radio(self)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/", line 325, 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

Although I'm not familiar with the code, I think the exception is being thrown from in get_model_data.

I am using an RT Systems branded cable but I have created a udev rule to ensure that the ftdi_sio driver is used:
SUBSYSTEM=="tty", ATTRS{idVendor}=="2100", ATTRS{idProduct}=="9e5f", ATTRS{serial}=="RTMFF71", SYMLINK+="Radio", RUN+="/sbin/modprobe -q ftdi_sio vendor=0x2100 product=0x9e5f"

Verified driver is loaded using usb-devices:
T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 7 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=2100 ProdID=9e5f Rev=10.00
S: Manufacturer=RT Systems
S: Product=RTS05 Radio Cable
S: SerialNumber=RTMFF71
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ftdi_sio


debug.log (21.2 KB) debug.log Matt Wallace, 12/10/2017 04:16 PM
Actions #1

Updated by Bernhard Hailer almost 4 years ago

  • Tracker changed from Bug to New Model
  • Target version set to chirp-legacy
  • Chirp Version changed from 0.4.0 to daily
  • Equipment Loan/Gift Offered set to No
Actions #2

Updated by Bernhard Hailer almost 4 years ago

  • Status changed from New to Feedback

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.
Let us know whether this helps, please!


Also available in: Atom PDF