https://chirpmyradio.com/https://chirpmyradio.com/favicon.ico?16699092072019-12-30T06:41:18ZCHIRPCHIRP - Bug #7417: Yaesu FT-65R "Frequency out of supported range" errorhttps://chirpmyradio.com/issues/7417?journal_id=190912019-12-30T06:41:18ZBrad Stewartbrad@austererisk.com
<ul></ul><p>I confirm the above issue.</p>
<p>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</p>
CHIRP - Bug #7417: Yaesu FT-65R "Frequency out of supported range" errorhttps://chirpmyradio.com/issues/7417?journal_id=190932019-12-30T09:05:10ZBrad Stewartbrad@austererisk.com
<ul></ul><p>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)</p>
CHIRP - Bug #7417: Yaesu FT-65R "Frequency out of supported range" errorhttps://chirpmyradio.com/issues/7417?journal_id=190952019-12-31T01:45:46ZBrad Stewartbrad@austererisk.com
<ul></ul><p>Brad Stewart wrote:</p>
<blockquote>
<p>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)</p>
</blockquote>
CHIRP - Bug #7417: Yaesu FT-65R "Frequency out of supported range" errorhttps://chirpmyradio.com/issues/7417?journal_id=199952020-02-01T22:37:02ZBernhard Hailerae6yn@arrl.net
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li><li><strong>Target version</strong> set to <i>chirp-legacy</i></li><li><strong>Model affected</strong> changed from <i>(All models)</i> to <i>Yaesu FT-65R</i></li><li><strong>Platform</strong> changed from <i>MacOS</i> to <i>All</i></li></ul><p>This is a duplicate on <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Allow RO frequencies on FT-4/FT-65 (Closed)" href="https://chirpmyradio.com/issues/6651">#6651</a>. Please leave any further feedback there. Thanks!<br>
I'm working on a fix.</p>