Bug #10432
closedYaesu FT-60: Will not upload, from computer to radio. Radio to computer works fine.
0%
Description
Error Message: "Failed to communicate with radio. Radio did not respond."
Bug log see attached.
My circle of "experts" all think it's a radio/hardware problem.
Note: failer both windows 10 & windows 7
Thank You
Related issues
Updated by Dan Smith about 1 year ago
This is a common thing with the FT-60, yes. Please see the discussion and ultimate resolution in #10220.
Updated by Dan Smith about 1 year ago
- Related to Bug #10220: Can not upload to FT-60R added
Updated by Dan Smith about 1 year ago
- Status changed from New to Closed
- Assignee set to Dan Smith
- Target version set to chirp-py3
Updated by Dan Smith about 1 year ago
- Status changed from Closed to New
- Assignee deleted (
Dan Smith)
Updated by Jerry Davis 5 months ago
I think your "Circle of Experts" are incorrect, in this case.
I have the RT-Systems cable, and I can download just fine, I can't upload at all.
I have tried every way possible.
- Linux chirp-next
- Linux legacy (via flatpak)
- Windows
every one of them, will download, but not upload.
So what is the status of this?
Jerry WF5W
Updated by Dan Smith 5 months ago
- Status changed from New to Closed
- I read the instructions above set to Yes
I think your "Circle of Experts" are incorrect, in this case.
It's been confirmed by multiple people in many different configurations.
I have the RT-Systems cable, and I can download just fine, I can't upload at all.
This is the exact behavior others see. It's not necessarily a problem with the cable, so much as some sort of weird compatibility thing. I don't have an FT-60 myself so I can't really say why, but because so many people have confirmed that a better cable solves the problem, it's hard to argue.
I have tried every way possible.
- Linux chirp-next
- Linux legacy (via flatpak)
- Windows
every one of them, will download, but not upload.
You've confirmed the exact input criteria to the problem that others have solved with a different cable.
So what is the status of this?
The status is that we don't have any additional information to offer you, other than that using a better cable works for everyone who has tried. Nobody on the CHIRP dev team (that I know of) is spending nights and weekends trying to figure out why. If you want it to just work, please use the solution in #10220 :)