Bug #471
closedBaofeng UV-5RC download crash on OS X
0%
Description
New radio, new user, etc. Trying to download, the progress bar goes all the way (almost), then the memory editor screen (I guess that's what it is, looks like a spreadsheet/UI) shows for half a second, then the whole app crashes. This happens every time with the latest release, the previous release version, and for giggles I tried the Jan. 1st build - all identical crashing. I'm running Mac OS X 10.8.2 on a 2012 MBP, I have a generic cable with popular driver for it installed, Python r10 installed (basically everything as suggested from hereon the CHIRP site). I'm also attaching debug log, which should have all other necessary info, but if not please let me know - I am happy to provide anything else needed. Thank you!
Files
| debug.log (6 KB) debug.log | |||
| debug.log (19.6 KB) debug.log | |||
| Screen Shot 2013-02-03 at 7.00.24 PM.png (76.2 KB) Screen Shot 2013-02-03 at 7.00.24 PM.png | |||
| debug.log (37.5 KB) debug.log |
Updated by Dan Smith almost 12 years ago
- Tracker changed from Bug to New Model
- Subject changed from Crashes after Download to Baofeng UV-5RC
- Status changed from New to Blocked
Can be supported when a developer gains access to a UV-5RC (not currently supported by CHIRP).
Updated by Michael Holdren almost 12 years ago
Thanks for the update Dan. So does this mean I have no software options (especially CHIRP) on a UV-5RC for the time being?
Updated by Dan Smith almost 12 years ago
All it means is that chirp doesn't support this radio at this time. I can't speak for any other options.
Unfortunately, the chinese manufacturers play very fast and loose with the names of these radios, and some that appear nearly identical to others are actually quite different. This makes it very hard to keep tabs on what chirp does and does not support, and definitely makes it difficult for the volunteers that contribute to this project to acquire all of these variants and ensure support.
Thanks!
Updated by Jim Unroe almost 12 years ago
- Chirp Version changed from 0.2.3 to daily
Michael,
The UV-5RC is supported by CHIRP. All of the extra letters and symbols appended to the end of UV-5R only identify cosmetic differences (primarily different case styles). All of the internal electronics are the same (except for the differences due to the various firmware versions).
Jim KC9HI
Updated by Michael Holdren almost 12 years ago
Hi Jim, so is the issue that my radio has BFB297 firmware?
Updated by Dan Smith almost 12 years ago
If the current build still has issues for you, please include an updated debug log.
Updated by Michael Holdren almost 12 years ago
Thanks Dan, apologies if I am going outside the process - still very new to this. :)
Updated debug log attached.
Updated by Dan Smith almost 12 years ago
- Status changed from Blocked to Feedback
Your latest log appears to indicate that the original bug was indeed fixed and that CHIRP is now downloading an image from your radio. Your radio has some non-standard tones in it, which is causing CHIRP to choke on those memories. However, you should now be presented with the the memory spreadsheet view after you attempt a download, with the affected memories marked as "ERROR". Is that correct?
Updated by Michael Holdren almost 12 years ago
Hi Dan, unfortunately not. I am still experiencing the same crash as before, although it does seem to take almost a full second before it crashes (in the previous version, it was about half a second - if that).
Updated by Michael Holdren almost 12 years ago
Dan, I was able to get a screenshot (after a few attempts) before it crashes. It does not appear to be downloading anything from the radio (see attached). If I can identify the non-standard tones in the debug log and remove them from the radio using the keypad, is it possible that would remove the crashing issue?
Updated by Dan Smith almost 12 years ago
- Status changed from Feedback to Blocked
No, it's not crashing because of the tones.
I just re-read your initial description of what you're seeing, which is probably a crash in GTK or something else external to (but used by) CHIRP, which is why it doesn't show in the log. Being on OSX (the least-supported platform, unfortunately) I think this is likely something beyond our control, and certainly not something I'm going to be able to reproduce and address.
My suggestion would be to try the linux livecd, or the windows version in a virtual machine to confirm that CHIRP itself is working properly with your radio. It should still complain about the odd tones in your radio, but should not crash post-download. If you can reproduce it with either the linux or windows version, I'll happily take a further look. However, there's not much I can do for you on the MacOS front.
Tom is the only developer with any real experience on OSX, and I'm sure he's monitoring this traffic and will chime in if he has any ideas.
Updated by Michael Holdren almost 12 years ago
Dan, thank you so much for the effort here. Unfortunately, I'm not having any luck with either of the other platforms either. I'm running Parallels which lets me run XP and Ubuntu, and both are have been giving me errors too: XP won't even launch (getting "...application failed to start because configuration is incorrect..." message, of which I have reinstalled several times with no change) and I can't even find the application folder in Ubuntu to launch it (I really have no clue what I'm doing in that one). I suppose I could submit another Issue for the XP error I am getting, but would much rather stay in OS X. If Tom does not post a response in the next few days, I'll move forward with my XP issues. Thank you!
Updated by Dan Smith almost 12 years ago
The XP issue is a problem with your system, not CHIRP. There's an entry about it dedicated in the FAQ, but it will require some googling to solve whatever your underlying problem is.
I recommend the Ubuntu LiveCD (available on the download page). It's pretty idiot-proof (no, I'm not calling you an idiot).
Updated by Michael Holdren almost 12 years ago
Ha! Okay, thank you very much Dan. I'll explore both options then (although I'm still optimistic that the OS X issue can be resolved).
Updated by Michael Holdren almost 12 years ago
LiveCD worked with my radio, so it is something with OS X.
Updated by Tom Hayward almost 12 years ago
- Assignee set to Tom Hayward
I haven't had a chance to test this yet, but I'm going to take ownership so I don't forget about it.
Updated by Michael Holdren almost 12 years ago
Fantastic, thanks Tom! Looking forward to hearing on any updates.
Updated by Michael Holdren almost 12 years ago
Tom - just updating on what works on OS X: In OS X, I can open CSV and images, but downloading from my radio still crashes the app. So my workaround is that I booted LiveCD (using Parallels), downloaded data from my radio, updated the file as desired (with content from RadioReference.com and RepeaterBook), and saved the CHIRP image to my OS X environment. I opened CHIRP in OS X, opened the image, connected to the radio, and then uploaded the image to the radio. Lengthy, but it works for now.
Updated by Tom Hayward almost 12 years ago
- Assignee deleted (
Tom Hayward)
I just tried to test this and then realized that I can't test it because it only happens with your radio.
Updated by Tom Hayward almost 12 years ago
- Tracker changed from New Model to Bug
- Subject changed from Baofeng UV-5RC to Baofeng UV-5RC download crash on OS X
- Model affected set to UV-5RC
- Platform set to MacOS
Fixing some fields the reporter didn't originally specify.
Still blocked while waiting for a debug.log. Last debug.log was from before fixing non-standard tones. Chirp only supports standard tones.
Updated by Michael Holdren almost 12 years ago
Hi Tom, what's a standard tone and a non-standard tone?
I'm attaching the latest debug log. After the work around stated above, and with Chirp 0.3.0, I no longer seem to have the crash issue when downloading from the radio (I only tried it once after the 0.3.0 release and no issue, have not needed to download since then).
Updated by Tom Hayward almost 12 years ago
- Status changed from Blocked to Rejected
Michael Holdren wrote:
Hi Tom, what's a standard tone and a non-standard tone?
Here is a list of the standard CTCSS tones: http://en.wikipedia.org/wiki/Continuous_Tone-Coded_Squelch_System#List_of_tones
I'm attaching the latest debug log. After the work around stated above, and with Chirp 0.3.0, I no longer seem to have the crash issue when downloading from the radio (I only tried it once after the 0.3.0 release and no issue, have not needed to download since then).
I'm going to close this because you can no longer reproduce the issue. If you find a way to reproduce it, post here and I will re-open it.