Project

General

Profile

Actions

Bug #8995

closed

"rf.valid_dtcs_codes" setting missing from "Radio Features"

Added by Jim Unroe about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
04/17/2021
Due date:
% Done:

100%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
All
Debug Log:
I read the instructions above:

Description

While performing research for another driver, I noticed that several drivers are coded with the intent to add 1 or mode additional DTCS codes to the chirp_common.DTCS_CODES list to extend the list to match the list of DTCS codes supported in the radio. However, the driver did not include the "rf.valid_dtcs_codes" setting to let CHIRP know about the additional DTCS code(s). Without being told otherwise, CHIRP defaults to the "chirp_common.DTCS_CODES" list and hides the "extra" DTCS codes from the driver user.

The drivers affected by this are:
alinco.py
kyd.py
leixen.py
retevis_rt1.py
retevis_rt22.py
retevis_rt23.py
retevis_rt26.py
uv5r.py
uv5x3.py
uv6r.py

Jim KC9HI

Actions #1

Updated by Jim Unroe about 3 years ago

  • % Done changed from 0 to 100

While doing the work, it was decided that the uv5x3.py and uv6r.py drivers are on the list by mistake.

Jim KC9HI

Actions #2

Updated by Jim Unroe about 3 years ago

  • Status changed from In Progress to Resolved

Patches submitted.

Jim KC9HI

Actions #3

Updated by Bernhard Hailer almost 3 years ago

  • Status changed from Resolved to Closed

This appears to be complete.

Actions

Also available in: Atom PDF