<br><br><div class="gmail_quote">On Sun, Feb 24, 2013 at 2:45 PM, Dan Smith <span dir="ltr"><<a href="mailto:dsmith@danplanet.com" target="_blank">dsmith@danplanet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">> struct {<br>
> + u8 code222[3];<br>
> + u8 unused222[2];<br>
> + u8 code333[3];<br>
> + u8 unused333[2];<br>
> + u8 alarmcode[3];<br>
> + u8 unused119[2];<br>
> + u8 unknown1;<br>
> + u8 code555[3];<br>
> + u8 unused555[2];<br>
> + u8 code666[3];<br>
> + u8 unused666[2];<br>
> + u8 code777[3];<br>
> + u8 unused777[2];<br>
> + u8 unknown2;<br>
> + u8 code60606[5];<br>
> + u8 code70707[5];<br>
<br>
</div>Just so I'm clear, are you adding the other elements here and planning<br>
to use them later (i.e. everything other than alarmcode).<br>
<span class="HOEnZb"><font color="#888888"></font></span><br></blockquote></div>Dan,<br>That's a valid question. I debated about this myself and probably should have asked your opinion about it.<br><br>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.<br>
<br>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?<br>Jim<br>