<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I used the label-encoding code straight from the ftm3200d. It worked correctly right off the bat. (so far, I’ve commented away the rest of the 3200d code.)<div class="">Thanks, Wade.</div><div class=""><br class=""></div><div class="">Now for the memory banks: those data are at a different offset than in the FT-1D.</div><div class=""><br class=""></div><div class="">BTW, I’ve also got development working directly in Mac OS X. I plan to write up the few things I needed to do so it can be included in the OS X-centric instructions on the development site (unless others have already done so or if it’s intuitively obvious to the rest of the world.)</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 24, 2017, at 19:45, Wade Simmons <<a href="mailto:wade@wades.im" class="">wade@wades.im</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Look at how the ftm3200d driver extends the FT1D one and uses ascii for encoding instead of the custom format the ft1d does. You can probably do the same thing.</span><br class="Apple-interchange-newline"></div></blockquote></div><br class=""></div></body></html>