New Model #3257: Yaesu FT2DR - CHIRP

Custom queries

All CHIRP-next Bugs
All CHIRP-next Feature Requests
All closed issues
All open issues
New Model Requests
Open bugs by Developer
Open bugs by Target Version
Potentially Stalled Bugs

New Model #3257

closed

Yaesu FT2DR

Added by Darin Record about 9 years ago. Updated about 5 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

01/29/2016

Due date:

% Done:

Estimated time:

Equipment Loan/Gift Offered:

I read the instructions above:

Description

Not sure if the programming is the same for this and the FT1, but it looks like they're pretty similar.

Files

Yaesu_FT2D_R.img (127 KB) Yaesu_FT2D_R.img

Sample memory image.

Declan Rieb, 07/05/2017 05:34 PM

Related issues 1 (0 open — 1 closed)

Has duplicate New Model #3325: Yaesu FT2DR

Closed

02/12/2016

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Jarno Jaskari about 9 years ago

Darin Record wrote:

Not sure if the programming is the same for this and the FT1, but it looks like they're pretty similar.

Chirp works fine with my FT2DE when i'm using FT1D profile.

Actions

Copy link

Updated by Jarno Jaskari about 9 years ago

Chirp works fine with my FT2DE when i'm using FT1D profile.

Actions

Copy link

Updated by Tony Leone almost 9 years ago

Using the latest version of Chirp as of today, with the latest Yaesu firmware as of today, with the CU-19 cable...

Using the FT1D profile, Chirp reads the radio when its in clone mode but the channel names are corrupt and several columns have incorrect values.

Actions

Copy link

Updated by Tony Leone almost 9 years ago

Using the latest OSX version of Chirp as of today, with the latest Yaesu firmware as of today, with the CU-19 cable...

Using the FT1D profile, Chirp reads the radio when its in clone mode but the channel names are corrupt and several columns have incorrect values.

Actions

Copy link

Updated by Declan Rieb almost 8 years ago

File Yaesu_FT2D_R.img Yaesu_FT2D_R.img added

It is indeed similar to the FT-1D memory module; FT-1D mostly works with FT2DR except that most labels are scrambled in chirp. I've submitted a candidate driver and am hereby uploading a test module, with the following caveats:

I cannot seem to get the radio back to exact factory-blank state. I know that APRS packet data are still in the radio (and thus in the test module.)
Even after a full reset, the radio insists on entering a call sign. So the test module has mine in there.

Actions

Copy link

Updated by Dan Smith almost 8 years ago

Yeah, that's a problem with Yaesu radios. I have no idea why they won't do a full reset, but they don't. Seems like a poor engineering decision to me :(

Actions

Copy link

Updated by Bernhard Hailer about 5 years ago

Tracker changed from Bug to New Model
Subject changed from Support for Yaesu FT2DR to Yaesu FT2DR
Status changed from New to Closed
Chirp Version changed from 0.4.0 to daily
Equipment Loan/Gift Offered set to No

Support for the Yaesu FT2DR has been added over two years ago.

Actions

Copy link

Also available in: Atom PDF

Project

General

Profile

CHIRP

Custom queries

New Model #3257

Yaesu FT2DR

Updated by Jarno Jaskari about 9 years ago

Updated by Jarno Jaskari about 9 years ago

Updated by Tony Leone almost 9 years ago

Updated by Tony Leone almost 9 years ago

Updated by Declan Rieb almost 8 years ago

Updated by Dan Smith almost 8 years ago

Updated by Bernhard Hailer about 5 years ago