Bug #5901
closedNo response from radio error - Alinco DR-235
0%
Description
Trying to download data from radio I got the error message "No response from radio".
Searching the Chirp website, I found that others users had the same issue in the past. I have tried all things they did, but with no success.
Monitoring the serial port activity I see Chirp sending "DR235" string three times and next the last string "AL~F0000R". The radio echo all sent strings from Chirp.
I am not using a USB/Serial converter. My PC has a native serial port.
Attached to this message is the debug.log file.
Files
Related issues
Updated by Steve Magnuson over 5 years ago
Hello,
I am having the same problem with a new DR-235T MkIII. I'm using a BlueMax49ers FTDI USB cable designed for this radio. It uses the FTDI FT232R chip. Debug file attached.
This is on Windows 10 Version 1803. I also tried it on Mint Linux (latest) with the same cable. Debug.log looks the same: Empty strings from the radio.
I tried someone's suggestion of using a speed other than 9600 in the Device Manager serial port settings. Same result. I tried 4800, 19200, 57600, 115200. All No parity, 8 data and 1 stop bits. No flow control.
Thanks,
Steve
Thanks,
Steve
Updated by Luiz Tresso over 5 years ago
The error message has changed after the last update.
Now Chirp shows "Unexpected Response From Radio".
Monitoring serial communication between radio and PC, I see Chirp sending the string "DR235" three times and the string "AL~F0000R" one time. The radio answers echoing the strings.
The debug file is attached.
Thanks
Luiz
Updated by Luiz Tresso over 5 years ago
I have tried on Linux and it's working. The version tested is 20180906.
On Windows still got the issue.
Updated by Steve Magnuson over 5 years ago
I can't get 20180906 to work on Windows, Mint Linux or Raspbian Stretch. All fail with the same "No response from radio" message. I'll have an opportunity to use a friend's RT Systems software and cable on Tuesday and will report back. I've attached the debug from Raspbian Stretch. I hope I don't have a faulty radio.
Steve
Updated by Steve Magnuson over 5 years ago
UPDATE: The RT Systems cable works fine with my DR-235TMkIII radio and CHIRP. Oddly, the cable that doesn't work on my radio DOES work on another DR-235TMkIII. I emailed Alinco and got this response:
_Subject: DR-235TMKIII Data Port
Hello,
I have a new DR-235TMKIII serial number M005xxx. I cannot get a USB Serial cable (BlueMax49ers FTDI cable, designed to work with the DR-135,-235,-435 radios) to work with CHIRP on this radio, although the same cable and software and PC works fine on an older DR-235TMKIII (serial number M002xxx).
An RT Systems USB cable works fine on both my new radio and the older radio with both CHIRP and RT Systems software.
Has the front panel programming ('data') port interface changed on this radio between serial number M002xxx and M005xxx such that it would make some cables work and others not work?
Thanks,
Steve
AG7GN_
Alinco replied with:
Hello Steve,
Thank You for contacting REMTronix.
According to Alinco Japan, nothing has been changed or modified from the two back of Serial number you provided.
We has heard compatibility issues with some 3rd part cables sold on
eBay and Amazon. Unfortunately we cannot support Its compatibilities with Alinco Radios as Alinco does sell ERW-7 cable that are fully compatible across almost all of its Radios.
.
.
.
Indeed I would recommend RT Systems cable as well. However one thing we noticed is that their cable will not allow Firmware
Updates on model DR-735. Otherwise their cable works across all of Alinco's Radios very well. Hopefully its Driver releated.
Updated by Bernhard Hailer over 4 years ago
- Subject changed from No response from radio error - DR235 to No response from radio error - Alinco DR-235
- Status changed from New to Feedback
- Chirp Version changed from 0.4.0 to daily
- Model affected changed from DR235 to Alinco DR-235
The original post was about a serial cable plugged into a native serial port.
For USB to serial converters, please also see my comment in #7547.
Updated by Bernhard Hailer almost 4 years ago
Luiz, have you found a solution for your problem?
The only thing coming to my mind is that the serial port perhaps isn't properly set up when you use Windows.
Updated by Bernhard Hailer over 3 years ago
- Status changed from Feedback to Closed
No more feedback by submitter.