<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Yeah, I’ll take a look. <div class=""><br class=""><div class="">For clarification, the patch quoted below is the one that added support of settings to all of the FT1900/FT2900 series, and I don’t believe that particular patch is what was causing the problem. I suspect you’re talking about another submission, which added support for a modded version of the FT2900. That was submitted in a similar timeframe, and is here: <a href="http://chirp.danplanet.com/projects/chirp/repository/revisions/1c398653986f" class="">http://chirp.danplanet.com/projects/chirp/repository/revisions/1c398653986f</a> </div><div class=""><br class=""></div><div class="">I’m now digging through the logic in that test. It’s not obvious to me how adding the support of a modified radio is different from adding support of a European version of the FT-2900/FT-1900 radio, which was done a long time ago (a year or more? I don’t remember, but it was long ago). In both cases, we didn’t add a new .img file to the test cases, there was just a new class added with the same settings overridden.</div><div class=""><br class=""></div><div class="">Anyway, I’ve got to step away from the computer for a while right now, but I just wanted to let you know I’ll be digging into this.</div><div class=""><br class=""><div apple-content-edited="true" class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Richard Cochran</div><div class=""><a href="mailto:ag6qr@sonic.net" class="">ag6qr@sonic.net</a></div><div class=""><br class=""></div><div class="">Sent from my Nye Viking Speed-X</div><div class=""><br class=""></div></div></span><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Apr 1, 2016, at 12:32 PM, Dan Smith <<a href="mailto:dsmith@danplanet.com" class="">dsmith@danplanet.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><blockquote type="cite" class=""># HG changeset patch<br class=""># User Richard Cochran <<a href="mailto:ag6qr@sonic.net" class="">ag6qr@sonic.net</a>><br class=""># Date 1456721059 28800<br class=""># Sun Feb 28 20:44:19 2016 -0800<br class=""># Node ID 432300d60fae4c517c8f98f3d52aef115c9a96e8<br class=""># Parent 1c398653986fb3e0a50bfbbc58f1a2f5c9ab2b95<br class="">[FT2900] Add support for settings. Fix #2867<br class="">This submission adds support for settings to the ft-2900/ft-1900 driver.<br class="">Special thanks to Chris Fosnight for getting a start at the settings code.<br class="">He gave his code to me (Rich Cochran), and I finished implementing more<br class="">settings, and tested both reading and writing of all the settings.<br class="">Settings are grouped into categories according to the manual, pp 72-73.<br class=""></blockquote><br class="">I didn't notice this until now, but this brought the current failure<br class="">we're seeing. The 2900 and 2900Mod radios are not distinguishable for<br class="">file detection.<br class=""><br class="">Can you figure out some way to do that so we can get the tests fixed up?<br class=""><br class="">Thanks!<br class=""><br class="">--Dan<br class=""><br class=""></div></blockquote></div><br class=""></div></div></body></html>