Bug #169
open
VX-7 doesn't recognize memory groups until one is set on the radio's keypad
Added by David Griffith about 11 years ago.
Updated over 1 year ago.
Model affected:
Yaesu VX-7R
Description
If you create a setup for the Yaesu VX-7 which has frequencies assigned to memory groups, the VX-7 will not recognize any of them as being valid unless and until you assign a memory slot to a memory group from the radio's keypad. After this is done, all memory slots are assigned to memory groups as they appeared in Chirp in addition to the assignment you just made.
Here are two image files containing three memories assigned to memory group 1 and are identical except that test1.img is buggy in this regard whereas test2.img is not.
Files
|
test1.img (15.8 KB)
test1.img |
buggy |
David Griffith, 05/11/2012 10:05 PM
|
|
|
test2.img (15.8 KB)
test2.img |
good |
David Griffith, 05/11/2012 10:05 PM
|
|
|
test.diff (3.98 KB)
test.diff |
Diff of test2.img against test1.img |
David Griffith, 11/16/2015 09:41 PM
|
|
|
mg-test1.hex (66.3 KB)
mg-test1.hex |
another test, but with just one channel set |
David Griffith, 11/16/2015 09:47 PM
|
|
|
mg-test2.hex (66.3 KB)
mg-test2.hex |
one channel, after being uploaded, manually set a MG, then downloaded again |
David Griffith, 11/16/2015 09:47 PM
|
|
|
mg-test.diff (4.65 KB)
mg-test.diff |
Diff of mg-test1.hex against mg-test2.hex |
David Griffith, 11/16/2015 09:47 PM
|
|
Further investigation show that the radio will not accept any memory group as valid until you assign a memory slot to that group. I previously believed that if you make one assignment, that will cause all groups to be recognized.
I uncovered another bug in how memory group settings are saved, but will put that in a different bug report.
Still further investigation shows inconsistent appearance of the bug in my previous update. Sometimes you need to use the keypad to assign a channel for each memory group and sometimes doing it just once will be enough for all groups to be recognized.
Are you working on trying to find the magic bit? It will be a week or so before I can take a look at it.
I typically use a script that does a hexdump of each image, followed by a diff -u, which is usually effective. You might also try vbindiff.
This problem is still present and seems to have become more complicated. I just now uploaded a setup that contains just one channel and assigned that one channel to MG1. Memory groups didn't work. I manually assigned channel 1 to MG1. Groups still don't work. Assigned it to MG2. Now groups work, but there's a bizarre side-effect. In MG1 and MG2 are lots of old channels from previous uploads. Shouldn't CHIRP completely blank those memories too?
Here's a diff of test2.img against test1.img after being run through xxd.
generated with "diff -u mg-test1.hex mg-test2.hex". Also, the previous diff was generated with "diff -u test1.hex test2.hex".
To make an .img file into hex, do "xxd test1.img test1.hex".
To turn a hex file back into binary, do "xxd -r test1.hex test1.img".
- Status changed from New to Feedback
- Target version set to chirp-legacy
- Model affected changed from VX-7 to Yaesu VX-7R
The original problem is 8 years old. Is it still an issue with current builds?
I just downloaded the software for Mac for the first time and am having this exact issue with multiple weird permutations. I know this is a long running issue. Is this a fixable bug or any good workarounds?
Also available in: Atom
PDF