Bug #7025

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

Added by Barry Smith almost 3 years ago. Updated over 2 years ago.

Status:New Start date:08/29/2019
Priority:High Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Chirp Version:daily Platform:Windows
Model affected:(All models)

Description

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

debug.log (26.8 kB) Barry Smith, 08/29/2019 08:14 am

Chirp_FT1900_Error.png (32.7 kB) Barry Smith, 04/15/2020 11:58 pm


Related issues

related to Bug #3571: YAESU FT-2900R-MARS MODDED Closed 04/14/2016
related to Bug #7773: FT1900 Closed 04/06/2020
related to Bug #6333: Failed to communicate with radio. Failed to read header. ... Closed 12/29/2018
related to Bug #3143: Yaesu Ft-1900 Failed to read header Closed 01/07/2016
related to Bug #5327: ft2900 header error Closed 11/05/2017
duplicated by Bug #7721: Yaesu FT-1900 invalid header Closed 03/22/2020
duplicated by Bug #7803: FT-1900E Invalid header Closed 04/15/2020
duplicated by Bug #7125: FT-2900 Closed 09/26/2019

History

Updated by Barry Smith over 2 years ago

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

Updated by Barry Smith over 2 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)

Also available in: Atom PDF