Bug #1397: FT-60 and FT-8800 Error reading echo (Bad cable?) - CHIRP

Actions

Copy link

Bug #1397

closed

FT-60 and FT-8800 Error reading echo (Bad cable?)

Added by Basil Copeland almost 11 years ago. Updated almost 5 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Jens Jensen

Category:

Target version:

0.4.0

Start date:

01/25/2014

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

all

Platform:

Windows

Debug Log:

I read the instructions above:

Description

As detailed in a thread to the mail list, I'm getting an "Error reading echo (Bad cable?)" trying to write to Yaesu FT-60 and FT-8800. I've replicated the error in daily builds 20131031 and 20140102. It does not occur with the current stable build, or daily build 20131002. So something changed between 20131002 and 20131031. While I've only tried the daily builds with FT-60 and FT-8800, and no other Yaesu model, that it occurred with two Yaesu models means that it may be related to code that would apply to all Yaesu models. I'm attaching a debug.log and an ft60.img file.

Files

Download all files

ft-60.img (27.9 KB) ft-60.img		Basil Copeland, 01/25/2014 06:07 AM
debug.log (9.48 KB) debug.log		Basil Copeland, 01/25/2014 06:08 AM

Actions

Copy link

Updated by Basil Copeland almost 11 years ago

File debug.log debug.log added

Actions

Copy link

Updated by Jens Jensen almost 11 years ago

Status changed from New to In Progress
Assignee set to Jens Jensen
Target version set to 0.4.0
Model affected changed from Yaesu FT-60 and FT-8800 to all

From email thread, seems like changes made in 2013-10-31 have broken this for Basil:

From: Basil Copeland blcjr2@gmail.com;
To: Milton Hywatt mhywattt@yahoo.com; Discussion of CHIRP ;
Subject: Re: [chirp_users] Chirp & FT-8800
Sent: Fri, Jan 31, 2014 8:42:21 PM

Okay, I gave it a try. No joy, with either the FT-60 or FT-8800. Same "bad cable?" error. I have to go back to 2013-10-27 to find a build that doesn't generate this error.

Basil
KE5GAE

To: Discussion of CHIRP
Sent: Thursday, January 30, 2014 4:28 PM
Subject: Re: [chirp_users] yaesu 897

FWIW, I made a global change that moved the opening of the com port for upload operation to before the clone message is displayed.
This was done because in my testing with FT-90, it worked fine on linux, but radio would not go into clone mode on windows xp.
I suspect it had something to do with port lines (DTR/CTS, etc) or with my homebrew cable, but whatever it was, opening the port before displaying the clone instructions worked for me across platforms, and so far have not heard any other negative side-effects.

http://chirp.danplanet.com/issues/1187#note-6
http://chirp.danplanet.com/projects/chirp/repository/diff/chirpui/mainapp.py?rev=1c8ef954a71b&type=sbs
I make this comment only in the off chance that it is somehow related to the issue being described here.

-Jens

Actions

Copy link