Project

General

Profile

Actions

Bug #240

closed

For Icom IC-T70A using Mac OS X

Added by Richard Steck over 12 years ago. Updated over 4 years ago.

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

0%

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

Description

Here is my environment:

Icom IC-T70A
Mac OS X 10.7.4
Chirp 0.2.2 (but same problem on 0.2.1)

Only one thing doesn't work-- I can download but I can't upload to my IC-T70A. When I upload, Python goes into a not responding state.

I checked permissions on /dev/cu.usbserial and that does not seem to be a problem.

Last login: Sun Jul 8 18:49:38 on console
Mac-Mini-2:~ rsteck56$ ls -al /dev/cu.usbserial
crw-rw-rw- 1 root wheel 18, 7 Jul 11 05:48 /dev/cu.usbserial
Mac-Mini-2:~ rsteck56$

Any suggestions would be appreciated.

Thank you.


Related issues 1 (0 open1 closed)

Related to Bug #2605: IC-T70A does not work with FTDI cable at allClosed05/21/2015

Actions
Actions #1

Updated by Richard Steck over 12 years ago

Sorry, the Platform is MAC, not Windows.

Actions #2

Updated by Dan Smith over 12 years ago

  • Description updated (diff)
  • Platform changed from Windows to MacOS

Need a debug log, per the instructions: How_to_report_issues

Actions #3

Updated by Tom Hayward about 12 years ago

  • Status changed from New to Blocked

Still waiting on a debug log.

Actions #4

Updated by Joseph Peterson over 11 years ago

Richard,
I'm not a Chirp developer, just another user, but I'm on a Mac and hope to help get the issues resolved..
Did you produce a debug log? are you still experiencing the issue?

The debug log is cleared every time you start chirp, so the procedure for getting a usable log is:

  1. Start chirp
  2. Reproduce the failure or bug
  3. Close chirp
  4. Copy and send the debug.log before starting chirp again

On the Mac platform, your debug log should be in your home directory, in .chirp/debug.log. If you don't know how to find this, open up a terminal window and run the following command at the prompt:

cp ~/.chirp/debug.log ~/Desktop
Then close the terminal window. The debug.log file will be on your desktop.

Hope this helps

Actions #5

Updated by Nick Papadonis over 9 years ago

Was this ever resolved? I'm using daily builds of Chirp and a genuine FTDI cable with my Mac. I'm unable to Download from the Radio and created the following bug:

http://chirp.danplanet.com/issues/2605

Actions #6

Updated by Bernhard Hailer over 4 years ago

  • Status changed from Blocked to Closed
  • Chirp Version changed from 0.2.2 to daily
  • Model affected changed from ICOM IC-T70A to Icom IC-T70A

No more feedback by submitter.
Duplicated by #2605; please leave further feedback there. Thanks!

Actions

Also available in: Atom PDF