[chirp_devel] FT817ND

[Dan Smith]

> Good news are I'm looking at my ft817 _ND_ memories in chirp :)

Nice!

> Please Dan, there are two things I don't know how to arrange: - seems
> that "PKT" mode is not in common.MODES, may I add it?

So, you're bumping up against something that has needed some maintenance
for some time. When CHIRP started out, it was rather ICOM-specific and
so several of those drivers still index directly into the global
definitions of the modes to convert something like "0x3" to "FM". If we
change those then they will break.

The short answer is: if you add "PKT" to the end of the list then you
should be safe for now. However, we need to move to radios declaring
their modes in valid_modes and indexing into *that* list instead.

The tuning steps have the same problem, of course. You can see that I
recently added 9.0 to the end of that list as well when hitting the same
sort of problem.

> - radio has different valid steps for FM, AM, SSB; how I can arrange
> for them to set valid_tuning_steps in get_features?

I think you'll need to declare all of the steps that the radio supports 
in valid_tuning_steps and then check in your set_memory() handler to 
make sure they're using a valid combination.

I wouldn't be opposed to changing valid_tuning_steps to look something 
like this:

   valid_tuning_steps = {"FM" : [5.0, 10.0, ...],
                         "AM" : [5.0, 9.0, ...],
                         ... }

However, that gives us the same problem of needing to update all the old 
drivers as well. If we can agree on these changes, then I can go through 
and manually update the drivers, but I don't want to do that more than 
once if I can help it :)

-- 
Dan Smith
www.danplanet.com
KK7DS