Project

General

Profile

Actions

Bug #11894

closed

baofeng_uv17Pro driver has incorrect DTMF mapping for *, #, A, B, C, D

Added by Jim Unroe about 2 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
03/16/2025
Due date:
% Done:

100%

Estimated time:
Chirp Version:
next
Model affected:
Baofeng UV-17ProGPS / Baofeng BF-F8HP PRO
Platform:
Windows
Debug Log:
I read the instructions above:
Yes

Description

It was noticed while performing development for the Baofeng K6 and K61 models that the CHIRP mapping for DTMF *, #, A, B, C and D signals did not match the factory programming software. The current mapping, DTMF_CHARS = "0123456789 *#ABCD" , displays the characters programmed by the factory software as show in the first column as the characters as shown in the second column below.

Set by  | Displayed
Factory | by
CPS     | CHIRP
--------+--------
    *** | BBB
    ### | CCC
    AAA | {space}{space}{space}
    BBB | ***
    CCC | ###
    DDD | AAA

The attached screen captures shows 16 DTMF Signal Codes each programmed and named with the 16 available DTMF characters using the factory software for the Baofeng UV-17ProGPS and the Baofeng BF-F8HP PRO and then displayed in CHIRP after downloading from each radio. Signal Code x and Signal Code Name x should match for all 16 codes however Signal Code 11 - Signal Code 16 do not match as described above.

The corrected mapping, DTMF_CHARS = "0123456789ABCD*#" , will properly map the correct DTMF signal in the radio with the displayed DTMF character in CHIRP as shown in the screen capture for the K6.


Files

Actions #1

Updated by Anonymous about 2 months ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF