Project

General

Profile

Actions

Feature #5579

closed

Yaesu FT-2D Chirp *.dat file open error

Added by Kell Bodholt over 6 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
02/15/2018
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Yaesu FT-2DR
I read the instructions above:

Description

Chirp 20180204 daily build (macOS)
macOS 10.13.3 High Sierra
HT: Yaesu FT-2DR (US)

Description: Formatted a 4G SD card in the FT-2DR. Created a backup of the FT-2DR and saved to SD card (BACKUP.dat). Created a backup of the memory channels and saved to SD card (MEMORY.dat). Opened Chirp, selection Open File, selected *.dat for file types, selected folder where I copied the BACKUP.dat and MEMORY.dat files from the SD card (see FT-2DR Screen Shot_1.jpeg). Once I clicked ok to open the BACKUP.dat file, Chirp reported an error message "Unable to detect model!" (see FT-2DR_Screen Shot_2.jpeg). I then selected the drop down menu and selected the "Yaesu FT2" radio (see FT-2D_Screen Shot_3.jpeg). The MEMORY.dat file then opens but the name column has "ERROR" for memory slots 1 through 38, which coincidentally is the number of memory channels I currently have hand programmed into the FT-2DR. Appears that no data is being read by Chirp (see FT-2DR Screen Shot_4.jpeg), even though the file tab does state "Yaesu FT2D:BACKUP.dat".

So not sure if this is a bug or not, but I would have expected Chirp to be able to open the *.dat file format.


Files

FT2D_Screen Shot_1.jpeg (67.5 KB) FT2D_Screen Shot_1.jpeg Kell Bodholt, 02/15/2018 04:17 PM
FT2D_Screen Shot_2.jpeg (42.2 KB) FT2D_Screen Shot_2.jpeg Kell Bodholt, 02/15/2018 04:17 PM
FT-2D_Screen Shot_3.jpeg (41.8 KB) FT-2D_Screen Shot_3.jpeg Kell Bodholt, 02/15/2018 04:17 PM
FT-2D_Screen Shot_4.jpeg (225 KB) FT-2D_Screen Shot_4.jpeg Kell Bodholt, 02/15/2018 04:17 PM

Related issues 1 (1 open0 closed)

Related to Feature #4779: FT1D microSD card New04/30/2017

Actions
Actions #1

Updated by Kell Bodholt over 6 years ago

Second to last sentence should have referenced the "BACKUP.dat" file rather than the "MEMORY.dat" file. Apologies.

Actions #2

Updated by Chris Gray over 6 years ago

20180810 - This appears to still be an issue with the addition that the option for Yaesu FT2 has been removed from the list of radios.

Actions #3

Updated by Dan Smith over 6 years ago

Chris Gray wrote:

20180810 - This appears to still be an issue with the addition that the option for Yaesu FT2 has been removed from the list of radios.

Why do you say this? Nothing has changed in this regard that I know of, and indeed I see it on 20100810 myself. See that it's on the model support report here:

https://trac.chirp.danplanet.com/chirp_daily/daily-20180810/Model_Support.html

Actions #4

Updated by Chris Gray over 6 years ago

Dan Smith wrote:

Why do you say this? Nothing has changed in this regard that I know of, and indeed I see it on 20100810 myself. See that it's on the model support report here:

https://trac.chirp.danplanet.com/chirp_daily/daily-20180810/Model_Support.html

Hi Dan!

Thanks for the link. OK, I tried it from my Windows PC and I see the FT2D there so I deleted and downloaded it again on my Mac and I see it there now too - guessing something got corrupted on my end. So I'm good there, but maybe I'm doing something else wrong. When I edit the backup.dat file and restore it to my radio, it goes to a factory reset configuration and asks me for my call sign and all of my settings are gone and none of the memories i created are there. My radio is an old firmware - Main Ver. 1.01, Sub Ver. 1.00. I get the same "reset to default" issue if I edit and restore the memory.dat file.

Any help would be greatly appreciated!

Actions #5

Updated by William Hirsch almost 5 years ago

I'm having this issue with the FT3D as well. See https://chirp.danplanet.com/issues/7561#change-19295

Actions #6

Updated by Bernhard Hailer over 4 years ago

  • Status changed from New to Feedback
  • Target version set to chirp-legacy
Actions #7

Updated by Bernhard Hailer about 4 years ago

  • Tracker changed from Bug to Feature
  • Status changed from Feedback to Closed

There are various requests to allow programming via SD Cards. See #4779 as an example. This is currently unsupported.
I'm closing this ticket, referring to #4779; please follow and post there.

Actions

Also available in: Atom PDF