Bug #7025: Yaesu FT-1900E - Failed to communicate with radio. Failed to read header - CHIRP

Actions

Copy link

Bug #7025

open

Yaesu FT-1900E - Failed to communicate with radio. Failed to read header

Added by Barry Smith about 5 years ago. Updated over 4 years ago.

Status:

New

Priority:

High

Assignee:

Category:

Target version:

Start date:

08/29/2019

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

(All models)

Platform:

Windows

Debug Log:

I read the instructions above:

Description

I thought this had been cured but it is back again in the latest release

Files

Download all files

debug.log (26.8 KB) debug.log		Barry Smith, 08/29/2019 08:14 AM
Chirp_FT1900_Error.png (32.7 KB) Chirp_FT1900_Error.png		Barry Smith, 04/15/2020 11:58 PM

Related issues 8 (0 open — 8 closed)

Actions

Copy link

Updated by Barry Smith over 4 years ago

File Chirp_FT1900_Error.png Chirp_FT1900_Error.png added

Guys

My cable is OK, my drivers are ok, my cloning skills are ok.
Chirp still claims invalid header.

My software will happily read the memory dump, read the header and all of the memory after it is sent the ack (hex 06)and show the correct channel programming. Months ago this problem was fixed in chirp after the original post, but in subsequent releases it has re-appeared. Mybe the Chirp build is addressing a wrong file

See attached pic for my software screen dump

The header rpeoted by my software is EXACTLY the same as is documented in chirp-FT2900_Driver.py

Actions

Copy link

Updated by Barry Smith over 4 years ago

Re Chirp_FT2900_Driver.py and header:- see line 1256

what is Chirp_Ft2900_driver.py line 1249 (~ NOTE: disabled until detection is fixed)

Actions

Copy link

Also available in: Atom PDF

Project

General

Profile

CHIRP

Custom queries

Bug #7025

Yaesu FT-1900E - Failed to communicate with radio. Failed to read header

Updated by Barry Smith over 4 years ago

Updated by Barry Smith over 4 years ago