[chirp_devel] [PATCH] [uv5r] Add setting to allow editing the 'Alarm Code' value

[Jim Unroe]

On Sun, Feb 24, 2013 at 2:45 PM, Dan Smith <dsmith at danplanet.com> wrote:

> >  struct {
> > +  u8 code222[3];
> > +  u8 unused222[2];
> > +  u8 code333[3];
> > +  u8 unused333[2];
> > +  u8 alarmcode[3];
> > +  u8 unused119[2];
> > +  u8 unknown1;
> > +  u8 code555[3];
> > +  u8 unused555[2];
> > +  u8 code666[3];
> > +  u8 unused666[2];
> > +  u8 code777[3];
> > +  u8 unused777[2];
> > +  u8 unknown2;
> > +  u8 code60606[5];
> > +  u8 code70707[5];
>
> Just so I'm clear, are you adding the other elements here and planning
> to use them later (i.e. everything other than alarmcode).
>
> Dan,
That's a valid question. I debated about this myself and probably should
have asked your opinion about it.

I considered making another structure for just the alarm code. But this
area of memory is what I call the ANI block. It definitely has other set of
codes within this block. But at this point I don't if the UV-5R is even
capable of using them. If I discover how to use them, sure I will add those
to the list of features.

What you you rather see? 'alarmcode' flanked by large unknowns or a
separate structure until a usefulness for the rest of the memory locations
can be established?
Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20130224/d7bb84f2/attachment-0001.html