Project

General

Profile

Actions

Feature #11619

closed

Retevis RT21v - Busy channel lockout naming convention

Added by Bryant L about 1 month ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
10/19/2024
Due date:
% Done:

100%

Estimated time:
Chirp Version:
next
Model affected:
Retevis RT21v
I read the instructions above:
Yes

Description

Hello,

After a quick search I was able to determine QT and DQT are different names for CTCSS and DTCS, but it is confusing to have them called one thing in one spot, and another in a different spot. Perhaps rename QT/DQT to TSQL/DTCS to follow the naming scheme of the rest of CHIRP, or at least add a tooltip to the setting to clarify they are just a vendor specific name? Another option would just be to clarify carrier is if any signal comes in vs a signal with the appropriate tone.

Like I said, I figured it out with a quick search since I have been learning so much about radios, but I think of the scenario where the less versed radio user would be confused which one to choose, or a situation where whoever is programming the radios doesn't have an active internet connection as they are working on something (more rare these days, but still feasible in scenarios where two way radios are used commonly). I also know the goal with CHIRP is to keep as close to OEM CPS as possible, but it's just a scenario of one name one place, and another in a different spot.


Files

chirp_debug-tt405mdr.txt (136 KB) chirp_debug-tt405mdr.txt Doubt this is needed, but including for the fun of it. Bryant L, 10/19/2024 01:17 PM
Screenshot_20241019_161918.png (98.6 KB) Screenshot_20241019_161918.png Image showing how having different names can cause confusion. Bryant L, 10/19/2024 01:20 PM
retevis_rt21.py (80.1 KB) retevis_rt21.py Dan Smith, 10/20/2024 09:05 AM
Actions

Also available in: Atom PDF