Bug #10970
openUnable to find a supported tuning step for xxx
0%
Description
using chirp next, I am unable to add channels to radio's. I can copy and paste these channels in chip legacy, they may not be a perfect tuning step, but it works. That is how I was managing this issue.
I recently acquired a UV-21pro (works with UV-17pro drivers). This is not supported in chirp legacy. So, I downloaded a stock image of the radio. Then I tried to copy the channels over. Several channels are rejected. I tried punching in 464.18875 directly in the radio. That works. But when I punch that directly in chirp, it rejects it. This has been happening across several radio models I use. I can dig in and provide more info if requested. But the logs and attached image should provide some context, I hope.
thanks.
Files
Updated by Jim Unroe 12 months ago
Those frequencies don't look like anything that would likely assigned by any agencies. Normal step compatible frequencies would be:
464.1875 (diff -500 Hz)
458.6625 (diff -500 Hz)
407.1125 (diff -800 Hz)
407.1375 (diff -800 Hz)
408.0125 (diff -800 Hz)
464.0890 (diff +500 Hz)
469.2625 (diff -900 Hz)
I would be interested in knowing where/how you came up with those frequencies?
Updated by Sander van der Wel 12 months ago
At least I find it interesting to read that the UV-17Pro driver reads the UV-21Pro.
Updated by C F 12 months ago
Jim Unroe wrote in #note-1:
Those frequencies don't look like anything that would likely assigned by any agencies. Normal step compatible frequencies would be:
464.1875 (diff -500 Hz) 458.6625 (diff -500 Hz) 407.1125 (diff -800 Hz) 407.1375 (diff -800 Hz) 408.0125 (diff -800 Hz) 464.0890 (diff +500 Hz) 469.2625 (diff -900 Hz)I would be interested in knowing where/how you came up with those frequencies?
I have a Chinese frequency sniffer. https://a.co/d/fBmSGpW
it is a close, but not exact thing, lol.
The issue is that chirp legacy doesn't complain about the channels, just programs them. When I look at the frequency in the older model radios, I see what appears to be exactly what I have input in chirp, just like in the posted picture, albeit rounded to 3 decimals. ie. 464.188. In the UV-21 I can punch in 464.188, and it just puts it at 464.18875. I can also punch in 464.18750. Chirp next however lets me punch in the frequencies you posted, which is probably more accurately the frequency of the company's channels, but not 464.18875. But the frequencies I am using are working on the older radios when I use them.
thanks to everyone who maintains this software though, just so I am clear, you guys rock.
Updated by C F 12 months ago
Jim Unroe wrote in #note-1:
Those frequencies don't look like anything that would likely assigned by any agencies. Normal step compatible frequencies would be:
464.1875 (diff -500 Hz) 458.6625 (diff -500 Hz) 407.1125 (diff -800 Hz) 407.1375 (diff -800 Hz) 408.0125 (diff -800 Hz) 464.0890 (diff +500 Hz) 469.2625 (diff -900 Hz)I would be interested in knowing where/how you came up with those frequencies?
I have a Chinese frequency sniffer. https://a.co/d/fBmSGpW
it is a close, but not exact thing, lol.
The issue is that chirp legacy doesn't complain about the channels, just programs them. When I look at the frequency in the older model radios, I see what appears to be exactly what I have input in chirp, just like in the posted picture, albeit rounded to 3 decimals. ie. 464.188. In the UV-21 I can punch in 464.188, and it just puts it at 464.18875. I can also punch in 464.18750. Chirp next however lets me punch in the frequencies you posted, which is probably more accurately the frequency of the company's channels, but not 464.18875. But the frequencies I am using are working on the older radios when I use them.
thanks to everyone who maintains this software though, just so I am clear, you guys rock.
Sander van der Wel wrote in #note-2:
At least I find it interesting to read that the UV-17Pro driver reads the UV-21Pro.
as much as I would like to take credit, I googled somewhere it is the same software.