Bug #87
closedNew memory channels on Yaesu VX-5 cause radio to lock up - suspect Icon number invalid
100%
Description
Preamble: Having discovered that the latest stable CHIRP version (0.2.0) writes memory channels to the Vx-5 as "hidden", I saw the issue report that said it was fixed for release in 0.2.1, so I used the daily version 03202012 to try to add new memory channels.
What happened: The channels I added were in the range 200 to 220. On trying to tune the radio to these from either direction, it either re-booted, or locked up completely (no response to any controls, the only way to clear it was to remove the battery). It seemed to reboot when going down the channel numbers to 220, and lock up when going upwards to 200, but I didn't explore this to confirm it.
I used VX-5 Commander to download the radio's configuration and noticed that the Icon number for the channels I'd added in CHIRP had 64 in it - the Vx-5 only has 32 icons!
I did a Reset of the radio to remove any vestiges of the problem data, Used Vx-5 Commander to change the icons to valid ones and uploaded the configuration successfully (you'll forgive me if I don't trust CHIRP on this radio at the moment!). The radio now behaves normally.
I don't know if the invalid icon numbers were the cause of the flakey behaviour, but it looks suspicious!
-- Howard
Files
Updated by Tom Hayward over 12 years ago
- Target version set to 0.2.2
I've seen this bug too. There are many parts of the VX5 memory that Chirp considers "unknown". It does not attempt to change data in these sections. It will write back to the radio whatever was there in the first place. If it was an unused channel, there could be essentially random data in these sections that the radio does not understand.
A simple workaround to fix a "lockup" channel is to use the VX5 to overwrite it (with 144.000 MHz, or whatever you want). Now that memory is sanitized and you can successfully overwrite it again with Chirp.
My plan to fix this bug is to do essentially the same thing--determine good values for the unknown stuff, and copy those values to all new memories. I should have this complete for 0.2.2. Thanks for the tip about the icon values; I'll start there.
Updated by Tom Hayward over 12 years ago
By the way, it sounds like you are getting lockups with 100% of the new channels you've created (or did you only test 201 and 220?). I'm getting lockups on approximately 1% of the channels, so it's much less annoying to fix them by overwriting the channel with the VX5.
Could you attach both your bad (lockups) img file, and the img file that worked after fixing the icons?
Updated by Tom Hayward over 12 years ago
- File vx5-initialize-new-memories.patch vx5-initialize-new-memories.patch added
- Status changed from New to Resolved
- % Done changed from 0 to 100
I've completed a fix for the lockups I was getting on some new memories. I've attached the fix as a patch. If you know how to apply a patch, you can test it now. If not, this fix should make its way into the daily build in the next day or two. Please let me know if this solves your problem.
The new code only takes affect when creating new channels (not overwriting existing ones), so if you have an img file created with the old code that needs to be "fixed", you'll need to follow this procedure:
File > Open, and choose your old img file¶
Select all memories (Ctrl-a)¶
Edit > Delete¶
File > Import, and choose the same old img file you just opened¶
Click Select All in the Import dialog¶
Click OK¶
All of your old memories will be imported¶
Upload to radio and/or Save As¶
Updated by Howard Winter over 12 years ago
Tom,
Wow, you dealt with this quickly!
Unfortunately I don't have the "bad" image files, as I stored them in the same directory as the software (I always put application software on a non-C: drive, and put the data with it where possible) and I didn't realise that installing another version would wipe that, which it did!
As for only trying the two "ends" of the bad channels, I'm not sure if there is another way to select them than turning the knob, which will always find one end or the other of the bad range and won't go past it. (If you can type in a memory number, I wasn't aware of that, or how to do so).
I used to know how to do patches many years ago, but I can't remember now, so I'll download a Daily and see how it goes - from the timing it may just have snuck in last night! :-)
Thanks for the fast response!
Cheers, Howard
Updated by Dan Smith over 12 years ago
Sorry, it didn't because I forgot to push, but it'll be there for tomorrow :)
Updated by Howard Winter over 12 years ago
I downloaded Sunday's Daily, and it all seems to be working fine now - well done!
Cheers,
Howard G1BYY
Updated by Tom Hayward over 12 years ago
- Status changed from Resolved to Closed
By the way...
Howard Winter wrote:
As for only trying the two "ends" of the bad channels, I'm not sure if there is another way to select them than turning the knob, which will always find one end or the other of the bad range and won't go past it. (If you can type in a memory number, I wasn't aware of that, or how to do so).
You can type the memory channel number then hit MR to tune directly. For example, to recall memory channel #205, press 2 - 0 - 5 - MR. More info on page 43 of the manual, under Memory Recall.