CHIRP

Sean Ebue wrote:

here are some photos showing my Yaesu FT65R with Chirp.

How about adding the requested *.img file?

Jim KC9HI

Thanks for adding the CHIRP image. The ft4.py driver which is used for the FT-65 mentions the following.

 ul16 offset;   //little-endian binary * scaler, +- per duplex
                   //scaler is 25 kHz for FT-4, 50 kHz for FT-65.

Looking at the "offset" values stored in the "image" for channel 4 and channel 5, that would calculate to the values as shown in CHIRP.

Scrolling down to channels 100 though 119 which calculate the offset for these VHF repeaters using the 50 kHz scaler, the displayed offsets appear to be correct.

So after spending some time with a calculator, it would seem to me (and this is a wild guess) is that your particular FT-65 uses a 50 kHz scaler only for VHF repeater frequencies. A 25 kHz scaler would be needed for CHIRP to calculate the correct offset for UHF repeater frequencies.

Jim KC9HI

Thank you and if I am not mistaken Yaesu FT65 was made only for amateurs and some limitations on commercial use.
Did I got it correctly? Anyway, Thank you and really appreciate it!

Sean

Sean can you confirm that you have an FT-65E (i.e. Euro or EXP export) model?

Also, can you confirm whether or not the offsets are wrong for VHF and UHF or only UHF?

I just tested the offsets on my FT-65E and didn't have any issues. Value matched between radio and CHIRP. Tested with CHIRP next-20230126.

Sorry, should have said in previous comment...I tested both VHF and UHF. Both fine.

I've received an email from Sean (thanks!) which confirms my assumptions that

• the phenomenon occurs on FT-25R/65R sold in the Asia region,
• the scaler is controlled by the last byte in the radio ID.

The debug logs he shared contain these telling lines, like in issue #10286:

[2023-02-15 06:57:09,622] chirp.drivers.ft4 - WARNING: ID suspect. Expected000: 49 48 2d 34 32 30 00 00   IH-420..
008: 00 56 31 30 30 00 00      .V100...
, Received:000: 49 48 2d 34 32 30 00 00   IH-420..
008: 00 56 31 30 30 00 03      .V100...

Please expect a test patch here soon.