[chirp_devel] [PATCH] [uv-b5] fix for proper display of STEP setting value

Jim Unroe
Sun Oct 20 13:18:09 PDT 2013


Dan,


>   VALID_STEPS = [5.0, 6.25, 10.0, 12.5, 20.0, 25.0]
>
>   def get_features(self):
>       ...
>       rf.valid_tuning_steps = VALID_STEPS
>       rf.has_tuning_step = True
>

I pretty much have this working except for one thing. The drop-down list of
steps available appears to be the common list of steps built into CHIRP:

TUNING_STEPS = [
    5.0, 6.25, 10.0, 12.5, 15.0, 20.0, 25.0, 30.0, 50.0, 100.0,
    125.0, 200.0,
    # Need to fix drivers using this list as an index!
    9.0, 1.0, 2.5,
]

I tried the only other driver that has "rf.has_tuning_step = True" and it
does the same thing. Is this a CHIRP bug or am I doing something wrong?

I suppose I could leave it "rf.has_tuning_step = False" since the user has
no real need to use tuning steps on the UV-B5 when programming with CHIRP.
But I'll wait to see what you have to say about it.

Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20131020/7d5dff0c/attachment-0001.html 


More information about the chirp_devel mailing list