CHIRP

Note:
Juentai JT6188, QYT KT8900, Luiton LT8900, Waccom Mini-8900 are essentially the same radio.

Thank you for that information. I've looked on the models supported on the daily build and could not find any of those you listed as supported. Am I missing something?

Has anyone found a CHIRP radio in the program that will read the Juentai JT-6188. The program that came with the radio is not operating coreectly

Any possibility of the Juentai JT-6188 being added in the future?

Jim Unroe wrote:

I will try to add these radios after I get the BTECH UV-5001 and UV-2501 added. They appear to be variants of one another.

Excellent, I bought one of these a few days ago and the official programming software runs only on Windows, and I can't get it to communicate with the radio under VMWare Fusion on my Mac.

John LaMartina wrote:

Note:
Juentai JT6188, QYT KT8900, Luiton LT8900, Waccom Mini-8900 are essentially the same radio.

the btech uv-2501 should work with all the above listed radios sence they are essentially the same except for the Luiton LT8900 but it may even be the same as the Luiton lt-825uv

Zastone MP-300 is also the same radio. This radio family is quickly becoming for mobiles what Baofeng is for HTs, so supporting it will make a lot of people very happy.

From what I understand, The Moonraker MT-270 is also a clone of this radio. The CPS software supplied is not the greatest, and it would be great if a solution could be created for these various alter-ego's.

Thanks. Dean

Please be patient, we are working on the BTECH driver and later we will address this alike radios.

This radio platform is becoming in the Baofeng for the mobiles just like Bruce mentioned, so it will be (possibly) easy to add support for them if the factory don't get to picky about the firmware. But first we must have a working and stable driver to work with as base.

Please follow the BTECH issue #3015 to know about it's progress, once it's completed then we will need your help to get support to this radios (serial logs, beta testing, etc)

73 from one of the BTECH driver developers.

I purchased one of the new QST KT-8900R. Tried installing the software with numerous failures. I used a new cable from Amazon which apparently has a dam Generic Prolific IC in it. I intentionally went to Amazon and to an American firm to purchase it to avoid just this problem...So far I've been able to program just one repeater , tone, and offset. After that forget it....I spent hours trying to manually program a second one with no success. Now on top of this I purchased this Radio on Aliexpress.com. I've always been careful who to pick by the number of sales they made. Well I won't use this guy anymore....LOL. Its been an experience. First I order this Radio in January, It wasn't shipped until February 15th.

Didn't arrive until two days ago. I ordered the cable a month ago and had it sitting on the shelf. Well I exceeded the Return date for the as well. Now the Icing on top of the cake. I specifically ordered the one does 220-260Mhz. I know what your thinking......you're right! I go the 240-260 MHZ. Version......It's not worth the hassle to send it back and it would be 1/2 the cost of what I paid for it. So now I have to find a new Prolific cable that will Actually function so I can at least use it for a dual band radio. It's strange I have the Baofeng U/V3R, the U/V 5RA+ and never had a problem. I finally get a mobile and its a fricking nightmare...........I won't be buying another one..........

Alex,

I only know of 2 vendors that actually sold programming cables that contained a "genuine" Prolific chip. One went out-of-business. The other switched over to selling programming cables with an FTDI USB-to-TTL chip.

Unless you specifically purchase a programming cable with an FTDI chip, you should count on getting a programming cable that has a counterfeit Prolific chip. Unfortunately that is the reality of it.

Your mistake is wanting a programming cable with a Prolific chip. If you are going to purchase another programming cable, you should look for one that has an genuine FTDI chip. It will cost you around $20-$25. The latest available FTDI device driver should work fine with it.

Counterfeit Prolific chips work fine with Windows if you download, install and select an older device driver from 2007 (Prolific device drivers since around 2008 are intentionally incompatible with counterfeit Prolfic chips). The majority of my programming cables have a counterfeit Prolific chip in them and they work fine plugged into my Windows 7 64-bit computer.

Jim

We are looking for owners of the Juentai JT6188, QYT KT8900, Luiton LT8900 and similar radios that can capture the serial transfer while downloading from the radio using the OEM software.

This will require the use of a software called Portnom running on a 32-bit Windows Operating System (XP, Vista, 7, etc.). Unfortunately Portmon won't run properly on a 64-bit Windows OS.

Portmon can be download from "Microsoft":https://technet.microsoft.com/en-us/sysinternals/portmon.aspx

Portmon should be configured with...

HEX/ASCII mode set to HEX
Time Format set so that the yellow clock icon is showing
The "Max Output Bytes" under Option is set to MaxBytes = 512

