Project

General

Profile

Actions

Bug #11681

closed

Yaesu FT-70D Wrong tuning steps

Added by Stephen Cavilia 8 days ago. Updated 6 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/14/2024
Due date:
% Done:

100%

Estimated time:
Chirp Version:
next
Model affected:
Yaesu FT-70D
Platform:
Linux
I read the instructions above:
Yes

Description

Some tuning step values for the FT-70D are incorrect, namely 5KHz and 6.25KHz. Creating channels in chirp with the default 5KHz step will become 6.25KHz on the radio. This doesn't really cause any issues if you're not adjusting tuning on a memory channel from the radio, but if you open this image with Yaesu's official software it will snap everything to frequencies that match the tuning step, and since 5 doesn't divide into 6.25 it will change some frequencies.

In the attached image, memory slots 50-59 were stored from the radio using the same frequency but with all different tuning steps in order (50 is 'auto,' which gets stored as 25K). The next two are really 5 and 6.25 but show up as 0 and 5 in chirp. Steps 10 and above are correct.

Looking at the raw memory the sequence appears to skip over 2 (0x00 = 5, 0x01 = 6.25, 0x03 = 10, 0x04 = 12.5)


Files

Yaesu_FT-70D_tuningsteps.img (63.9 KB) Yaesu_FT-70D_tuningsteps.img Stephen Cavilia, 11/14/2024 07:34 AM
ft70.py (44.3 KB) ft70.py Dan Smith, 11/14/2024 05:06 PM
Actions #1

Updated by Dan Smith 7 days ago

Excellent prep work, thanks. Please try the attached module with LoadingTestModules and let me know.

Actions #2

Updated by Stephen Cavilia 6 days ago

Dan Smith wrote in #note-1:

Excellent prep work, thanks. Please try the attached module with LoadingTestModules and let me know.

Seems to work now. I uploaded the data from the radio again and my test channels showed the correct steps, also changed the other channels to sensible values (most showed 6.25 now) and they match after writing the file back to the radio.

Actions #3

Updated by Dan Smith 6 days ago

Perfect thanks, I will queue for the next build.

Actions #4

Updated by Dan Smith 6 days ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF