Project

General

Profile

Actions

Bug #3573

closed

Yaesu ft2900r programming issue

Added by Ronald Donato about 8 years ago. Updated almost 4 years ago.

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

0%

Estimated time:
Chirp Version:
daily
Model affected:
Yaesu FT-1900/FT-2900/FT-8800
Platform:
Windows
Debug Log:
I read the instructions above:

Description

Hello,
I have previously programmed the ft2900r with chirp with success, but now I am trying to update and it won't work. I keep getting "error" on the radio and "unable to communicate: header error" in chirp. I know this radio cloning procedure is a little convoluted, so what am I missing?
Thanks,
-Ron


Files

FT-2900R_Test.img (7.81 KB) FT-2900R_Test.img Mark Cayton, 06/10/2016 07:42 PM
Actions #1

Updated by Daniel Clerc about 8 years ago

Dear Ron!

Please add the debug.log file with your issue. Then maybe we can support you!

Best,

Daniel

Actions #2

Updated by Ronald Donato about 8 years ago

I figured out the issue. When I save the file and open it back up, I noticed that is was saved as a (modded) file even though the downloaded file from the radio wasn't. That is one of the yaesu ft2900R/1900R options for download. The (modded) version does not work, but somehow gets saved that way, so that future recall of that file won't work.

Actions #3

Updated by Paulo Henrique about 8 years ago

Ronald Donato wrote:

I figured out the issue. When I save the file and open it back up, I noticed that is was saved as a (modded) file even though the downloaded file from the radio wasn't. That is one of the yaesu ft2900R/1900R options for download. The (modded) version does not work, but somehow gets saved that way, so that future recall of that file won't work.

friend could tell me if you have cable or bought it ready?
which became the serial configuration used?
I am using a usb> ttl converter to use to program other radios I have here

Actions #4

Updated by Mark Cayton almost 8 years ago

To whom it may concern:

Ronald Donato was mistaken in his post #2 when he said that that a FT-2900R .img file is saved as a (modded) file. It isn't saved as a (modded) file, it's merely opened as a (modded) file.

The Chirp executable dated 3-23-2016 is the last one in the Daily Releases that behaves correctly in that respect. I can open any FT-2900R .img file just fine with that version, but any later Chirp version opens any FT-2900R .img file as a (modded) file and consequently thinks the radio is a (modded) version and will fail to upload the file to an un-modded radio.

That's the problem. I'm agreeable to assisting with a resolution in any way I can. I've attached a test FT-2900R .img file. That file opens as a non-(modded) file with any Chirp executable dated 3-23-2016 or earlier, but opens as a (modded) file by any subsequent version of Chirp.

Please let me know if I can be of any more help.

Actions #5

Updated by Eric schwab about 7 years ago

Mark Cayton wrote:

To whom it may concern:

Ronald Donato was mistaken in his post #2 when he said that that a FT-2900R .img file is saved as a (modded) file. It isn't saved as a (modded) file, it's merely opened as a (modded) file.

The Chirp executable dated 3-23-2016 is the last one in the Daily Releases that behaves correctly in that respect. I can open any FT-2900R .img file just fine with that version, but any later Chirp version opens any FT-2900R .img file as a (modded) file and consequently thinks the radio is a (modded) version and will fail to upload the file to an un-modded radio.

That's the problem. I'm agreeable to assisting with a resolution in any way I can. I've attached a test FT-2900R .img file. That file opens as a non-(modded) file with any Chirp executable dated 3-23-2016 or earlier, but opens as a (modded) file by any subsequent version of Chirp.

Please let me know if I can be of any more help.

So, how can I find the download dated 3-23-16?
I tried everything (I believe) to make it work with my FT-2900M.
I uninstalled, reinstalled, used many of the older builds ( history dont go back to March.....) and it still says "Cant read header".
I'm running win 10. It worked on these radios with this computer in the last 6-8 months.....HELP!

Actions #6

Updated by Eric schwab about 7 years ago

Anybody have an download as old as 3/23/16 or older they can send me?

Actions #7

Updated by Jim Unroe about 7 years ago

  • Status changed from New to Feedback

Eric,

There looks to be one in the repository that is about 2 years old.

http://chirp.danplanet.com/projects/chirp/repository/show/tests/images

Jim

Actions #8

Updated by Gualterio Papparelli about 7 years ago

Eric schwab wrote:

Anybody have an download as old as 3/23/16 or older they can send me?

Hello, this is the version 20160323.http://www.mediafire.com/file/lc9xfmi4n4kq72d/chirp-daily-20160323-installer.exe

Actions #9

Updated by Eric schwab about 7 years ago

THANK YOU!!!

Actions #10

Updated by Bernhard Hailer almost 4 years ago

  • Status changed from Feedback to Closed
  • Target version set to chirp-legacy
  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from (All models) to Yaesu FT-1900/FT-2900/FT-8800

Issue had been fixed, but was reopened in #7025. Please follow and post there. Thanks!

Actions

Also available in: Atom PDF