If you have a radio that hasn't been submitted yet, then capture the download, ZIP the log file, name it with the Brand/Model and attach it to this issue.

Thanks in advance.
Jim KC9HI

I have a QYT KT8900 and Windows XP (32bit).
Do you want only one logfile or should I make several with only one data-change in each?

Thank you for the work you put into this!

-Sindre

Hi Sindre,

A single log file will be sufficient for now.

Thanks,
Jim

CHIRP daily-20160323 added support for the WACCOM Mini-8900 Plus

A patch has just been submitted to add support for the QYT KT-UV980. If accepted, it will be in the next daily build.

There are no settings menus yet but all of the per-channel settings have been implemented.

Jim KC9HI

Thanks to Kevin & Sindre for the logs.

In the developer queue there is a patch now with the support for the QYT KT-8900 radio, it appears to be a predecessor of the BTECH 2501+220.

I noted in the Internet that this radio is advertised also with a variant of 2m/1.25m (137-174/230-240 or so), there is anyone out there with a radio with this configuration?

If you have one of this we need your serial log (QYT KT-8900 with 220 Mhz band) to be able to disambiguate from one or the other model.

Support for this radio is conditioned to the patch being approved by the main developer after inspection.

73 Pavel.

Pavel Milanes wrote:

Thanks to Kevin & Sindre for the logs.

In the developer queue there is a patch now with the support for the QYT KT-8900 radio, it appears to be a predecessor of the BTECH 2501+220.

I noted in the Internet that this radio is advertised also with a variant of 2m/1.25m (137-174/230-240 or so), there is anyone out there with a radio with this configuration?

If you have one of this we need your serial log (QYT KT-8900 with 220 Mhz band) to be able to disambiguate from one or the other model.

Support for this radio is conditioned to the patch being approved by the main developer after inspection.

73 Pavel.

Was told that is a KT8900R special made by http://www.brickolore.com/2015/12/qyt-kt-8900r-tri-band-including-220.html hope this helps.

Kevin Echstenkamper wrote:

Here is a LOG file from a QYT KT8900

Sindre Asser wrote:

Hello again Jim, sorry for the late reply.
Here is a readout from QYT KT8900. On the miklor-page I use the software version labeled "E". I do not know if this is a model variant of the radio or simply a different version of the program.
Let me know if there's anything else you need :)

Hi, can you please repeat the process with a UPLOAD to the radio with the OEM software?

I have identified a problem on the BTECH 2501+220 UPLOAD and this radio appears to be an ancestor of this one and maybe it has the problem too.

I need a serial log of portmon with the OEM software doing an upload of the data to the radio.

Thanks in advance, Pavel CO7WT.

Thanks Sindre and Kevin,

I will parse the logs to get more knowledge about these radios.

73

The logs I sent you is the OEM software version, not a work around version.

Dale Miller wrote:

Here is the logs for Juentai JT-6188Mini
I got the Read, Write and Open program in the zip file.

Dale, KC2CBD

Thanks, Will process it tonight, Can you post a log for the upload?

73 Pavel.

I did the Upload(write) Download(Read) and start up software.

Is Chirp going to be able to program the 2 tone and 5 tone?

Hi again!

It is very good that we soon can update the memory channels on the radio using Chirp. Of course it would have been nice if we could use all the other options too (eg 2/5 tone as Dale mentions).

(I use QYT KT8900)

If you want I can create documentation with which options are available in OEM software, and I can also create multiple capture-files with minimal data changes in each file (of course with a description of what changes were).
Another thing that is interesting is that OEM software is able to upload / download only portions of memory to the radio without transferring all data (channels, options, 2 tone / 5 tone / DTMF). Do you want an example of each of these transfers? Maybe it will be easier to associate an address to a value?

-Sindre

Thank Dale,

Now the log are in the way it must be (I checked this time!), I will parse it on the night and will submit the patch as soon as possible.

About Chirp just updating parts of the radio and not the full radio: This is not the way Chirp is intended to work, so it will be difficult to implement.

We re waiting for ending the basic support for at least the declared radios in the related issues to start working on the settings part. So wait for it.

73

My QYT-8900R S/N is 1601152691. Let me know if you need anything from it.

Hi Michael.

You are welcomed to help, we need a download & upload serial log from that kind of radios, see this for instructions about how to do it:

http://chirp.danplanet.com/attachments/2257/how%20to%20portmon.doc

When you have the logs please zip them and upload it to this thread issue.

Thanks your your cooperation.

73 CO7WT Pavel.

Are you still in need of Juentai JT-6188 files?

Jan Allbright wrote:

