Bug #1655
closedCannot upload to Yaesu FT-817ND (US)
0%
Description
I get this error when uploading to FT-817ND (US) from a Mac. I have no problem downloading, only uploading...
"Failed to communicate with radio: Radio did not ack block 0"
Files
Related issues
Updated by Filippi Marco almost 10 years ago
- Status changed from New to Feedback
- Assignee set to Filippi Marco
To help you we need some more info, please provide a debug.log (click the link below for instructions).
Please also try uploading to radio immediately after the image download finished without modifying anything.
Tnx
73 de IZ3GME Marco
Updated by Filippi Marco almost 10 years ago
FT817 and FT897 use same cloning routines so both model can suffer of the very same problem.
From early test it can be a timing problem ...
Updated by Darren Nelsen about 9 years ago
Still having this issue with latest daily build (chirp-daily-20150202.app). Attached is the debug.log.
Updated by Albert White over 7 years ago
Hi,
I'm seeing the same error message uploading to an 817ND (non US version). The debug log is from:
- Start Chrip and download from the radio. This is over a bluetooth adapter but the download is fine.
- Upload what we just downloaded without modification.
I've tried increasing the sleep() times in _clone_out of ft817.py but the buf is still empty after we read it.
Updated by Bernhard Hailer almost 4 years ago
- Priority changed from High to Normal
- Chirp Version changed from 0.4.0 to daily
- Model affected changed from FT-817ND (US) to Yaesu FT-817ND
Have you been able to resolve this on your own since you submitted this?
Both of you are experiencing cable issues. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
Updated by Bernhard Hailer almost 4 years ago
- Status changed from Feedback to Closed
- Assignee deleted (
Filippi Marco)
I'm closing this due lack of feedback.
Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
Windows notes: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php
MacOS notes: this OS is apparently very picky about USB to Serial cables. From what I heard, only (genuine) FTDI-based cables can be made work.
You must have the KK7DS Python runtime for Mac OSX installed.
Linux notes: Linux generally is quite good with USB to Serial converter drivers. The most likely cause for grief is a connector which doesn't provide good electrical contact.
Bluetooth notes: connections often suffer from timing issues, please try a cable instead.