<div dir="ltr">Yeah, that sounds reasonable. If it's a checkbox that means it just needs to store checked or unchecked, so two values, so a single bit. It's pretty common to use a single byte to store multiple values like that.<div><br></div><div>If your interpretation is correct, one question left would be what they mean by the "second bit" for example. In an 8-bit byte, is it the second from the left (high-order bit, but this is how you'd read it when looking at the byte written out) or the second from the right (starting with the smallest value you can represent in a bit, going up as you use more bits). In this case, using hex, a byte with just the second bit from the left set is 0x40, and a byte with just the second bit from the right set is 0x02.</div><div><br></div><div>Once you identify which bit it is, you can easily check if that bit is set using some simple bit operations. For example, for byte b, to check if b has the second bit from the left set: (b & 0x40) == 0x40.</div><div><br></div><div>Back to your original post, f3 = 1111 0011, so if b2/b3 are from the left, both bits are set. If they're from the right, b2 = 2, b3 = 0. That may help if you know what the values are supposed to be.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 24, 2018 at 6:04 PM, Rob Owens <span dir="ltr"><<a href="mailto:robowens13@gmail.com" target="_blank">robowens13@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I asked what memory address stores the "Functiom Enable" feature. <br><br>In the OEM software, that checkbox is right next to the "Wireless Start" checkbox, but I don't quite understand how they're related. Both are in the "Wireless Change Channel" box in the GUI. <br><br></div>Thanks, I know I should probably ask them for clarification and I may do that. But I needed a little assurance that I was asking something reasonable.<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 24, 2018 at 8:41 PM, Rhett Robinson <span dir="ltr"><<a href="mailto:rrhett@gmail.com" target="_blank">rrhett@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">What was the question to which that was the vendor's response? I don't really know how to interpret that without a bit more context, sorry. Saying B3 refers to the third bit is plausible.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 24, 2018 at 12:44 PM, Rob Owens via chirp_devel <span dir="ltr"><<a href="mailto:chirp_devel@intrepid.danplanet.com" target="_blank">chirp_devel@intrepid.danplane<wbr>t.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks. So here's a follow-up question. Here is the vendor's response, verbatim: "0x0187，B3：Wirelsee start,B2:function enable". Do you suppose the B3 and B2 refer to the third and second bits within the 0x0187 byte? Is that typical notation?<br></div><div class="m_-8543760457622257717m_-3440148987202096009HOEnZb"><div class="m_-8543760457622257717m_-3440148987202096009h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 24, 2018 at 2:34 PM, Rhett Robinson <span dir="ltr"><<a href="mailto:rrhett@gmail.com" target="_blank">rrhett@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yes, hexdump prints each line as 16 bytes: two blocks of 8 bytes each, beginning with the address of the first byte. So, in your example:<div><span style="font-size:12.8px">00000180 63 ff ff ff 32 ff ec f3 f2 87 44 03 14 23 01 01 |c...2.....D..#..|</span><br style="font-size:12.8px"></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">The first byte, 63 is at 0x180. The second byte, ff is at 0x181. The 7th byte, at address 0x187, is f3. After that it is f2 at 0x188, 87 at 0x189, 44 at 0x18a through 01 at 0x18f. So each block will be 0x???0 through 0x???f.</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Hope that helps!</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Rhett</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 24, 2018 at 11:13 AM, Rob Owens via chirp_devel <span dir="ltr"><<a href="mailto:chirp_devel@intrepid.danplanet.com" target="_blank">chirp_devel@intrepid.danplane<wbr>t.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Here are two consecutive lines from a 'hexdump -C' of a Chirp image:<br><br>00000180 63 ff ff ff 32 ff ec f3 f2 87 44 03 14 23 01 01 |c...2.....D..#..|<br>00000190 0f 37 1d 65 05 f0 fc d3 00 0a 0a 00 3c 00 e3 3c |.7.e........<..<|<br><br></div>Based on information from the radio vendor (Leixen), I am interested in memory address 0x0187. <br></div></div>Is that the "f3" byte?<br><br></div>I understand the concept of different base numbering systems, but I'm rusty. And I'm brand new to this Chirp driver stuff...<span class="m_-8543760457622257717m_-3440148987202096009m_-8060272378872420208m_9110361972129114555HOEnZb"><font color="#888888"><br><br></font></span></div><span class="m_-8543760457622257717m_-3440148987202096009m_-8060272378872420208m_9110361972129114555HOEnZb"><font color="#888888">-Rob<br></font></span></div>
<br>______________________________<wbr>_________________<br>
chirp_devel mailing list<br>
<a href="mailto:chirp_devel@intrepid.danplanet.com" target="_blank">chirp_devel@intrepid.danplanet<wbr>.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_devel</a><br>
Developer docs: <a href="http://chirp.danplanet.com/projects/chirp/wiki/Developers" rel="noreferrer" target="_blank">http://chirp.danplanet.com/pro<wbr>jects/chirp/wiki/Developers</a><br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
chirp_devel mailing list<br>
<a href="mailto:chirp_devel@intrepid.danplanet.com" target="_blank">chirp_devel@intrepid.danplanet<wbr>.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_devel</a><br>
Developer docs: <a href="http://chirp.danplanet.com/projects/chirp/wiki/Developers" rel="noreferrer" target="_blank">http://chirp.danplanet.com/pro<wbr>jects/chirp/wiki/Developers</a><br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>