Bug #9007
"Failed to read header" when reading from Yaesu FT-2900 with MARS mod
| Status: | New | Start date: | 04/23/2021 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | chirp-daily | |||
| Chirp Version: | daily | Platform: | Windows | |
| Model affected: | Yaesu FT-2900 |
Description
I have a Yaesu 2900 that has the MARS mod done to it, and I am trying to read/write the presets to the radio. When trying to read from the radio, I follow these steps.
- Connect FTDI cable between radio and computer
- Power on radio in cloning mode
- Start CHiRP
- Select radio->download from radio
- Set model to Yaesu FT-2900R/1900R
- Press Ok
- Hit "Set" button on radio to start upload.
CHiRP will then display the "Failed to communicate with radio: Failed to read header." message, and the radio will display an ERROR.
What I have tried:- Changing the sequence of these steps
- Factory resetting the radio
- Reinstalling the cable's FTDI and Prolific drivers.
- Restarting my computer
- Using a different USB port.
I am using CHiRP daily-20210416
When enabling developer options, I see the following in the log:
[2021-04-23 09:27:54,854] chirp.drivers.ft2900 - DEBUG: Header: 000: 56 43 32 33 01 02 c7 01 VC23.... 008: 01 01 00 00 00 00 00 00 ........ [2021-04-23 09:27:54,854] chirp.drivers.ft2900 - DEBUG: len(header) = 10 [2021-04-23 09:27:55,109] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:55,111] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:55,365] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:55,365] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:55,621] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:55,621] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:55,877] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:55,877] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:56,132] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:56,132] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:56,388] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:56,388] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:56,644] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:56,644] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:56,898] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:56,898] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:57,154] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:57,154] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:57,411] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:57,411] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:57,665] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:57,665] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:57,921] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:57,921] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:58,173] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:58,173] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:58,424] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:58,424] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:58,680] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:58,680] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:58,936] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:58,936] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:59,190] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:59,190] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:59,444] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:59,444] chirp.drivers.ft2900 - DEBUG: len(header) = 0 [2021-04-23 09:27:59,700] chirp.drivers.ft2900 - DEBUG: Header: [2021-04-23 09:27:59,700] chirp.drivers.ft2900 - DEBUG: len(header) = 0
I am eager to get this issue resolved, and will help however I can.
History
Updated by Jon C over 1 year ago
Potentially related: I have tried using a program called FTB2900 and received the following error there: "The radio identifier expected was X'564332300' but the identifier actually received was X'564332301'"
This program can be found on g4hfq's website.
Updated by Jon C over 1 year ago
- File ft2900.py added
I have found a related issue with a driver that works. I was able to load the driver through the "Load Module" dialogue. It appears to work...
Updated by Anthony Naia over 1 year ago
Jon, the latest daily release includes a patch for the FT1900/FT2900 to handle the MARS Mod. It's a separate entry in the model drop down [FT2900R/1900R(TXMod)].