Re: [chirp_devel] [PATCH 0 of 3] [RFC] Radio Mods Interface
(pulling the list back into this thread)
On 04/06/2011 12:25 PM, Robert Terzi wrote:
Reading between the lines for some of the stuff I've read about the VX-8R, there was a firmware setting that could be reached through a service menu/backdoor, which would change the frequency ranges it would tx on. I believe the purpose was changing the region. Doing this changed the model number that was reported by the radio for the clone interface and would cause all of the settings to be reset (so the radio lost all programming).
Are you sure you're not thinking of the VX7? What you describe is exactly how it works for that radio, but the VX8 makes a departure from the three-block protocol that the 7 (and others of that vintage) use. The block missing is the one with the mods in it.
Rick did some work on the VX3 trying to figure out the soft mod but I'm not aware that anything ever came of it. Personally, I think its likely that Yaesu didn't carry that "feature" forward past the VX5/7 days.
For what is worth looking at vx6tool.c, the vx6 could be freebanded by changing two bytes looks like offset 8 & 9.
Yep, the 2,5,6, and 7 all have that one block in between the header and the memory data, but the 3 and 8 do not (which is the source of my skepticism)
On whether mods in terms of freebanding should be part of a general settings interface -- my inclination is to say no, especially from the user interface point of view.
Aside from the obvious liability issues, if changing the frequency ranges causes radios like the vx-8 do a full reset, it would be problematic for the user, they'd probably have to download to the radio multiple times, there is currently no backup or manipulation of the regular settings through chirp. I'd rather see the frequency range settings done through a separate UI even though it probably shares most of the code/models of the radio underneath.
Hmm, well, I'm not too worried about the liability issues. I certainly plan to throw up a huge blinking buzzing warning about doing something to your radio that you might regret.
I think that it will be fairly easy to re-use the same key/value mechanism underneath the covers without making the UI (for settings and mods) a big mess of knobs. That's what I meant about using this system for generic settings and mods. It will definitely need a little augmentation to allow it to be organized.
Thanks for the feedback!
On 04/06/11 23:48, Dan Smith wrote:
(pulling the list back into this thread)
On 04/06/2011 12:25 PM, Robert Terzi wrote:
Reading between the lines for some of the stuff I've read about the VX-8R, there was a firmware setting that could be reached through a service menu/backdoor, which would change the frequency ranges it would tx on. I believe the purpose was changing the region. Doing this changed the model number that was reported by the radio for the clone interface and would cause all of the settings to be reset (so the radio lost all programming).
Are you sure you're not thinking of the VX7? What you describe is exactly how it works for that radio, but the VX8 makes a departure from the three-block protocol that the 7 (and others of that vintage) use. The block missing is the one with the mods in it.
Rick did some work on the VX3 trying to figure out the soft mod but I'm not aware that anything ever came of it. Personally, I think its likely that Yaesu didn't carry that "feature" forward past the VX5/7 days.
For what is worth looking at vx6tool.c, the vx6 could be freebanded by changing two bytes looks like offset 8& 9.
Yep, the 2,5,6, and 7 all have that one block in between the header and the memory data, but the 3 and 8 do not (which is the source of my skepticism)
I am familiar with the mods for 2, 5, and 7. I'm not personally familiar with the 6 mod, but if you say it is possible I'm sure it is very similar to the others.
VX3 and VX8* are rather similar in that the really convenient mod interface is definately gone. I'm not saying it isn't possible, but I need someone to take a clone of their radio before and after hardmod/reset as I am not comfortable modding my VX3 (I really suck at soldering).
-Rick
On whether mods in terms of freebanding should be part of a general settings interface -- my inclination is to say no, especially from the user interface point of view.
Aside from the obvious liability issues, if changing the frequency ranges causes radios like the vx-8 do a full reset, it would be problematic for the user, they'd probably have to download to the radio multiple times, there is currently no backup or manipulation of the regular settings through chirp. I'd rather see the frequency range settings done through a separate UI even though it probably shares most of the code/models of the radio underneath.
Hmm, well, I'm not too worried about the liability issues. I certainly plan to throw up a huge blinking buzzing warning about doing something to your radio that you might regret.
I think that it will be fairly easy to re-use the same key/value mechanism underneath the covers without making the UI (for settings and mods) a big mess of knobs. That's what I meant about using this system for generic settings and mods. It will definitely need a little augmentation to allow it to be organized.
Thanks for the feedback!
On 4/7/2011 12:09 AM, Richard Farina wrote:
On 04/06/11 23:48, Dan Smith wrote:
Are you sure you're not thinking of the VX7? What you describe is exactly how it works for that radio, but the VX8 makes a departure from the three-block protocol that the 7 (and others of that vintage) use. The block missing is the one with the mods in it.
...
I'm not personally > familiar with the 6 mod, but if you say it is possible I'm sure it is very similar to the others.
...
VX3 and VX8* are rather similar in that the really convenient mod interface is definately gone. I'm not saying it isn't possible, but I need someone to take a clone of their radio before and after hardmod/reset as I am not comfortable modding my VX3 (I really suck at soldering).
Ok thanks for filling in some of the background info for me. I didn't know if that piece of memory was available or not and didn't have the background - the vx8 was my first radio. Also as I noted in my original msg to Dan, the software mod that worked through the backdoor on the VX-8R apparently has been removed from the VX-8DR.
What I saw about the vx6 was from vx6tool.c, which was the first piece of OSS I came across for Yaesu VX's (and I used to figure out how to download/upload my vx8's memory). vx6tool is available here:
http://lategahn.2log.de/index.php?yaesu-vx6-command-line-utility
Also as I noted in my original msg to Dan, the software mod that worked through the backdoor on the VX-8R apparently has been removed from the VX-8DR.
I had one of the original VX-8 radios and it didn't have the magic middle block that the 5,6,7 radios do, just for what it's worth. However, it's entirely possible that the switches are buried elsewhere.
There's definitely a H/W mod option for the VX-8r for MARS type use.
http://www.kb2ljj.com/data/yaesu/VX-8R.htm
This claims to document a soft mod that's accessible via magic key combinations but I don't know that it necessarily involves memory that's exported in a clone
On Fri, Apr 8, 2011 at 6:51 AM, Dan Smith dsmith@danplanet.com wrote:
Also as I noted in my original msg to Dan, the software mod that worked through the backdoor on the VX-8R apparently has been removed from the VX-8DR.
I had one of the original VX-8 radios and it didn't have the magic middle block that the 5,6,7 radios do, just for what it's worth. However, it's entirely possible that the switches are buried elsewhere.
-- Dan Smith www.danplanet.com KK7DS
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
There's definitely a H/W mod option for the VX-8r for MARS type use.
Yep, I had done it to my original 8R. When I got it back from Yaesu after the 8DR upgrade, they put the resistor back :)
http://www.kb2ljj.com/data/yaesu/VX-8R.htm
This claims to document a soft mod that's accessible via magic key combinations but I don't know that it necessarily involves memory that's exported in a clone
I forgot about this entirely until just now. I had tried it once upon a time and didn't get it to work.
If, however, it does, then maybe we could use that to figure out where (if at all) it's triggered in the memory. The string you type in (AH029) is, by the way, the model identifier that the PC and radio exchange during a clone. So, we should know it for other radios as well, such as the VX3. Might be worth a shot.
http://www.kb2ljj.com/data/yaesu/VX-8R.htm
This claims to document a soft mod that's accessible via magic key combinations but I don't know that it necessarily involves memory that's exported in a clone
I forgot about this entirely until just now. I had tried it once upon a time and didn't get it to work.
Yes, that is what I was referring to as to a backdoor that was available for the -8R, but stopped working for the -8DR even after using AH29D instead of AH029 as the identifier for the VX-8DR.
Some people reported that it also didn't work after removing the resistor, but I never understood why you would try it or need it after doing the h/w mod....
If, however, it does, then maybe we could use that to figure out where (if at all) it's triggered in the memory.
Yes, the before and after from an original -8R not an -8DR would certainly be helpful.
btw, Anyone ever compare the dump of a freshly reset (non-US) VX-8E to a (US) VX-8R for obvious differences?
On 04/07/11 17:59, Dan Smith wrote:
There's definitely a H/W mod option for the VX-8r for MARS type use.
Yep, I had done it to my original 8R. When I got it back from Yaesu after the 8DR upgrade, they put the resistor back :)
http://www.kb2ljj.com/data/yaesu/VX-8R.htm
This claims to document a soft mod that's accessible via magic key combinations but I don't know that it necessarily involves memory that's exported in a clone
I forgot about this entirely until just now. I had tried it once upon a time and didn't get it to work.
If, however, it does, then maybe we could use that to figure out where (if at all) it's triggered in the memory. The string you type in (AH029) is, by the way, the model identifier that the PC and radio exchange during a clone. So, we should know it for other radios as well, such as the VX3. Might be worth a shot.
The magic menu stuff has at best left the radio unchanged and at worst found some rather unpleasant settings which can damage the radio. Mind you I'm lumping all the magic menu hacks together here, but still, I've never found one that works.
Though anyone with the scruples to hardmod their radio I would love a hardreset/clone before and after image.
-Rick
participants (4)
-
Dan Smith -
Grant Diffey -
Richard Farina -
Robert Terzi