Project

General

Profile

Actions
Copy link

Bug #9713

closed

Chirp reads Yaesu FT65R saved offset different value

Added by Sean Ebue almost 3 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Bernhard Hailer
Category:
-
Target version:
-
Start date:
01/18/2022
Due date:
% Done:

100%

Estimated time:
Chirp Version:
daily
Model affected:
Yaesu FT65R
Platform:
Linux
Debug Log:
I read the instructions above:

Description

Yaesu FT65R using original Yaesu data cable.
Issue:
Chirp reads the offset different value from the saved offset on the said Yaesu FT65r.

Files

Download all files
Screenshot 2022-01-19 094955.jpg (366 KB) Screenshot 2022-01-19 094955.jpg Sean Ebue, 01/18/2022 06:12 PM
Screenshot 2022-01-19 095047.jpg (273 KB) Screenshot 2022-01-19 095047.jpg Sean Ebue, 01/18/2022 06:12 PM
20220120_092909.jpg (4.05 MB) 20220120_092909.jpg Sean Ebue, 01/19/2022 05:37 PM
20220120_092917.jpg (4.08 MB) 20220120_092917.jpg Sean Ebue, 01/19/2022 05:37 PM
20220120_092935.jpg (4.07 MB) 20220120_092935.jpg Sean Ebue, 01/19/2022 05:37 PM
Yaesu_FT-65R_20220121.img (8.49 KB) Yaesu_FT-65R_20220121.img Sean Ebue, 01/20/2022 06:16 PM
ft4.py (52.5 KB) ft4.py Bernhard Hailer, 02/15/2023 01:16 AM

Related issues 1 (0 open — 1 closed)

Related to Bug #10286: Yaesu FT-25 Offset doublesClosedBernhard Hailer01/18/2023

Actions
Actions
Copy link
 #1

Updated by Jim Unroe almost 3 years ago

  • Status changed from New to Feedback

Hi Sean,

You should include a CHIRP Radio Images (*.img) file that was freshly downloaded from your FT65R so a developer has something to work with.

Jim KC9HI

Actions
Copy link Download all files
 #2

Updated by Sean Ebue almost 3 years ago

here are some photos showing my Yaesu FT65R with Chirp.

Actions
Copy link
 #3

Updated by Jim Unroe almost 3 years ago

Sean Ebue wrote:

here are some photos showing my Yaesu FT65R with Chirp.

How about adding the requested *.img file?

Jim KC9HI

Actions
Copy link
 #4

Updated by Sean Ebue almost 3 years ago

Here is the *.img file

Actions
Copy link
 #5

Updated by Jim Unroe almost 3 years ago

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

Actions
Copy link
 #6

Updated by Sean Ebue almost 3 years ago

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

Actions
Copy link
 #7

Updated by Dan Smith almost 2 years ago

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?

Actions
Copy link
 #8

Updated by Dan Smith almost 2 years ago

  • Related to Bug #10286: Yaesu FT-25 Offset doubles added
Actions
Copy link
 #9

Updated by Steven Hiscocks almost 2 years ago

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.

Actions
Copy link
 #10

Updated by Steven Hiscocks almost 2 years ago

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

Actions
Copy link
 #11

Updated by Bernhard Hailer almost 2 years ago

  • Assignee set to Bernhard Hailer
  • Platform changed from Windows to Linux

The interesting thing is that there is a multiplier in the code. The multipliers for FT-25/65 and FT-4 are different, with the one for the FT-25/65 being twice the value of the one for the FT-4 (50 vs. 25 kHz). Looking into this ticket, and also #10286, I'm beginning to suspect that the multipliers are applied using some mechanism we haven't caught on yet.

The radio in ticket #10286 might be an export version, sold in Asia. Does this apply for your radio as well?

Actions
Copy link
 #12

Updated by Bernhard Hailer over 1 year ago

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.

Actions
Copy link
 #13

Updated by Bernhard Hailer over 1 year ago

Attached is a modified driver. You can test as follows:

  1. Open Chirp software.
  2. In Help, checkmark "Developer mode".
  3. End and restart Chirp.
  4. In File menu, select "Load module" and load the attached file.
  5. Test.

Please check:

  • whether the offsets are coming out correctly,
  • and whether there's no ID warning anymore in the debug log. Please share your observations and the debug log. Thanks!
Actions
Copy link
 #14

Updated by Anonymous over 1 year ago

  • Status changed from Feedback to Closed
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF

Copyright 2023 CHIRP Software LLC