Are you still in need of Juentai JT-6188 files?

Thanks Jan, but no.

The Juentai JT-6188 is supported now as a clone of one of the QYTs (see the supported radios's page on the wiki)

73 Pavel.

I just tried the latest build chirp-daily-20160402.app.zip and am unable to read data from my Juentai JT-6188Mini using the QYT KT8900 option.

With a JT-6188 and chirp-daily-20160402..
Selecting QYT -> KT8900
Identifying radio gets about 1/2 bar and then errors
Selecting QYT -> KT-UV980
Identifying radio gets full bar and then errors and radio chirps

The radios covered in this driver that has a second id on the ident process are affected by a bug on the driver about the timeouts chaining together in the second id processing and the result is the timeout and reset of the radio, as many of you has noticed.

Models affected are BTECH 2501+220 & QYT KT8900 (& JT-6188 as this is a clone of the QYT)

I was working on a solution on the weekend, a patch is on the developer queue now with the solution to this issue.

Next version of chirp will have this bug fixed.

Cheers, Pavel.

It works...now if you all can get the extras working in the future that would be nice.

Thank You!!

Dale
KC2CBD

Sorry to say it works not with my Juentai-6188 Mini

Ver: 20160412

Setting: QYT, HT8900
Error reading from radio

Interestingly...
Setting: QYT, KT-UV908
Radio Ident Failed

-73
W0VSO

Jan, check your email.

I have a request for help from your side about the problem.

73, Pavel.

Ok, working with Jan I found that his JT-6188 is NOT a clone of the QYT KT8900 as we have found already, but a upgrade copy of the Waccom Mini-8900.

Searching the net I see that Junetai is releasing a new ugraded model JT-6188Plus (www.chinajuentai.com/product_detail.php?id=175) and maybe Jan got one of this or a kind of JT-6188mini Gen 2...

We are working on that, just to let you all know.

I will be the full next week out of town and I don't know if where I go there is a internet access, just wait for me, I willl try to solve this issue with the JT-6188 before departure.

73

I worked with Pavel to get a decent portmon capture file and wonder of wonders the radio both downloaded and uploaded.
The down / up does not appear to work without portmon running (!?!).

Thanks to Pavel for all the hard work!

73 all

Jan Allbright wrote:

I worked with Pavel to get a decent portmon capture file and wonder of wonders the radio both downloaded and uploaded.
The down / up does not appear to work without portmon running (!?!).

Thanks to Pavel for all the hard work!

73 all

Yes Jan, it's really strange, it's like a timing issue, the portmon utility slow down the things a bit, maybe the driver needs to slow down on ceirtain points.

I need you to do a serial capture (down/up, both of them) with portmon and the +OEM software+, not chirp this time. (upload the files to this issue and/or email it to me)

From there I will profile the timing and will try to determine where to put a pause for the driver to work reliably.

73 Pavel CO7WT

For the users that like to be on the bleeding edge, here (http://chirp.danplanet.com/issues/3527#note-21) are an updated version of the driver with instructions about how to use it.

+It has this improvements:+

• The process of get into clone mode is fixed (yeah, it was broken, it was not trying 3 times as coded, it was failing after just one attempt) and you may get rid of the problems like "my radio does not work in the first try" or "it does not work from a cold start"
• Added a new variant (Gen2?) of the BTECH UV-2501+220
• Add support for the Sainsonic GT-890

This changes are on the developer queue and is a matter of time to get into the daily Chirp.

Enjoy and report back failure or success.

73 Pavel CO7WT

Roger roger
Give me a day to setup and will get back to you.
Portmon + http://www.miklor.com/KT8900/software/JT-6188_CPS%20042615.rar software

• 73

I've noticed there is a jt6188 mini and a jt6188 plus, it's there a difference between the two? I have the plus and have tried to read it with chirp (under the qyt-kt 8900 setting) but it fails.

I've noticed there is a jt6188 mini and a jt6188 plus, it's there a difference between the two? I have the plus and have tried to read it with chirp (under the qyt-kt 8900 setting) but it fails.

Sorry for the duplicate. Mobiles do weird things.

Hi Robert,

To support the "JT6188 Plus" we need a serial port capture for that radio, instructions on how to do that are here http://chirp.danplanet.com/attachments/2257/how%20to%20portmon.doc

If you like to use Chirp with your radio I need the serial port captures to make it happens...

73 Pavel CO7WT

Paul Schubitzke wrote:

I don't know if anyone knows this or not, but I was able to program my JT-6188 Plus using the Sainsonic GT-890 profile in CHIRP. Selecting this model (Sainsonic GT-890) allowed me to download, configure and re-upload to my Juentai JT-6188 Plus. I hope this helps others as using the Chinglish software that came with the radio was driving me nuts!

I wasn't very clear ... I was able to use the Sainsonic GT-890 profile IN CHIRP to program my JT-6188 Plus. Sorry for the SPAM

Thanks Paul! Just tried your suggestion and it worked like a charm on my 6188-Plus.

Paul Schubitzke wrote:

I wasn't very clear ... I was able to use the Sainsonic GT-890 profile IN CHIRP to program my JT-6188 Plus. Sorry for the SPAM

Hi Paul and Jason,

I'm very interested in a debug.log from chirp of a successful programming of the Juentai JT-6188 Plus as the Sainsonic GT-890 (check this to know how to find it: http://chirp.danplanet.com/projects/chirp/wiki/How_To_Report_Issues), also please note that in the today version of Chirp the Sainsonic GT-890 was REMOVED from the listing because it's a clone of the QYT KT8900.

From that info I can tell you that all models we know so far of the Juentai JT-6188 (Mini & Plus) and all the variants of the Sainsonic GT-890 are indeed clones of the QYT KT8900.

So to program one of these you will have to select the QYT KT8900.

We are working on a solution to bring the clones to the UI to make the life easier fo you (the users) with all this clones, but it will take time before it hits the street.

73 Pavel CO7WT

What I can tell you for certain, is that every model I tried, the QYTs, the TYT's etc, all failed to identify the radio.
I fought with it for hours. As soon as I tried the Sainsonic GT-890, it immediately found the radio and I successfully programmed the JT-6188 Plus. I used the radio all day today in the car and at the base and had zero problems. I'll see what I can do about getting you a debug.log in the next day or so.

First of all, thank you for CHIRP. It is awesome software for easy programming of difficult radios!
I downloaded the latest daily this morning, and this time was able to program my radio using the QYT KT8900 profile. I did notice that the Sainsonic GT-890 profile had been removed.
So for all trying to program the JT-6188, using the QYT KT8900 profile does seem to work perfectly now.

Thanks!

Paul
W0PWS

Hi,
I've updated CHIRP and it doesn't work anymore with my QYT KT UV980. The radio reboots when the software shows "Identifying radio" then the download fails.
So, I just reinstalled the "20160401" release which works fine.

Robin

Robin Pierre wrote:

Hi,
I've updated CHIRP and it doesn't work anymore with my QYT KT UV980. The radio reboots when the software shows "Identifying radio" then the download fails.
So, I just reinstalled the "20160401" release which works fine.

Robin

Hi Robin,

I'm very interested in your debug.log file, please do a try with the last version and after failure find the debug.log of chirp and post it here.

Hint: Windows Key + R, type %appdata%, a explorer will open, on it a folder called Chirp, inside you will find the debug.log

This is to understand what's going on.

73

Mathew Mirabito wrote:

I have attached a portmon using the "UV3BAND" software to read and write channel values to the KT-8900R.

For reference, I started the portmon, waited a few moments after the portmon screen stopped, read the channel data, waited a few moments after the portmon screen stopped, and wrote the data back to the radio.

Many Thanks !

We was lacking a good portmon serial log from this radio to be included in Chirp, I'm processing it ASAP.

Expect support for it on a few days/weeks. 73 CO7WT.

Hello again.
(Sorry for the late response, I've been busy)

I still can not download or upload to my KT-8900 using CHIRP (Linux / Ubuntu).
When I use the original software the radio reboots when I select the COM port (before any data transfer). After this I can download and upload without any problems.

When I use CHIRP (QYT KT8900) the radio also reboots itself and CHIRP gives an error message before the reboot is completed: "Invalid header for block 0x0000".

In the portmon file I uploaded the end of March I have only captured the part after the COM port is selected (Which is after the radio has rebooted).

It is possible (in CHIRP profile) to remove something from the beginning of the transmission so it does not tell the radio to reboot?

Sure, it helps a lot, you have a new (unsupported yet) variant of this radios.

Check your email!

Thank you Pavel !!!!
Upload & download works perfectly now.

I notice in Settings/Other Settings that the frequency bands are not adjustable
I am guessing this is hard-coded into the radio.

Thank you for all your hard work!
Noel

should we open a separate ticket for this?

Anthony,

Yes. This radio does not appear to be related to the radio models covered by this ticket. I would open a separate issue for the LT-725uv.

Jim KC9HI

Jim Unroe wrote:

Anthony,

Yes. This radio does not appear to be related to the radio models covered by this ticket. I would open a separate issue for the LT-725uv.

Jim KC9HI

request opened http://chirp.danplanet.com/issues/3745

So how do you know which "flavor" your Juentai is?

Jan Skogheim Allbright,

If you are referring to the mini or plus model, it is written on the top right of the radio just above the volume button. Mine reads "JT-6188PLUS"

de KM4ACK

I have the "Mini" and was under the impression that there are a couple of different "types" (like the QYT KT8900) that might work with a given Mini .. or are all the Mini's now handled by the QYT KT8900 driver?

Jan Allbright wrote:

I have the "Mini" and was under the impression that there are a couple of different "types" (like the QYT KT8900) that might work with a given Mini .. or are all the Mini's now handled by the QYT KT8900 driver?

Hi Jan,

So far we (Chirp) know just one type of Juentai JT-6188 Mini that's a clone of the QYT KT8900, it has the same magic (special string you send to the radio to put it on clone mode) of all the modern QYT KT8900 and particular ID is "M29154" (same as one of the QYT KT8900)

If you think you have a new (unsupported) variant, please go to http://chirp.danplanet.com/attachments/2257/how%20to%20portmon.doc and follow the instructions and upload the serial logs to this issue for us to parse and give support to it.

73 Pavel CO7WT.

Thanks Pavel!

Hi.

I have just purchased a latest firmware Juentai JT-6188Plus. The new version with fan.

Have tried all the clones but with no success. No surprise there then (-:

Obviously a new unsupported variant.

Running Linux Mint 17.3 here.

Anything I can provide to help?

73 Wallace MM0AMV

Wallace,

Try installing daily build 20160507. http://trac.chirp.danplanet.com/chirp_daily/daily-20160507/

Then select Sansonic for your radio and GT-890 for the model.

It is the setup that allows me to program the plus models that I bought a couple of months ago.

Hope that helps!

Jason
KM4ACK

Hi Jason.

Using daily builds, currently 20160706.
Tried using the Sainsonic GT-890 but sadly no joy.
Thanks anyway.

73 Wallace MM0AMV

Hi Wallace,

Chirp's developer here; actually the Chirp driver for the Juentai JT-6188Plus, Jetstream JT2705M and Waccom Mini-8900 (all of this modes are a unique variant in this family) is unstable on windows and a no-go on Linux yet.

This variant of the family has specific requirements and are very picky on the communication process. Last week we conducted a few intern tests and the driver is more stable on windows but still a no-go on Linux (changes are not applied yet to the release versions), we learn some tricks on the process but we still need more time/tests to address this issue.

The lastest Chirp's versions do work in windows but you need a few tries to get it download/upload it correctly, BTW you don't need to select another vendor/model beside the proper one, as Chirp now support a feature called Aliasing_for_radio_clones

73 Pavel CO7WT.

Wallace Moodie wrote:

Hi.

I have just purchased a latest firmware Juentai JT-6188Plus. The new version with fan.

Have tried all the clones but with no success. No surprise there then (-:

Obviously a new unsupported variant.

Running Linux Mint 17.3 here.

Anything I can provide to help?

73 Wallace MM0AMV

Hi Pavel,
Nice to hear from "The Boss", and thanks for the info.
In the meantime I have manually programmed in the four local repeaters so no panic.
I guess the Linux version will be ready when it is ready. I can wait.
Just to touch another subject if I may.
Any news on the Yaesu FTM-400 ?
It is a pure bitch to program manually, and CHIRP would make is so much easier.
Best wishes from Scotland.
73 Wallace MM0AMV

Sindre Asser wrote:

When I use CHIRP (QYT KT8900) the radio also reboots itself and CHIRP gives an error message before the reboot is completed: "Invalid header for block 0x0000".

Hi,
Ticket http://chirp.danplanet.com/issues/3993 has a potential fix for this issue - maybe you can restest with that version, and report the status?

73,
Michael
OE4AMW

Michael Wagner wrote:

Sindre Asser wrote:

When I use CHIRP (QYT KT8900) the radio also reboots itself and CHIRP gives an error message before the reboot is completed: "Invalid header for block 0x0000".

Hi,
Ticket http://chirp.danplanet.com/issues/3993 has a potential fix for this issue - maybe you can restest with that version, and report the status?

73,
Michael
OE4AMW

Hello!
When I use the btech_2.py from post #16 in that tread everything worked like a charm. No need to change the delay. Both uploading and downloading is now working!
Thank you so much :)

Glad to hear it work & thanks for testing it.

Just for checking: what is your radio model and what flavor of Linux are you using?

73 Pavel CO7WT