Project

General

Profile

Actions

Bug #783

closed

Yaesu FT7900R: "Radio did not ack block at 31624"

Added by Patrick Wong over 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
04/16/2013
Due date:
% Done:

0%

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

Description

Previously I have been using version 0.1.12 with my Yaesu FT7900R without any problem. Yesterday, I upgraded to version 0.3.1. I was able to load the frequencies from the radio to CHIRP. However, after changing some entries using CHIRP, I tried to load the frequencies back to the radio. At the end of the cloning, the subject error occurred. Please assist. Thx!

P.S. I am an ARES volunteer scheduled to work the radio communications at the BP MS150 bike ride from Houston to Austin this Saturday and I plan to use my FT7900R. It would be good if this reported bug is resolved before then.


Related issues 1 (0 open1 closed)

Is duplicate of Bug #597: FT-7900 upload errorClosedJens Jensen02/19/2013

Actions
Actions #1

Updated by Patrick Wong over 11 years ago

Patrick Wong wrote:

Just found out the Bug #597 reported the same issue with his FT-7900R file upload, except that the other person was running MacOS vs. my running XP. Just as the other person said, the upload seemed to have completed despite of the error.

Previously I have been using version 0.1.12 with my Yaesu FT7900R without any problem. Yesterday, I upgraded to version 0.3.1. I was able to load the frequencies from the radio to CHIRP. However, after changing some entries using CHIRP, I tried to load the frequencies back to the radio. At the end of the cloning, the subject error occurred. Please assist. Thx!

P.S. I am an ARES volunteer scheduled to work the radio communications at the BP MS150 bike ride from Houston to Austin this Saturday and I plan to use my FT7900R. It would be good if this reported bug is resolved before then.

Actions #2

Updated by Jens Jensen almost 11 years ago

  • Status changed from New to Resolved
  • Assignee set to Jens Jensen

resolved on #597

Actions #3

Updated by Jens Jensen over 10 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF