<html><head></head><body><div style="color:#000; background-color:#fff; font-family:lucida console, sans-serif;font-size:16px"><div id="yui_3_16_0_ym18_1_1459616500741_9336"><span id="yui_3_16_0_ym18_1_1459616500741_9341">Just a few cents here from memory (which might not be worth much over time-depreciation ;)</span></div><div id="yui_3_16_0_ym18_1_1459616500741_9357"><br></div><div id="yui_3_16_0_ym18_1_1459616500741_10165"><b id="yui_3_16_0_ym18_1_1459616500741_10168">long:</b><br><span id="yui_3_16_0_ym18_1_1459616500741_9341"></span></div><div id="yui_3_16_0_ym18_1_1459616500741_9372"><span id="yui_3_16_0_ym18_1_1459616500741_9341">I recall from playing with several yaesu radios (VX-2/3/6/170?,FT-90,FT-7900) that the memory layouts and protocols were quite similar.</span></div><div id="yui_3_16_0_ym18_1_1459616500741_9389">They usually started with some ident (ascii?) string, e.g. AH017$, whch identified the model class, e.g. VX-2 vs VX-3.</div><div id="yui_3_16_0_ym18_1_1459616500741_9433">That was followed by a few bytes (1-3 or 4 cant recall exactly), which seemed to indicate either the regional variation (EU vs US), and also if it was "modded" or stock. I want to say that the first byte might have been a direct result of the jumper configuration (which I think also had to do with the regional setting and mods). Let's call this the "feature bits". <br></div><div dir="ltr" id="yui_3_16_0_ym18_1_1459616500741_9553"><br></div><div id="yui_3_16_0_ym18_1_1459616500741_9698" dir="ltr">Note that whenever you changed jumpers, you were supposed to default/reset the radio, in order for the change to
take effect. (It seemed that the radio used the feature bits in the running image, not the jumper settings, and the jumper settings were only transferred to running image during a default.) So after changing jumpers, defaulting, and downloading,
some of those feature bits in the image would change. I attempted to exploit this, as I was trying to find a way to "soft-mod" the radio by tweaking these bits in the image, however the radio would not accept the image with the modded bits (if they did not match the bits in the running radio image).</div><div id="yui_3_16_0_ym18_1_1459616500741_9746" dir="ltr"><br></div><div id="yui_3_16_0_ym18_1_1459616500741_9601" dir="ltr">The result of this was that the radio would refuse to accept a clone image which was previously made from that same radio after you changed the jumper settings (and defaulted).</div><div id="yui_3_16_0_ym18_1_1459616500741_9921" dir="ltr"><br></div><div id="yui_3_16_0_ym18_1_1459616500741_9983" dir="ltr">So what this means for chirp interaction is that although the model id was the same, there differences in the features, and they are not portable between direct images. As with other radios, the best pattern is to pull a fresh image from the radio, and import the channels from previous image of the radio.</div><div id="yui_3_16_0_ym18_1_1459616500741_10048" dir="ltr"><br></div><div id="yui_3_16_0_ym18_1_1459616500741_10004" dir="ltr">You might also be able to detect the capabilities of the radio by looking at these feature bits (e.g. frequency range of EU vs US, unlocked, etc).</div><div id="yui_3_16_0_ym18_1_1459616500741_10095" dir="ltr"><br></div><div id="yui_3_16_0_ym18_1_1459616500741_10145" dir="ltr"><b id="yui_3_16_0_ym18_1_1459616500741_10160">short:</b><br></div><div id="yui_3_16_0_ym18_1_1459616500741_10096" dir="ltr">The summary is that I dont think you need to treat the variants of a radio model for Yaesu as separate models in chirp.</div><div id="yui_3_16_0_ym18_1_1459616500741_10125" dir="ltr">I think these feature bits are just attributes of model capabilities.<br></div><div id="yui_3_16_0_ym18_1_1459616500741_9373" class="qtdSeparateBR"><br><div id="yui_3_16_0_ym18_1_1459616500741_10199">-Jens</div><div id="yui_3_16_0_ym18_1_1459616500741_10200"><br></div></div><div style="display: block;" id="yui_3_16_0_ym18_1_1459616500741_9696" class="yahoo_quoted"> <div id="yui_3_16_0_ym18_1_1459616500741_9695" style="font-family: lucida console, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_ym18_1_1459616500741_9694" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_ym18_1_1459616500741_9693" dir="ltr"> <font id="yui_3_16_0_ym18_1_1459616500741_9985" face="Arial" size="2"> <hr id="yui_3_16_0_ym18_1_1459616500741_9984" size="1"> <b><span style="font-weight:bold;">From:</span></b> Dan Smith via chirp_devel <chirp_devel@intrepid.danplanet.com><br> <b><span style="font-weight: bold;">To:</span></b> <br><b><span style="font-weight: bold;">Cc:</span></b> chirp_devel@intrepid.danplanet.com<br> <b><span style="font-weight: bold;">Sent:</span></b> Friday, April 1, 2016 3:25 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [chirp_devel] [PATCH] [FT2900] Add support for settings. Fix #2867<br> </font> </div> <div id="yui_3_16_0_ym18_1_1459616500741_10093" class="y_msg_container"><br>> For clarification, the patch quoted below is the one that added support<br clear="none">> of settings to all of the FT1900/FT2900 series, and I don’t believe that<br clear="none">> particular patch is what was causing the problem. I suspect you’re<br clear="none">> talking about another submission, which added support for a modded<br clear="none">> version of the FT2900. That was submitted in a similar timeframe, and<br clear="none">> is here:<br clear="none">> <a shape="rect" href="http://chirp.danplanet.com/projects/chirp/repository/revisions/1c398653986f" target="_blank">http://chirp.danplanet.com/projects/chirp/repository/revisions/1c398653986f </a><br clear="none"><br clear="none">Yep, sorry, my bad :)<br clear="none"><br clear="none">> I’m now digging through the logic in that test. It’s not obvious to me<br clear="none">> how adding the support of a modified radio is different from adding<br clear="none">> support of a European version of the FT-2900/FT-1900 radio, which was<br clear="none">> done a long time ago (a year or more? I don’t remember, but it was long<br clear="none">> ago). In both cases, we didn’t add a new .img file to the test cases,<br clear="none">> there was just a new class added with the same settings overridden.<br clear="none"><br clear="none">Because the euro version has a different ident string or something.<br clear="none">We've got to be able to detect which model class to use from the file<br clear="none">when we open it. Some radios do that by file size, while others look at<br clear="none">some identification bytes inside. Some a combination of both.<br clear="none"><br clear="none">If the mod bits are stored in the file anywhere, then you can just<br clear="none">modify both classes to look at the mod bytes and return the appropriate<br clear="none">match. Right now the class uses file size only:<br clear="none"><br clear="none"><a shape="rect" href="http://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/ft2900.py#L1207" target="_blank">http://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/ft2900.py#L1207</a><br clear="none"><br clear="none">If you look at a couple other examples in other files you'll see some of<br clear="none">the more complicated ones.<br clear="none"><br clear="none">> Anyway, I’ve got to step away from the computer for a while right now,<br clear="none">> but I just wanted to let you know I’ll be digging into this.<br clear="none"><br clear="none">No problem, thanks much!<div class="yqt3184717347" id="yqtfd60764"><br clear="none"><br clear="none">--Dan<br clear="none">_______________________________________________<br clear="none">chirp_devel mailing list<br clear="none"><a shape="rect" ymailto="mailto:chirp_devel@intrepid.danplanet.com" href="mailto:chirp_devel@intrepid.danplanet.com">chirp_devel@intrepid.danplanet.com</a><br clear="none"><a shape="rect" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel</a><br clear="none">Developer docs: <a shape="rect" href="http://chirp.danplanet.com/projects/chirp/wiki/Developers" target="_blank">http://chirp.danplanet.com/projects/chirp/wiki/Developers</a></div><br><br></div> </div> </div> </div></div></body></html>