Bug #7037
closedQYT KT-7900D - Radio did not enter clone mode
0%
Description
- I have downloaded the latest Chrip installable from the web site (date 05/09/2019).
- I connect my FTDI chip set based programming cable (the same used for programming ICOM sets like ICOM IC2200H). It is detected and loaded on COM6
- I connect the pin to the DATA port on my QYT KT-7900D
- I switch on the radio. It opens up as expected, and what ever frequencies I have manually entered is visible.
- I open Chirp choose the option download from radio, and choose the COM Port, Make and model number of the radio.
- I did get a warning that the driver used is still not the final one. I proceed further.
- I can see a scroll bar moving really quick followed by the error message "Radio did not enter clone mode"
I check up the log file, and the last few lines (after the error) are:-
[2019-09-05 22:19:30,936] chirp.ui.reporting - DEBUG: Reporting model usage: QYT_KT7900D,download,True
[2019-09-05 22:19:30,936] chirp.ui.reporting - DEBUG: Reporting exception
[2019-09-05 22:19:30,936] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Radio did not enter clone mode ---
[2019-09-05 22:19:30,936] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 68, in
AttributeError: 'NoneType' object has no attribute 'split'
Note: Please reach out to me in case you need any further information to trouble shoot the issue. I tried programming using an old version of CPS provided by QYT, but that also did not work out.
Files
Updated by Bernhard Hailer about 4 years ago
- Status changed from New to Feedback
- Model affected changed from (All models) to QYT KT-7900D
This looks like a cable / driver / connector issue (maybe your Icom cable is not correctly wired for a KT-7900D?). 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.
Also see MacOS Tips!
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.
Let us know whether you were able to resolve.
Updated by Bernhard Hailer almost 4 years ago
- Status changed from Feedback to Closed
No more feedback by submitter.