Bug #3143

Yaesu Ft-1900 Failed to read header

Added by Sandra Pringle almost 7 years ago. Updated over 2 years ago.

Status:Closed Start date:01/07/2016
Priority:Normal Due date:
Assignee:- % Done:


Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:Yaesu FT-1900


1. What is the behavior you are seeing?
After putting the radio into Clone mode and following the instructions on the screen to click ok and then the "Set MHz" button on the radio I get this error message; An error has occurred, Failed to communicate with radio; Failed to read header.

2. What is the behavior you were expecting?
I was expecting to see the input of the data on the program screen.

3. Can you reproduce the problem all the time?
Yes, every time I try.

4. What are the steps required to reproduce the problem?
Since my program cord is a prolific I tried to downgrade the driver, made no difference
I tried a total reset of the radio, no difference
I found a similar issue reported http://chirp.danplanet.com/issues/2501 and spoke with some older radio operators, and was told my radio (given to me) was modified but that the radio had been programmed in the past with no problems. I also see that my header is different from what is listed in the past issue.
000: 56 43 32 33 00 02 c7 01 VC23....
008: 01 01 00 00 00 00 00 00 ........

5. Is this specific to a certain radio model (driver) or something that you can reproduce with another radio?
I have had no trouble at this time with my other radios (Baofeng)

Error.jpg - ScreenShot (80.9 kB) Sandra Pringle, 01/07/2016 05:51 am

debug2.txt - Debug Log (16.7 kB) Sandra Pringle, 01/07/2016 05:51 am

Related issues

related to Bug #7025: Yaesu FT-1900E - Failed to communicate with radio. Failed... New 08/29/2019
related to Bug #3567: FT1900 Failed to read header Closed 04/13/2016


Updated by Bernhard Hailer almost 3 years ago

  • Subject changed from Header Yeasu Ft-1900 to Yaesu Ft-1900 Failed to read header
  • Status changed from New to Feedback
  • Target version set to chirp-daily
  • Model affected changed from Yeasu Ft-1900 to Yaesu FT-1900

From the log, I'd think that you might have a problem with your cable. Please check these Wiki articles:
CableGuide FTDI OEM Cables
RTSystemsCablesAndMavericks (for MacOS)

Updated by Bernhard Hailer over 2 years ago

  • Status changed from Feedback to Closed

This issue was declared closed in #6925, then re-opened in #7025. Please let's continue the discussion there. Thanks!

Also available in: Atom PDF