Project

General

Profile

Actions

Bug #11600

closed

ID5100 Out of Sync error

Added by Jarred Burk 2 months ago. Updated about 2 months ago.

Status:
Not a bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
10/08/2024
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
Icom ID-5100
Platform:
Windows
Debug Log:
I read the instructions above:
Yes

Description

I was trying to clone my data from Chirp to my Icom ID5100. When I told it to upload, the software showed it was cloning the data properly but when it got to the end of the upload, an error message appeared. The message read "Failed to communicate with the radio. Out of sync with radio." I have used Chirp to program this radio before with no issues. Now, what was programmed in the radio has been erased and nothing will load onto the radio.


Files

config.txt (1.14 KB) config.txt Jarred Burk, 10/08/2024 01:59 PM
Icom_ID-5100_20240307.img (169 KB) Icom_ID-5100_20240307.img Jarred Burk, 10/08/2024 01:59 PM
debug_log.txt (9.23 KB) debug_log.txt Jarred Burk, 10/08/2024 01:59 PM

Related issues 1 (0 open1 closed)

Has duplicate Bug #11617: ID5100 Out of SyncRejected10/15/2024

Actions

Updated by Jarred Burk 2 months ago

[Uploaded from CHIRP next-20241003]

Actions #2

Updated by Dan Smith 2 months ago

Yeah, the upload is failing on the first block. All icoms reset themselves after any failed clone-in operation. They also reset themselves if there's anything in the inbound image they don't like. Have you maybe upgraded the firmware in the radio since the last time it worked, or when was that? I also just talked to someone locally that used this driver with their radio without a problem.

Nothing has changed with this driver in a few years, so I don't think there's anything software-wise going on here. I would guess potentially cable driver or connectivity issues since the very short exchanges to identify the radio seem fine, but the first large block failed.

Actions #3

Updated by Jarred Burk 2 months ago

I only updated to the newest Chirp.
I found it weird that it would download from the radio with no issue but wouldn't upload. Would that be normal?

Yahoo Mail: Search, Organize, Conquer

On Tue, Oct 8, 2024 at 4:38 PM, Dan Smithredmine@chirpmyradio.com wrote:

Actions #4

Updated by Dan Smith 2 months ago

Yeah, that's a common symptom of bad communication. On Icoms, during download, the computer just sends "okay give me what you got" and the radio spews the whole thing out (aside from a little more handshaking at the end). On upload, it's the computer doing all the talking. It's not unusual for a bad connection or OS serial driver issue to impact one method more than the other. Other radios are much more chatty during both processes which makes them more susceptible regardless of upload or download.

What sort of cabling are you using?

Any idea what version of chirp you were running before? The chirp 5100 driver was touched in June, but as part of a larger change that affected basically everything. Before that it was January 2023 that any actual runtime change was made:

https://www.chirpmyradio.com/projects/chirp/repository/github/changes/chirp/drivers/id5100.py?rev=master

Maybe go back and try the earliest build from before that wide change and see if that has any effect?

https://archive.chirpmyradio.com/chirp_next/

If so, that'll be a good data point.

Actions #5

Updated by Dan Smith 2 months ago

  • Subject changed from Uploading Data to ID5100 Out of Sync error
Actions #6

Updated by Dan Smith about 2 months ago

  • Status changed from New to Not a bug

Note that I've confirmed locally that the ID-5100 driver is working properly and I have no issues downloading or uploading here. I'm using a genuine Icom OPC-478, Genuine FTDI USB-to-serial adapter and the same firmware version of the radio as indicated in your log/image. Given that info and that there has been no follow-up here, I'm going to close this as not a bug. If you find more information or an older version that works for you when the current does not, please comment here and we can re-open.

Actions

Also available in: Atom PDF