Project

General

Profile

Actions

Bug #7417

closed

Yaesu FT-65R "Frequency out of supported range" error

Added by Dalton Touchberry over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
12/06/2019
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Yaesu FT-65R
Platform:
All
Debug Log:
I read the instructions above:

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?


Files


Related issues

Is duplicate of Feature #6651: Allow RO frequencies on FT-4/FT-65ClosedDaniel Clemmensen03/28/2019

Actions
Actions #1

Updated by Brad Stewart about 4 years 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

Actions #2

Updated by Brad Stewart about 4 years 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)

Actions #3

Updated by Brad Stewart about 4 years 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)

Actions #4

Updated by Bernhard Hailer about 4 years ago

  • Status changed from New to Closed
  • Priority changed from High to Normal
  • Target version set to chirp-legacy
  • 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.

Actions

Also available in: Atom PDF