Bug #52
closedUpload frozen at 40% / "Clone Error" message on VX-7R's screen
0%
Description
Good day,
First of all, thank you for bringing to the OSX community this useful tool. Having both a PC running windows XP and Mac mini running OSX 10.7, i downloaded both versions. The problem shows only with OSX. Every upload to the VX-7R lead to frozen progression bar at round about 40% and an "clone error" msg on VX-7R'screen. Then, it's not possible to quit Chirp from it's menu. Going thru the "force to quit" finder's menu clean-up the screen but then the finder is more or less frozen, unable to shut-down the computer. I have to force the shut-down, to restart in single user mode and do some repairs thru the "fsck -fy" command to recover to fix system files. I don't have this upload problem when i am using the XP machine.
On both OS, the download from from the VX-7R is fine except a little problem reading memory with names containing such "@" symbols.
Of course, i am using the same USB cable to connect to VX-7R either to windows or OSX.
I found that VX Commander has no problem to read memories names containing symbols, when Chirp is ignoring those memories (cf cap screen).
Best 73s de Cyril
Files
| debug.log (2.48 KB) debug.log | |||
| Capture_d’écran_2012-02-09_à_13.51.06.jpg (56.3 KB) Capture_d’écran_2012-02-09_à_13.51.06.jpg | ignored memories |
Updated by Dan Smith about 12 years ago
Hi Cyril,
The issue with the @ symbols in the names is understood. Could you file a separate bug for that one just to keep it distinct from the clone issue? I have something else to work on with the vx7 in the near future, so I will make an effort to fix the name issue at that time as well.
On the cloning issue, it's unfortunate that MacOS is unable to handle that bit of application misbehavior. It definitely should be able to gracefully kill the offending task without all the trouble you describe. It may be related to the use of X11 -- I'm not a Mac person.
If I send you a patch file, are you able to descend into the internals of the .app and apply a patch from the command line? That will be the easiest way for me to get you to try a change without having to integrate it into a formal build.
Thanks!
Updated by Dan Smith about 12 years ago
Er, actually, I just noticed that you're using 0.1.12. Have you tried the latest daily version? It looks to me like the @ memories should be supported properly in that version of the code.
At the bottom of the downloads page, there is a link to the repository of daily builds. Grab the latest and give that a shot.
Thanks!
Updated by Cyril Hollande-Boyer about 12 years ago
Hello Dan,
I am not at my best with Terminal and the command line, but if you tell me what to do (what to type in) i can give try...
About the latest daily built on windows, i will give a try as well and will forward some feedback.
Thank you for quick answer,
73's
Updated by Travis Augustine almost 11 years ago
My apologies for posting to an old bug but it describes the exact problem I am having so it seemed like a good place to start. I have Chip installed on both an Ubuntu 13.04 box and two separate Mountain Lion Macs. Everything works perfectly on the Ubuntu system but on the Mac systems I am getting the 40% bar accompanied by a "clone error" on the VX-7. It reads just fine, but it fails on the write. When it does, I have to force quit the app, and the force restart the mac in question. Thankfully I don't have to fix system files like the original op does but I the issue does effectively render my mac inoperable until I reboot it.
A great program and I can't wait to use it on my FT-8800R and my FT-857D so that they are all programmed the same once this issue is fixed.
Thank you for all your hard work and dedication into what seems to be a great product.
73,
Travis W9HDG
Updated by Dan Smith almost 11 years ago
- Chirp Version changed from 0.1.12 to 0.3.0
Yeah, unfortunately the state of USB-to-serial drivers on OSX is pretty sad. I'd bet that if you look in dmesg (or your system log or whatever) you'll see kernel messages about the USB device being thrown offline and then coming back online during the transfer. That seems to be the most common situation.
Most folks seem to eventually resolve their issues by finding drivers that work better with their USB hardware, finding better USB hardware, etc. The CHIRP code is 100% the same on Windows, Mac and Linux, so the fact that it works on the latter shows that the clone code is working as expected :)
Good luck!
Updated by Travis Augustine almost 11 years ago
Sounds good, I'll start hunting for new drivers. I use a different USB-Serial adaptor for packet work and that was a colossal pain so guess I'm not surprised.
Updated by Bernhard Hailer about 4 years ago
- Status changed from Feedback to Closed
- Chirp Version changed from 0.3.0 to daily
No more traffic on this ticket.