Project

General

Profile

Actions

Bug #1881

closed

Mac 10.9.4 hangs, needs reboot uploading to VX-6R

Added by Walter Underwood over 9 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
08/30/2014
Due date:
% Done:

0%

Estimated time:
Chirp Version:
0.4.0
Model affected:
Yaesu VX-6R
Platform:
Windows
Debug Log:
I read the instructions above:

Description

I have a Kawamall cable and was finally able to download from my VX-6R.

Later, after getting a new MacBook, I added four new frequencies and tried to upload to the HT. It hung with the progress bar about 20% of the way across. Mac needed rebooting. Memories are wiped out on the VX-6R.

This is absolutely consistent. I tried several times, including after making the number of stored frequencies smaller. It still hangs loading 29 memories.


Files

chirp-debug-2014-08-20.log (4.25 KB) chirp-debug-2014-08-20.log Walter Underwood, 08/30/2014 05:08 PM
Actions #1

Updated by Dan Smith over 9 years ago

Hi Walter,

The only thing that could cause that is a problem with the driver the USB-to-serial cable. Do you know what chipset the cable uses? FTDI perhaps? I think if you hunt through "system information" you will be able to find something about the chip that is used. If it's FTDI, I think it's a known problem with that driver and later versions of MacOS.

Actions #2

Updated by Walter Underwood over 9 years ago

The Kawamall cable uses FTDI. Mac OS X 10.9 includes an FTDI driver. I am not using the FTDI-provided driver.

Looks like a driver issue to me, too.

Actions #3

Updated by Jens Jensen over 9 years ago

can you provide the output from the following two commands when your cable is plugged in:

@
kextstat |grep -i ftdi
@

@
ls -l /dev/cu.usbserial-*
@

Actions #4

Updated by Walter Underwood over 9 years ago

Dang it, the KawaMall cable uses a Prolific chip. I guess you can take them off the recommended list. Works for fetching memories, but not for sending them to the radio.

$ ls -l /dev/cu.usbserial*
crw-rw-rw- 1 root wheel 19, 5 Sep 9 09:22 /dev/cu.usbserial
$ kextstat | grep -i prolific
350 0 0xffffff7f822b2000 0x7000 0x7000 com.prolific.driver.PL2303 (1.5.1) <113 13 5 4 3>

Here is what System Information says:

USB-Serial Controller:

Product ID: 0x2303
Vendor ID: 0x067b (Prolific Technology, Inc.)
Version: 3.00
Speed: Up to 12 Mb/sec
Manufacturer: Prolific Technology Inc.
Location ID: 0x14100000 / 27
Current Available (mA): 500
Current Required (mA): 100

Actions #5

Updated by Tom Hayward over 9 years ago

  • Status changed from New to Feedback

Prolific chips work fine, it's just a lot harder to match up with the proper driver. Jens' installer does a pretty good job sorting this out for OS X: MacOS Tips

Actions #6

Updated by Walter Underwood over 9 years ago

Thanks, the other driver works now, both for upload and download. I was using the latest official driver from Prolific.

That was a painful experience.

If I knew that the Kawa cable used a Prolific chip, I would have bought something different.

Actions #7

Updated by Tom Hayward over 9 years ago

  • Status changed from Feedback to Rejected

The official Prolific driver only works with official Prolific chips. Sounds like you got a counterfeit.

Glad you were able to resolve the issue.

Actions #8

Updated by Walter Underwood over 9 years ago

It worked for download but not upload.

Perhaps KawaMall should not be a recommended source of cables.

Thanks for the help.

K6WRU

Actions #9

Updated by Tom Hayward over 9 years ago

Walter Underwood wrote:

Thanks, the other driver works now, both for upload and download.

Walter Underwood wrote:

It worked for download but not upload.

Can you clarify what you mean by these two statements?

Actions #10

Updated by Walter Underwood over 9 years ago

I was able to clone from the radio to Chirp with this cable on my previous MacBook running 10.8. That MacBook died.

My new MacBook running 10.9 would hang when trying to clone from Chirp to the radio.

With the open source driver, it can clone both ways.

It is possible that I was using the open source driver on the old machine, I have no way to verify that now.

Actions

Also available in: Atom PDF