Project

General

Profile

Actions

Bug #7725

open

Won't Upload data file to IC-2730 using MacOS

Added by Paul Alonge over 4 years ago. Updated 7 months ago.

Status:
Blocked
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
03/23/2020
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Icom IC-2730A
Platform:
MacOS
Debug Log:
I read the instructions above:
Yes

Description

Summary: I can download the data from the radio, but I cannot upload a file to the radio. This is even if I try to upload the file that was originally downloaded, without any changes.

Details:
The radio that I want to program is an ICOM IC-2730A
I am using a MacBook Air, running Catalina, 10.15.2
I am connecting using an EZSync USB FTDI OPC-478 Cable for ICOM and Alinco Radios, with a true FTDI Chip.

  1. I downloaded the MacOS Unified Application - 20200227
  2. I moved the downloaded CHIRP file from my downloads to my Applications folder
  3. Then I “cntrl-clicked” on it using my touchpad and the Control Key. When the security panel came up and asked if I was sure l wanted to open it, I clicked on the “Open” button.

I was presented with a blank CHIRP window and the CHIRP menus. Never having used CHIRP before, I assumed this was the right “look”.

  1. I then plugged my cable into my laptop and the “speaker 2” jack of my radio and powered on the radio.

My radio came on in its default settings of 146.010 on the left and 440.000 on the right.

  1. I navigated the menu system: MENU>EXEMENU>FUNC>CI-V…
    I left the CIVADR = 90; CIVBAUD = AUTO
    I changed CIVTRAN to ON
    Then I backed out of the menu system

  2. I then went to CHIRP and went to the “Radio” menu. I selected “Download from Radio” so that I could get the default configuration and save it.

  3. In the “Radio” popup: I selected the appropriate port, “ICOM” as the vendor, and “IC-2730A” as the model. Then hit “OK”.

  4. I said “OK” on the instruction screen.

The CHIRP program showed the “Cloning” status bar and my radio displayed “CLONE OUT” on the screen. Then the radio reset and CHIRP displayed the default values.

  1. I saved the file. This showed that the program can reach my file system. So I am not suffering the problems that have been discussed previously regarding the security and file system issues (Issue #7663)

UP TO THIS POINT, ALL WAS WORKING AS EXPECTED!

I then imported a known good file and tried to upload it to the radio. The cloning process started but aborted part of the way through. The radio froze displaying “CLONE ERROR” and had to be reset.

In order to verify that this was not due to the data file, I went back through steps 1-5 above. Then I reloaded the default ICOM file that I had saved in step 9.

  1. Then I went to the “Radio” menu in CHIRP and clicked the “Upload to Radio” Option.

  2. I clicked OK on the popup since the port had not changed, and clicked “OK” on the instructions.

The cloning bar started to move and the radio displayed “CLONE IN”. But it aborted part way through and displayed “CLONE ERROR” again. Note that this was while uploading the unmodified file that I had downloaded directly from the same radio.

Please help me determine what is wrong.

I have attached the debug file and the .img file from the radio.


Files

Icom_IC-2730A_20200323.img (21 KB) Icom_IC-2730A_20200323.img Paul Alonge, 03/23/2020 02:28 PM
debug.log (44 KB) debug.log Paul Alonge, 03/23/2020 02:31 PM
Actions #1

Updated by Paul Alonge over 4 years ago

Actions #2

Updated by Bernhard Hailer over 4 years ago

  • Status changed from New to Feedback
  • Target version set to chirp-legacy
  • Model affected changed from (All models) to Icom IC-2730A
  • Platform changed from Windows to MacOS

You're locked in a catch-22.

Some Icom radios are known to deny cooperation with FTDI cables (even genuine ones). Please try a cable with a genuine Prolific chip.
Unfortunately cables with fake "Prolific" chips make the vast majority of cables on the market; genuine Prolific cables are on the more expensive side.

Now the problem with MacOS is that it seems to like FTDI, but not so much Prolific (even genuine ones).

The one thing you can try is a different operating system for now... :-/

Actions #3

Updated by Rick DeWitt almost 4 years ago

  • Assignee set to Rick DeWitt

I will try to take a look at this. May need to find a local operator with a MAC and use my radio...

Actions #4

Updated by Rick DeWitt 7 months ago

  • Status changed from Feedback to Blocked
  • I read the instructions above set to Yes

Due to medical issues I can no longer devote time to CHIRP driver development.
This issue needs to be re-assigned.

Actions #5

Updated by Dan Smith 7 months ago

  • Assignee deleted (Rick DeWitt)
Actions

Also available in: Atom PDF