Project

General

Profile

Actions

Bug #7547

closed

Alinco DR-135T Mkiii Returns No Response

Added by Brian Hickmann over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/11/2020
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Alinco DR-x35T MKIII
Platform:
All
Debug Log:
I read the instructions above:

Description

I am running CHIRP daily-20200107 on Ubuntu and attempting to program an Alinco DR-135T Mkiii using a bluemax49ers' FTDI USB programming cable plugged into the front data port of the radio. However, despite trying several different methods, I always get the same error: No Response from Radio. I have tried the download from the radio with three different start conditions, and I only see a response on the radio screen in one of the three modes. In the debug logs for all three start conditions, there is just a blank response from the radio.

1.) Radio in normal operating mode - debug.log.radio_not_in_clone_mode
No change in radio screen after attempt

2.) Radio in clone "send" mode, as indicated in the radio manual - debug.log.radio_in_clone_send_mode
Radio screen reads "SD 000" before and after attempt to download from the radio

3.) Radio in clone mode - debug.log.radio_in_clone_mode
Radio screen reads "CLONE" before the attempt, and reads "RD 000" after the attempt, which indicates that there was SOME response to the commands send over the serial connection.

Any help/ideas on what might be the problem would be greatly appreciated!

Thanks,
Brian
KI7MDF


Files

debug.log.radio_not_in_clone_mode (24.8 KB) debug.log.radio_not_in_clone_mode 1.) Radio in normal operating mode Brian Hickmann, 01/11/2020 09:57 PM
debug.log.radio_in_clone_mode (24.8 KB) debug.log.radio_in_clone_mode 3.) Radio in clone mode Brian Hickmann, 01/11/2020 09:57 PM
debug.log.radio_in_clone_send_mode (24.7 KB) debug.log.radio_in_clone_send_mode 2.) Radio in clone "send" mode Brian Hickmann, 01/11/2020 09:57 PM

Related issues

Related to Bug #5901: No response from radio error - Alinco DR-235Closed06/24/2018

Actions
Actions #1

Updated by Bernhard Hailer over 4 years ago

  • Status changed from New to Feedback
  • Model affected changed from (All models) to Alinco DR-x35T MKIII
  • Platform changed from Linux to All

A few years ago I ran into the very same problem with this family of radios (Alinco DR-135/235/435T MKIII) and a cable from BlueMax49ers. This company makes excellent cables with genuine FTDI chips, and they provide excellent customer service - all my cables are from them, and I highly recommend them.

I worked with BlueMax49ers on a solution. They were very responsive. Neither I nor Mark of BlueMax49ers were able to find out why these particular radios wouldn't cooperate with the FTDI cable, but we found that the cable definitely was the culprit: they even sent a replacement, which didn't work either. Finally, the company provided a (genuine) Prolific USB to Serial converter for testing - and it worked right out of the box! So the solution for these Alincos is to use Prolific, not FTDI. We don't know why.

You should contact them!

Actions #2

Updated by Brian Hickmann about 4 years ago

Ok I finally got the non-FTDI cable and it worked great! Thanks for the information.

Actions #3

Updated by Bernhard Hailer about 4 years ago

  • Status changed from Feedback to Closed

Suggested solution worked.

Actions

Also available in: Atom PDF