[chirp_devel] Patch for #681: Add support for band plans

Sean Burford
Tue Mar 26 18:54:28 PDT 2013


Hi,

I've attached a revised patch.

Band plans (chirp/bandplan_*.py) contain some information to help with
maintenance (source URL, version) and after that they are basically flat
lists of Band instances.  Band instances can suggest modes, tuning steps,
tones, duplex offsets, etc.  You can reuse one band plan in another using
the + operator (eg. bandplan_na imports bandplan_iaru_r2)

chirp/bandplan.py defines the Band class and the BandTree class.  These are
distinct because the same Band may be in multiple BandTrees.  A BandTree is
just an optimised way of applying properties of wider bands to sub bands
within them, as implemented in the search() function.

chirpui/bandplans.py handles all of the band plans on behalf of the user
interface.  When you add a band plan you just create bandplan_whatever.py
and then add it to this file.

chirpui/mainapp.py has been modified to make channel defaults selection a
pop up with a single select drop down (populated from
chirpui/bandplans.py).  To simplify conflict resolution I've flipped from
multiple selection to single selection.  I figure that if you go from
adding amateur channels to adding marine channels you can select a
different band plan when you start on the marine channels.

Users won't notice any immediate change except that the default (North
America) now has some HF band defaults (eg. AM mode for 14.29MHz)



On Wed, Mar 13, 2013 at 1:05 PM, Dan Smith <dsmith at danplanet.com> wrote:

> > Yes, however a North American Marine band plan and a North American
> > Amateur band plan would both be under an ITU region 2 band plan, and
> > you might want to use both.
>
> Hrm, bummer, okay.
>
> > You're right.  I'll try it with objects and see how it looks.  I
> > expect that will make it easier to calculate and claim the repeater
> > input blocks too (with opposite offsets).
>
> Cool, thanks!
>
> > I've filed bug #683
>
> Thanks! I just sent a patch for this, let me know if it resolves it for
> you. It's actually silly internal logic and not related to config
> objects. Nice catch :)
>
> --
> Dan Smith
> www.danplanet.com
> KK7DS
>
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>



-- 
Sean Burford <sburford at google.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20130327/99af7207/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bands.patch
Type: application/octet-stream
Size: 36555 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20130327/99af7207/attachment-0001.obj 


More information about the chirp_devel mailing list