Bug #4101

juentai jt-6188 "radio did not enter clone mode"

Added by Trent morrison 12 months ago. Updated 8 months ago.

Status:In Progress Start date:10/01/2016
Priority:Normal Due date:
Assignee:Jim Unroe % Done:

100%

Category:-
Target version:0.5.0
Chirp Version:daily Platform:All
Model affected:KT-8900

Description

I'm using windows 10 64bit. Was finally able to use oem software successfully with uv2band_e_cps

Would love to get the issue figured out. What can I do to help?

debug.log (19.1 kB) Trent morrison, 10/01/2016 10:53 pm

device manager.PNG (52.6 kB) Trent morrison, 10/02/2016 09:45 am

debug2.txt (19.4 kB) Trent morrison, 10/03/2016 04:28 pm

btech.py - test driver for M2G314 MCU-Version (57.5 kB) Jim Unroe, 10/03/2016 06:33 pm

Associated revisions

Revision 2786:862dc68beeca
Added by Jim Unroe 12 months ago

[QYT KT-8900] Add Support for a New MCU-Version

This patch adds support for a newly discovered MCU-Version for
QYT KT-8900 and variants like the Juentai JT-6188 Mini.

related to #4101

History

Updated by Trent morrison 12 months ago

Debug file attached.

Updated by Trent morrison 12 months ago

Nont sure if this helps but I am using a MAXTOP usb programming cable with FTDI FT23rl chip

Updated by Jim Unroe 12 months ago

  • Status changed from New to Feedback

Trent,

Your radio doesn't appear to be responding to the clone request. Are you sure that it is the correct programming cable? In other words, does it work with the OEM software?

Jim KC9HI

Updated by Trent morrison 12 months ago

Hello Jim,

Thanks for taking a look.The answer to your question is Yes and No. Using the program software from the Miklor site I was unable to get it to work using the jt-6188 software package (UC_CPS), but it does work with the Kt-8900 software(UV2BAND_E_CPS).

i'm attaching a screen shot of my cables driver setting. Thanks for the help.

Updated by Jim Unroe 12 months ago

Trent,

Good. That rules out the programming cable being the issue. Have you tried the QYT KT-8900 in CHIRP yet?

Jim

Updated by Trent morrison 12 months ago

Here are the results using the QYT-Profiles

KT8900 = Radio identification failed
KT8900R = Radio did not enter clone mode
KTUV980 = Radio did not enter clone mode

Updated by Jim Unroe 12 months ago

Trent,

Apparently your radio has an MCU-Version that is currently unknown to CHIRP. Try KT8900 again and then include the debug.log file.

Jim KC9HI

Updated by Trent morrison 12 months ago

Lucky me! the requested debug file is attached.

Updated by Trent morrison 12 months ago

I am not sure if this helps but here goes. When selecting the jt-6188 profile, I get the "radio did not enter clone mode" error but nothing happens to the radio. However when trying the kt8900 profile the radio power cycles briefly and then i get the "Radio identification failed error"

Updated by Jim Unroe 12 months ago

Yes, this helps. Also, you should be selecting JT-6188 Mini, not JT-6188 Plus.

Jim

Updated by Jim Unroe 12 months ago

  • File btech.py added
  • Status changed from Feedback to In Progress
  • Assignee set to Jim Unroe
  • Target version set to 0.5.0
  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from (All models) to KT-8900
  • Platform changed from Windows to All

Trent,

Please give this driver a test. Here's how.

1 download the test btech.py driver module and save it to a convenient place
2 load CHIRP
3 click "Help"
4 enable "Enable developer functions"
5 click "File"
6 click "Load Module"
7 located and load the driver module saved in step 1

Now try to download from your radio using the following:

VENDOR = "Juentai"
MODEL = "JT-6188 Mini"

Report back the results.

Jim KC9HI

Updated by Trent morrison 12 months ago

Hello Jim. I tried the btech.py driver again and still no luck. Just to clarify, My radio is the jt-6188plus not the mini. Unfortunately I do not see that in the above notes. However I have tried the procedure with the mini and plus profiles to no avail.

Updated by Trent morrison 12 months ago

it worked, it worked it worked it worked.. i had tried a btech.py driver numerous times before to no avail and used the same btech driver that i found in another post tonight to the same result...noticed your driver was dated today and used the 6188 mini profile and it worked. I am super thankfull. Would you mind explaining to me what caused this issue. I'm fairly new to these radios and have found the process fascinating.

Updated by Jim Unroe 12 months ago

  • % Done changed from 0 to 100

Trent,

With what limited research I have done, I cannot find any difference between the Mini and the Plus except for the name printed on the case. What matters is that your radio responds to the request to begin cloning the same way as a QYT KT8900.

I have submitted a patch to add the "M2G314" fingerprint (what the OEM software calls the MCU-Version) so that CHIRP will now recognize the response from your radio. You can choose one of these aliases to program your radio.

VENDOR = "Juentai"
MODEL = "JT-6188 Mini"

VENDOR = "Sainsonic"
MODEL = "GT-890"

VENDOR = "Zastone"
MODEL = "MP-300"

Or the main selection that the above are an alias of.

VENDOR = "QYT"
MODEL = "KT8900"

The "JT-6188 Plus" selection is an alias of the WACCOM "MINI-8900" which your radio does not respond to.

Jim KC9HI

Updated by Steven Cox 12 months ago

I would like to add my confirmation of success in programming Juentai jt-6188Plus following these instructions and using py file referenced on this page. Thanks for the great work.

Steve K4EMX

Updated by Randy Nunez 8 months ago

I just received the Juentai JT-6188 Plus through Amazon. The Juentai JT-6188 Plus did not work for me (shows as WACOM 8900) but the JT-6188 Mini did (shows as QYT KT8900).

Updated by Jim Unroe 8 months ago

What is the exact error message? Attach the debug.log file.

Also available in: Atom PDF