Bug #7417
Yaesu FT-65R "Frequency out of supported range" error
| Status: | Closed | Start date: | 12/06/2019 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | chirp-daily | |||
| Chirp Version: | daily | Platform: | All | |
| Model affected: | Yaesu FT-65R |
Description
I have a Yaesu FT-65R with a prolific cable that I have seen successful reports from. Chirp correctly downloads memory channels from the radio. However, in UHF I cannot enter perfectly valid frequencies such as the FRS/GMRS channels (462 - 467 MHz). These can be programmed into memory via the radio. Why are they blocked in CHIRP? Is there a way for me to disable CHIRP's error checking in order to "force" it to enter these valid frequencies?
Related issues
History
Updated by Brad Stewart over 1 year ago
I confirm the above issue.
I am trying to program Australian UHF CB frequencies (476.4250 - 477.4125) into the Yaesu FT-65R with a genuine Yaesu SCU35 cable and Prolific PL2303 drivers installed onCHIRP daily-20191221
Updated by Brad Stewart over 1 year ago
When I enter 430.000Mhz it is fine - this means that CHRIP is only allowing the EU model (FT-65E) and not the Asian model (FT-65R)
Updated by Brad Stewart over 1 year ago
Brad Stewart wrote:
When I enter 430.000Mhz it is fine - this means that CHIRP is only allowing the FT-65E 430 - 440MHz [EU Version] and not the Asian model (FT-65R)
Updated by Bernhard Hailer about 1 year ago
- Status changed from New to Closed
- Priority changed from High to Normal
- Target version set to chirp-daily
- Model affected changed from (All models) to Yaesu FT-65R
- Platform changed from MacOS to All
This is a duplicate on #6651. Please leave any further feedback there. Thanks!
I'm working on a fix.