<div dir="ltr">Hi,<div><br></div><div>Please find attached a patch to add band plans. It replaces "Automatic Repeater Offsets".</div><div><br></div><div>When you have a band plan selected and you modify a frequency, the band plan code looks up the frequency and sets:</div>
<div style> - The default mode.</div><div style> - The default repeater offset.</div><div style> - The default tune step.</div><div style>There is also support in the band plan for tones, but it isn't plumbed through yet.</div>
<div style><br></div><div>You can select multiple plans because, for example, you might want both an IARU plan and a country plan.<br><div><br></div><div style>chirpui/bandplans.py is the API for accessing band plans. chirp/bandplan_*.py are the technical details of each band plan. bandplans.py is in the UI directory because it deals with config, which appears to be used exclusively from the chirpui directory.<br>
</div><div style><br></div><div style>The format in bandplan_au.py is the format I prefer. The format in bandplan_na.py is carried over from chirp_common.py and should be replaced by the new format once we agree on how it should look.<br>
</div><div><br></div><div>I've left placeholders for the IARU band plans (eg. <a href="http://www.iaru-r2.org/band-plan/">http://www.iaru-r2.org/band-plan/</a>). We can add them to the UI once they have been populated.</div>
<div><br></div><div style>While testing this I noticed that there are multiple instances of the config class, with different and overlapping lifetimes. This means that sometimes configuration changes are applied and sometimes they are not. That is a separate issue.</div>
<div><br></div>-- <br><div><span style="color:rgb(102,102,102)">Sean Burford <<a href="mailto:sburford@google.com" target="_blank">sburford@google.com</a>></span></div>
</div></div>