[chirp_devel] [PATCH 0 of 6] Fixes for rf.valid_tuning_steps
# HG changeset patch # User Jim Unroe rock.unroe@gmail.com # Date 1575405270 18000 # Node ID d24f8e02a31f9f49931be895a2c179d53c5bc1a1 # Parent 08f9cc4320194da261c9b804b943accc9428fc8f Fix Yaesu FTM-350 tuning steps
fixes #6639
diff -r 08f9cc432019 -r d24f8e02a31f chirp/drivers/ftm350.py --- a/chirp/drivers/ftm350.py Tue Dec 03 13:30:33 2019 -0500 +++ b/chirp/drivers/ftm350.py Tue Dec 03 15:34:30 2019 -0500 @@ -265,6 +265,9 @@ (76000000, 250000000), (30000000, 1000000000)] rf.can_odd_split = True + rf.valid_tuning_steps = [5.0, 6.25, 8.33, 10.0, 12.5, 15.0, 20.0, + 25.0, 50.0, 100.0, 200.0] + return rf
def get_sub_devices(self):
# HG changeset patch # User Jim Unroe rock.unroe@gmail.com # Date 1575406486 18000 # Node ID 01abbbc13a018bdfdfa7368e7ad40b6a08267806 # Parent d24f8e02a31f9f49931be895a2c179d53c5bc1a1 Fix Radioddity R2 tuning steps
fixes #6743
diff -r d24f8e02a31f -r 01abbbc13a01 chirp/drivers/radioddity_r2.py --- a/chirp/drivers/radioddity_r2.py Tue Dec 03 15:34:30 2019 -0500 +++ b/chirp/drivers/radioddity_r2.py Tue Dec 03 15:54:46 2019 -0500 @@ -350,6 +350,7 @@ rf.valid_skips = [] rf.valid_bands = [self._range] rf.memory_bounds = (1, self._upper) + rf.valid_tuning_steps = [2.5, 5.0, 6.25, 10.0, 12.5, 25.0] return rf
def process_mmap(self):
# HG changeset patch # User Jim Unroe rock.unroe@gmail.com # Date 1575407086 18000 # Node ID 4decba7bfca2a6fd8aeab981eccf56a4de77ffe7 # Parent 01abbbc13a018bdfdfa7368e7ad40b6a08267806 Fix Yaesu FT-4 valid steps
Should also fix FT-25, FT-35 and FT-65.
fixes #6807
diff -r 01abbbc13a01 -r 4decba7bfca2 chirp/drivers/ft4.py --- a/chirp/drivers/ft4.py Tue Dec 03 15:54:46 2019 -0500 +++ b/chirp/drivers/ft4.py Tue Dec 03 16:04:46 2019 -0500 @@ -669,6 +669,7 @@ rf.has_dtcs_polarity = False # REV TN reverses the tone, not the dcs rf.has_cross = True rf.has_settings = True + rf.valid_tuning_steps = self.legal_steps
return rf
# HG changeset patch # User Jim Unroe rock.unroe@gmail.com # Date 1575408698 18000 # Node ID 1fb51f2fced1a2cb2a0910a8673b634d0269e629 # Parent 4decba7bfca2a6fd8aeab981eccf56a4de77ffe7 Fix Puxing PX-888K tuning steps
fixes #6887
diff -r 4decba7bfca2 -r 1fb51f2fced1 chirp/drivers/puxing_px888k.py --- a/chirp/drivers/puxing_px888k.py Tue Dec 03 16:04:46 2019 -0500 +++ b/chirp/drivers/puxing_px888k.py Tue Dec 03 16:31:38 2019 -0500 @@ -1143,6 +1143,7 @@ rf.valid_cross_modes = CROSS_MODES rf.memory_bounds = (1, 128) rf.valid_special_chans = SPECIAL_CHANNELS.keys() + rf.valid_tuning_steps = [5.0, 6.25, 10.0, 12.5, 25.0] return rf
def sync_in(self):
# HG changeset patch # User Jim Unroe rock.unroe@gmail.com # Date 1575409568 18000 # Node ID 19016d47dec8c8c7788e3120f7b7e4324e68085c # Parent 1fb51f2fced1a2cb2a0910a8673b634d0269e629 Fix Kenwood TM-D700 tuning steps
fixes #7053
diff -r 1fb51f2fced1 -r 19016d47dec8 chirp/drivers/kenwood_live.py --- a/chirp/drivers/kenwood_live.py Tue Dec 03 16:31:38 2019 -0500 +++ b/chirp/drivers/kenwood_live.py Tue Dec 03 16:46:08 2019 -0500 @@ -575,6 +575,8 @@ rf.valid_characters = chirp_common.CHARSET_ALPHANUMERIC rf.valid_name_length = 8 rf.memory_bounds = (1, self._upper) + rf.valid_tuning_steps = [5.0, 6.25, 10.0, 12.5, 15.0, 20.0, 25.0, + 30.0, 50.0, 100.0] return rf
def _make_mem_spec(self, mem):
# HG changeset patch # User Jim Unroe rock.unroe@gmail.com # Date 1575409568 18000 # Node ID 19016d47dec8c8c7788e3120f7b7e4324e68085c # Parent 1fb51f2fced1a2cb2a0910a8673b634d0269e629 Fix Kenwood TM-D700 tuning steps
fixes #7053
Gah, sorry Jim! I was literally doing some work on the D700 in the last couple of days. I just pushed those, including a fix for tuning_steps, then said "oh, I better go apply that set from Jim" and saw this.
So, my bad, my patch went in first, but I applied the rest :)
Thanks!
--Dan
On Wed, Dec 4, 2019 at 3:55 PM Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
# HG changeset patch # User Jim Unroe rock.unroe@gmail.com # Date 1575409568 18000 # Node ID 19016d47dec8c8c7788e3120f7b7e4324e68085c # Parent 1fb51f2fced1a2cb2a0910a8673b634d0269e629 Fix Kenwood TM-D700 tuning steps
fixes #7053
Gah, sorry Jim! I was literally doing some work on the D700 in the last couple of days. I just pushed those, including a fix for tuning_steps, then said "oh, I better go apply that set from Jim" and saw this.
So, my bad, my patch went in first, but I applied the rest :)
Thanks!
--Dan
Dan,
No problem. I feel a little nervous making these patches not having a physical radio to test them. But there are a quite a few open issues regarding the valid_tuning_step and it is a fairly straight forward fix (plus I was in the mood to do some programming). The hardest part was searching for a User Manual to determine what each model actually supported.
Jim
# HG changeset patch # User Jim Unroe rock.unroe@gmail.com # Date 1575419553 18000 # Node ID a7011810dd85edeeb0f1e318f1679930a77222f5 # Parent 19016d47dec8c8c7788e3120f7b7e4324e68085c Fix Kenwood TK-370 tuning steps
Also TK-260, TK-270, TK-272, TK-278, TK-360, TK-372 and TK-378
fixes #7199
diff -r 19016d47dec8 -r a7011810dd85 chirp/drivers/tk270.py --- a/chirp/drivers/tk270.py Tue Dec 03 16:46:08 2019 -0500 +++ b/chirp/drivers/tk270.py Tue Dec 03 19:32:33 2019 -0500 @@ -382,6 +382,7 @@ rf.valid_dtcs_codes = DTCS_CODES rf.valid_bands = [self._range] rf.memory_bounds = (1, self._upper) + rf.valid_tuning_steps = [2.5, 5.0, 6.25, 10.0, 12.5, 25.0] return rf
def sync_in(self):
participants (2)
-
Dan Smith -
Jim Unroe