Project

General

Profile

Actions

Bug #9865

closed

Clone error when uploading to Icom 2730 from macOS app

Added by Mark Kulich over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
05/08/2022
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
MacOS
Debug Log:
I read the instructions above:

Description

When uploading to an Icom 2730 from macOS the radio will report a clone error part way through the upload using an rt systems USB-29A cable. I am able to download from the radio without issue. After the error, the radio must be restarted and is restored back to factory state. Furthermore, I can upload to radio without issue using the same cable and MacBook but running the Windows version of Chirp on a Windows VM. Also, using the cloning cable with the rt systems software works fine. See below for system/cable information and attached logs and chirp image.

Cloning cable: rt systems USB-29A
Radio: Icom 2730a
Computer: 2018 MacBook Pro macOS 12.3.1
Additional notes: Since the MacBook Pro has usb c ports I'm using an usb a to usb c adapter


Files

debug.log (57.2 KB) debug.log Mark Kulich, 05/08/2022 11:43 PM
Icom_IC-2730A_Local.img (21 KB) Icom_IC-2730A_Local.img Mark Kulich, 05/08/2022 11:43 PM
Actions #1

Updated by Dan Smith about 2 years ago

  • Status changed from New to Closed

Hi Mark,

Just FYI, that's almost certainly a bug in the driver for your cable. By using it in a windows VM, you get the Windows driver for the cable. MacOS USB-to-serial drivers are pretty terrible. FTDI is, of course. In general people try to stay away from using RTSystems cables, not because they're necessarily bad (I don't know much about what they use) but because they intentionally try to make their cables not work with other software.

The CHIRP code is identical on all three platforms, and Icom radios are very robust in that they are not sensitive to small timing changes like some of the other radios. There are no (relevant) errors in the provided log that would point to anything CHIRP is doing wrong.

Not much help, I know, but...

Actions

Also available in: Atom PDF