Project

General

Profile

Actions

Bug #5103

closed

DTMF & ANI code changing for QYT KT-8900

Added by Brent Sutherland over 6 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
08/25/2017
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
QYT KT-8900
Platform:
Windows
Debug Log:
I read the instructions above:

Description

First of all let me thank the developers of CHIRP for providing such a powerful multi platform product! As a novice radio enthusiast it has really helped me learn a lot.

Now on to my request for info.... I'm sure you get a plethora of wants and needs requests but as stated I have a QYT KT8900 radio. I can't for the life of me find where I can change the ANI code of it and properly set up EOT DTMF transmission. Your software did this like a champ on my UV-5R+. But I can't find this little tid bit of programming in CHIRP.

As a side note I've tried the factory software with factory dongle and the radio just keeps rebooting so that's not an option. But the radio reads and writes 100% with CHIRP; it never misses a beat.

Thank you,

Brent


Files

CHIRP_DTMF_Code-ANI.png (75.4 KB) CHIRP_DTMF_Code-ANI.png DTMF Encoding Settings tab where DMTF Code/ANI signals are programmed Jim Unroe, 08/26/2017 06:54 PM
CHIRP_PTT_ID-ANI.png (24.2 KB) CHIRP_PTT_ID-ANI.png Memory Properties page tp program per-channel PTT ID/ANI signals Jim Unroe, 08/26/2017 06:54 PM
Actions #1

Updated by Jim Unroe over 6 years ago

Hi Brent,

It is all right there. Virtually the same as for a UV-5R. You have 15 code slots with up to 16 DTMF signals each that you can program to be transmitted BOT, EOT or both on a per channel basis.

Jim KC9HI

Actions #2

Updated by Brent Sutherland over 6 years ago

Thanks very much for getting back to me... I'm beginning to think I may have a radio fault. I had tried those settings in CHIRP before and nothing changed in the radio operation wise. Oh well it is what it is. I guess I can live with keying in the DTMF code manually till I get a new radio.

Again, thanks a bunch! I thought I was going mental but in the end I was on the right track with a suspect radio! :)

Actions #3

Updated by Bernhard Hailer about 4 years ago

  • Tracker changed from Feature to Bug
  • Status changed from Feedback to Closed
  • Target version set to chirp-legacy
  • Platform set to Windows

No more traffic on this ticket.
Assuming faulty radio.

Actions

Also available in: Atom PDF