Project

General

Profile

Actions

Bug #1273

closed

FT-60r not receiving "on frequency"

Added by Phil Lichtenberger over 10 years ago. Updated about 7 years ago.

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

100%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
All
Debug Log:
I read the instructions above:

Description

As per my e-mail thread here: http://intrepid.danplanet.com/pipermail/chirp_users/2013-November/004951.html

I'm trying to write to a FT-60r using the latest stable build and the latest dev build (2013-11-21). Using both versions of software, it seems that the radio is failing to receive on the correct frequency, even though Chirp shows the correct data was entered.

Example: Saving 477.3875 with a step of 12.5khz is being received by the radio as 477.380. I verified this by changing the memory settings from Alpha to Freq. A frequency of 477.380 is displayed in that memory location. (In an update to my e-mail request, I checked 453.8375 is going into the radio as 453.8300)

BUT - the strange thing is, if I read the configuration back via Chirp, it reads that 477.3875 was actually programmed into the radio in that memory location!

I'm just picking this single frequency as an example, but it seems that every frequency I programmed into the radio is "off".

As Requested from Tom, I'm enclosing a dump of the radio with 477.8300 in memory 1 and 477.8375 in memory 2. The radio was cleared prior to the two frequencies being placed in memory locations 1 and 2 via the keypad entry method of programming


Files

FT-60r_477-3875.img (27.9 KB) FT-60r_477-3875.img Phil Lichtenberger, 11/26/2013 12:59 PM
ft60.png (53.9 KB) ft60.png Tom Hayward, 11/26/2013 01:28 PM
Actions #1

Updated by Tom Hayward over 10 years ago

  • File ft60.png ft60.png added
  • % Done changed from 0 to 10
  • Platform changed from Windows to All

Thanks for taking the time to submit this issue and prepare the img. It is exactly what I needed to see the problem.

I added a third memory to your img, this time adding 477.3875 via Chirp. The attached screenshots illustrates that the memory saved by the radio and by Chirp are different! This should not happen. I'll submit a patch to correct this.

!/attachments/839/ft60.png!

Actions #2

Updated by Tom Hayward over 10 years ago

  • Status changed from New to Resolved
  • % Done changed from 10 to 100

Patch submitted.

Actions #3

Updated by Tom Hayward over 10 years ago

  • Status changed from Resolved to In Progress

Well, the patch fixes this one frequency but breaks many others. I'd hold off on using this until I figure out what's going on.

I've got access to an FT-60 this weekend for testing. Unfortunately, I didn't grab the programing cable, so I can't test anything.

Actions #4

Updated by Tom Hayward over 10 years ago

  • Status changed from In Progress to Needs Backport

Should work properly in the latest daily build.

Sorry it took me so long to dig into the radio (at least I had one available to borrow!).

Actions #5

Updated by Tom Hayward about 7 years ago

  • Status changed from Needs Backport to Closed
Actions

Also available in: Atom PDF