Project

General

Profile

Actions

Bug #11573

open

FT-4XR download fails

Added by Thomas Larsen about 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
09/26/2024
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
Yaesu FT-4XR
Platform:
Windows
Debug Log:
I read the instructions above:
Yes

Description

(Describe what you were doing)
Trying to download the memory from the FT-4XR

(Describe what you expected to happen)
Memory being downloaded to Chirp, like it does from my other radios.

(Describe what actually happened instead)
It immediately fails after pressing OK to download (less than half a second).

To replicate:

  1. Connect cable to USB and radio mic port
  2. Switch radio on
  3. Select Radio > Download from Radio from the Chirp menu
  4. Select port (in my case COM4: USB Serial port), Vendor (Yaesu), and model (FT-4XR)
  5. Click OK
  6. I immediately (no delay at all) get error message: "Failed to communicate with radio: Incorrect echo on serial port. Radio off? Bad cable?"
  7. Radio flashes --TX-- in display

(Has this ever worked before? New radio? Does it work with OEM software?)
The radio is new.

The cable is also new: MIRKIR FTDI multiple-tip cable. I'm using the adapter pigtail marked "M-88S/3688S etc..", which is a 2.5mm jack adapter pigtail, connected to the radio mic port.

Yes, the cable works fine with the Yaesu FT-4X_USA_EXP_1.00 software and this radio. No issues reading the radio memory, nor writing to it.

The cable also works fine with Chirp and my Yaesu FT-60 (with a different adapter pigtail of course - in that case the 3.5 mm 4-ring jack marked "Y-VX160/VX168 etc..").

Some communication is working with the FT-4XR. If I select a different driver - say, FT4VR or FT65R - I get a "Failed to communicate with radio: Incorrect ID read from radio" error.

(Other information)
I realize a nearly identical Bug #10466 was closed a 18 months ago; however in that case there was a some progress before it failed, which is not what I'm seeing. For me, it fails right away, and the error message I'm getting is also different.


Files

config.txt (1.58 KB) config.txt Thomas Larsen, 09/26/2024 11:27 PM
Untitled.csv (245 Bytes) Untitled.csv Thomas Larsen, 09/26/2024 11:27 PM
debug_log.txt (45.2 KB) debug_log.txt Thomas Larsen, 09/26/2024 11:27 PM

Updated by Thomas Larsen about 2 months ago

[Uploaded from CHIRP next-20240926]

Actions

Also available in: Atom PDF