Project

General

Profile

Actions

Bug #254

closed

Alinco DR-235 CHIRP 'Download from Radio' error

Added by Gary Takis almost 12 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
07/21/2012
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Alinco DR-235
Platform:
Windows
Debug Log:
I read the instructions above:

Description

Dan,

Per your recommendation, I did install the latest daily update (chirp-daily-20120720-installer). When I start CHIRP, it boots up fine. I attached an Alinco DR-235 and using an Icom OPC-478 (RS-232 to radio cable) and clicked on Radio > Download from Radio, get a short flash of the 'cloning' popup, then the error window shown in the attached .jpg. Also attached is the debug log.

Admittedly, I do have the CBTI Alinco mobile sofware and I tried it without changing any cables or settings and it worked ok.

I have not tried it with other Alinco DR-series radios that I have.

Gary


Files

debug.log (3.52 KB) debug.log Gary Takis, 07/21/2012 08:30 PM
Error out window 1.jpg (29.5 KB) Error out window 1.jpg Before the daily update was installed Gary Takis, 07/21/2012 08:30 PM
Error out window 2 w-daily update & reboot.jpg (32.6 KB) Error out window 2 w-daily update & reboot.jpg After the daily update was installed Gary Takis, 07/21/2012 08:30 PM
debug.log (3.58 KB) debug.log Gary Takis, 07/30/2012 08:52 AM
Actions #1

Updated by Dan Smith almost 12 years ago

Have you put the radio into clone mode? It has been a while since I've used one of those, but I was thinking you had to put it in clone mode first. I never had access to the real software, so it may have some way of doing that automatically.

Press Func+Call to get it into clone mode, per the manual. Then try the download.

Actions #2

Updated by Dan Smith almost 12 years ago

Hmm, the FAQ page makes it sound like you shouldn't have to do this. It's just been so long with this radio, I don't quite recall. I'll poll the users list for clues.

Actions #3

Updated by Dan Smith almost 12 years ago

A user on the chirp mailing list reports that it is not necessary to move into clone mode first, and that he uses CHIRP with an OPC-478 with no problems.

I have included some more tracing information in the code, which will be included in tomorrow's build. Please grab the new build tomorrow and retry, attaching the new debug log to this ticket. The additional tracing information may help us determine the cause.

Thanks!

Actions #4

Updated by Gary Takis over 11 years ago

Dan,

Finally checked the status of my input. I'll upload the update tonight or tomorrow and give it a try.

No 'clone' mode. It just works with the OPC-478 Icom cable or equivalent.

Thanks...

Gary

Actions #5

Updated by Gary Takis over 11 years ago

Dan... no joy on the 7/24 CHIRP daily update. Still get the same error popup.
Gary

Actions #6

Updated by Dan Smith over 11 years ago

I need the debug log from the later version, which should have additional tracing in it. Please attach after reproducing the issue.

Actions #7

Updated by Gary Takis over 11 years ago

Dan...
Here is a fresh attempt and the debug.log results with the DR-235...
The error reads different... Now it reads "Unexpected response from Radio".
Immediately after, I checked with brand 'X' software and it worked fine.
Gary

Actions #8

Updated by Dan Smith over 11 years ago

Hmm, the radio and PC are clearly talking. After sending the block request string (which is correct), the radio reports "ERROR". I'm not quite sure what to say about that, since it's a pretty simple exchange...

I've added another piece of tracing information to the code. Please re-test with tomorrow's daily build and post the updated debug log.

Thanks!

Actions #9

Updated by Mitch Kobierowski about 10 years ago

Hello,
Today I was programming a friends DR-235 and encountered the same errors as in the original post. I think I have found a fix for the problem. If you look at the DR-235 owners manual in the cloning section, it says not to use 9600baud to communicate between the radios. In checking the default baud rate of the usb to serial adapter (prolific), I discovered the default to be 9600 baud. I changed the baud rate from 9600 to 19200. Tried to program the radio again, and everything worked fine. I was able to read from and write to the radio. I did get an odd error at the end of writing to the radio, but the radio was programmed correctly. Anyway, changing the baud rate to something other than 9600 seems to have corrected the problem. Hopefully this helps.

Actions #10

Updated by Bernhard Hailer almost 4 years ago

  • Status changed from New to Closed
  • Model affected changed from DR-235 to Alinco DR-235

Resolved by submitter / Patches added.

Actions

Also available in: Atom PDF