Bug #12008
openFrequency shift on transmit
0%
Description
(Describe what you were doing - I was programming my two Quansheng UV-K5 radios to communicate on 154.600 MHz, MURS Channel 5, using CHIRP software. I configured Channel 1 on both radios with DTCS codes: Radio 1 with TX DCS D754N and RX DCS D743N, and Radio 2 with TX DCS D743N and RX DCS D754N, using Cross Mode DTCS->DTCS with Normal polarity (NN).)
(Describe what you expected to happen - I expected both radios to transmit and receive on 154.600 MHz reliably. Pressing PTT on Radio 1 should transmit at 154.600 MHz with DTCS code D754N, allowing Radio 2 (set to unmute for D754N) to receive clear audio. Similarly, Radio 2’s TX with D743N should be received by Radio 1 (set for D743N). The radios’ displays should show 154.600 MHz during TX, and scanning with one radio should detect the other’s TX at 154.600 MHz with the correct DTCS code.)
(Describe what actually happened instead - When I press PTT on either radio, the TX frequency shifted to 18.000 MHz (shown on the display), and scanning with the other radio detected frequencies like 161.99960 MHz or 180.0048 MHz instead of 154.600 MHz. No RX occurred between radios.)
(Has this ever worked before? New radio? Does it work with OEM software? - This was my first time trying this DTCS programming (154.600 MHz, DTCS->DTCS, D754N/D743N) on these Quansheng UV-K5 radios. The radios aren’t new; they’ve worked on other frequencies with simpler settings (e.g., no DTCS, carrier RX) without TX shifts or RX issues. I’ve only used CHIRP to program. The TX frequency shift to 18.000 MHz occurred only with CHIRP-programmed channels. Resetting and programming manually resolved the TX shift, and now TX/RX functions correctly.)
Files
Updated by Dustin Clark 18 days ago
- File config.txt config.txt added
- File Channel setup.img Channel setup.img added
- File win_system_info.txt win_system_info.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20250516]
Updated by Dan Smith 18 days ago
Your channels are set to duplex=off. That is supposed to make them not transmit at all, but I'm guessing the egzumer variant changes the behavior in some way, I'll have to ask. However, if you want them to transmit on the same frequency as receive, set the duplex field to "empty". Can you try that and see if it behaves as expected?