Hi,

I've added IARU region 3 and added it as a parent for Australian Amateur.

While adding IARU region 3 I noticed a few bugs in the original patch:

- a typo in the code that builds the bands tree resulted in misplaced items.

- IARU region 2 had CW spanning 24.89-29.15 rather than 24.89-24.915

I've also added a debug function to print the bands tree structure (chirpui/bandplans.py PrintBandPlan())

N2NOV, I've found a US amateur band plan. It supplies channel step and mode, which will be reflected in the defaults once I've incorporated it into bandplan_na.py:

http://www.arrl.org/band-plan

On Wed, Mar 27, 2013 at 12:54 PM, Sean Burford <sburford@google.com> wrote:

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@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@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers

--

Sean Burford <sburford@google.com>

Sean Burford <sburford@google.com>