[chirp_devel] VX2r stuff

[Andrew Errington]

Hi everyone,

So far I have these fields decoding successfully:

# mode
# duplex
# freq
# power
# tmode
# name
# offset

I'm a little worried because when I change a single property of a single 
memory I get a large number of changes in the memory file.  For example, if I 
change only one channel from high power to low power I get about 37 bytes 
affected.  I expected to see only two or three (the byte that records the 
power level, and the checksum).

'tune_step' might be working, but I'm not sure, and I need to work on 'tone' 
and 'dcs'.

I think I should have started with the VX3 code instead of VX7, but I just 
copy stuff from VX3 anyway.  I am focusing on decoding the memory image.  I 
haven't done anything to the code that writes a modified memory image.

Finally, I seem to have a problem where occasionally I get or lose a null byte 
at the beginning of the file, which of course messes up the byte count.  I 
think I should get "\x00AHN015" but sometimes I just get "AHN015".

That's all for now.  I guess there won't be a patch as the VX2r is a new 
program file.  I'll send the whole thing when I'm done, or I can send the 
current horribly broken mess to anyone who wants to look at it.

73,

Andrew
ZL3AME