Project

General

Profile

Actions

New Model #3657

closed

QYT KT-8900 (Not R Version)

Added by Stephen Ireland almost 7 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
05/16/2016
Due date:
% Done:

0%

Estimated time:
0.50 h
Equipment Loan Offered:
No

Description

Hi Folks,

Chirp will NOT detect the QYT KT-8900 (NOT R VERSION). The radio will NOT perform the "reset" that punches it into programming mode.

I have the "factory" USB-Serial cable talking beautifully with the radio; I can use the ORIGINAL release of the programming software (and the extremely rare VIP software to set band limits) to set all features.

Tested on Versions of Windows 7 and 10; Same issues. Tested on Linux. Same issues.

Firmware on the radio: MCU-Version 2.88.5.4

Note: I am no newbie at this; the drivers have been FULLY eliminated although the "original" programming cable uses a PL2303HX-A (ewww) !!!!

Further Reference: Even the latest QYT Programming software for the radio does not detect radios with the 2.88.5.4 firmware (available at http://www.qyt-cn.com/uploads/UploadFiles/Files/2015114103194608.rar) This suggests that developers may need to be aware that there are newer firmware versions around for this hardware, and that many of us have older firmware on our devices.

There are no point sending serial dumps from CHiRP as there is no radio detection taking place (otherwise I would).

73

Steve I
VK3VM / VK3SIR
(direct reply vk3vm @ hotmail . com)


Files

serial-dump.zip (1.09 MB) serial-dump.zip Serial Port Dump Dennis d'Entremont, 05/18/2016 11:42 AM
Desktop.zip (991 KB) Desktop.zip Captures plus Software (incl. VIP) Stephen Ireland, 05/18/2016 03:39 PM
UV_VIP_CPS_DUMP.zip (1 MB) UV_VIP_CPS_DUMP.zip Stephen Ireland, 05/18/2016 11:05 PM
Actions #1

Updated by Pavel Milanes almost 7 years ago

  • Status changed from New to In Progress
  • Estimated time set to 0.50 h
  • Model affected changed from (All models) to QYT KT8900
  • Platform changed from Windows to All

Hi Steve,

You mentions that you actually can make the radio work with the "ORIGINAL" (OEM) software; that's all we need.

Please make a serial port log of the communication process using the OEM software that you know works. Use portmon to capture the serial log: http://chirp.danplanet.com/attachments/2257/how%20to%20portmon.doc

We need actually two logs, one for a download (Radio > PC) and other for an upload (PC > Radio) since the QYTs uses and extra step in the upload and it changes from time to time.

Once you have the logs, upload them to this post and I will process it to make your radio supported on Chirp, it's all that simple. ;-)

73 Pavel CO7WT.

Actions #2

Updated by Stephen Ireland almost 7 years ago

Pavel,

Thanks. Will set up a "portmon" in a 32-Bit Win 7 VM (and I know this VM works); will also attempt a "Serial Port Monitor" V5 dump as well from the base 64-bit system. Give me a few hours to make this happen.

Regards,

Steve I
VK3VM / VK3SIR
(direct reply vk3vm @ hotmail . com)

Actions #3

Updated by Dennis d'Entremont almost 7 years ago

I have one of these KT8900s with the same issue. I used serial port monitor and did a dump of both a read and a write from the radio using the OEM software. I haven't used this Serial Port app but I did export to plain text all 4 of the "views" it has when running. I've attached the zip file. Hopefully that helps in some way.

Regards,
Dennis

Actions #4

Updated by Pavel Milanes almost 7 years ago

Dennis & Stephen,

Any logs of a serial port capture software is valid as it's setup in a way that I can get this:

  • Hex dump of the data, the default is almost always ASCII, and it's worthless as non printable chars get masked by a dot.
  • You can set/check the queue size for the biggest packet and it's about at least 256 bytes long, this is to not lose any byte on long packets.

Sure, I have the tools to automatically parse the portmon logs (I can even retrieve a partial radio image from it) and that makes the process a matter of minutes, but any other that meet the above points will do it, just will take more time to process.

I'm getting your file as a corrupted one, I'm downloading it for the second time... (slow internet here, sorry)

73

Actions #5

Updated by Pavel Milanes almost 7 years ago

Hi Dennis, yup, I got the file now.

The "Dumpview" is the one, it's of no value for a new radio, but it works for this with a known comm protocol aka: I can read it.

That file told me that you have an simple KT8900 (did you see the notice in the recent version when you tied to read it?)

I put recently a comment on the last version of Chirp just for this case, update your Chirp and try to read it, this time pay attention to the error's comment...

Spoiler: It will suggest you to use the Waccom Mini8900 instead as some units of the KT8900 behave as the Waccom Mini8900.

I call this ones "early KT8900" as by now all know variants use the default protocol in Chirp for the KT8900.

Stephen, please try that also.

73 CO7WT.

Actions #6

Updated by Dennis d'Entremont almost 7 years ago

Hi Pavel,

Weird, I did try both the Waccom Mini8900 as well as the KT8900. The KT8900 said that it couldn't find the radio and the Mini8900 said something about not being able to put the radio into clone mode. When using the Mini8900 it did blink the display on the radio for a second and seemed like it was going to work after.

Prior to trying, I did grab the nightly build for 5/17 and installed it. So the tests were done with the latest version I saw.

Any other ideas?

Thanks! 73

Actions #7

Updated by Dennis d'Entremont almost 7 years ago

I meant that it seemed like it was going to work but did not. That's when the error about going into clone mode came up.

I'll check at the additional information on the error next time I try. I'm not in from of that laptop right at the moment.

Actions #8

Updated by Pavel Milanes almost 7 years ago

Yes, there is a know bug about the Waccom Mini8900 and the BTECH 2501 not working on the first tries, please try it a few times.

73

Actions #9

Updated by Stephen Ireland almost 7 years ago

Hi Folks,

A complete set of PortMon dumps now included as promised.

All is in the ZIP file. Note that I have used the VIP software (included) to do the captures. There is an initial negotiation to put the radio into programming mode (ProgramMode.Log).

Regards,

Steve I

Actions #10

Updated by Stephen Ireland almost 7 years ago

Hi Folks,

oops... for some reason PortMon has NOT save it as Hex dumps... Will investigate and repost ASAP.

And NO... The WACCOM MINI-8900 does NOT WORK !

Regards,

Steve I

Actions #11

Updated by Stephen Ireland almost 7 years ago

Stephen Ireland wrote:

Hi Folks,

[ oops... for some reason PortMon has NOT save it as Hex dumps... Will investigate and repost ASAP.... No ... double-checked... The Dumps OK... ]

And NO... The WACCOM MINI-8900 does NOT WORK !

Regards,

Steve I

Actions #12

Updated by Stephen Ireland almost 7 years ago

Hi All,

Sorry for the crap above... made a mistake. Attached is the "portmon" dump produced EXACTLY according to the document supplied along with the standard CPS and VIP software used to create the dump.

73

Steve I

Actions #13

Updated by Pavel Milanes almost 7 years ago

Stephen Ireland wrote:

Hi All,

Sorry for the crap above... made a mistake. Attached is the "portmon" dump produced EXACTLY according to the document supplied along with the standard CPS and VIP software used to create the dump.

73

Steve I

Got it, I will process and report back later today.

73 Pavel CO7WT

Actions #14

Updated by Dennis d'Entremont almost 7 years ago

Hi Pavel,

I tried The WACCOM MINI-8900 multiple times in succession with the latest version of chirp and it doesn't work at all for me.

The screen on the radio blinks as if it is going to work but then chirp says "An Error has occurred. Error reading data from radio".

Actions #15

Updated by Stephen Ireland almost 7 years ago

No still issues... At least the Waccom selection gets closest causing the "reset" into Programming Mode... but then the detection fails. There is no radio "reset-into-programming-mode" taking place under the QYT settings.

Actions #16

Updated by Pavel Milanes almost 7 years ago

Hi to all.

This is a known bug with the WACCOM Mini-8900 and the some of the QYT KT-8900 that is a clone of the WACCOM (or vice versa), sadly I don't have much free time lately to craft a solution now; but this task is in #1 of priority on the TODO list.

The "reset" upon programming tell me that this radios are indeed a clone of the WACCOM (as it responds to the magic code to turn it into program mode) but then we have this radios insisting on sending a misplaced byte in whatever position it likes.

I have drafted a new strategy that I need to implement and test but it (maybe, 50% chance) requires some fundamental changes on the whole driver.

Sorry for the inconvenience.

73 Pavel CO7WT.

Actions #17

Updated by Bernhard Hailer almost 3 years ago

  • Status changed from In Progress to Closed
  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from QYT KT8900 to QYT KT-8900

I believe this radio is now supported. Please let us know in case closing this ticket was an error. Thanks!

Actions #18

Updated by Bernhard Hailer almost 3 years ago

  • Tracker changed from Bug to New Model
  • Subject changed from QYT KT-8900 (Not R Version) Not being detected at all. to QYT KT-8900 (Not R Version)
  • Equipment Loan Offered set to No
Actions

Also available in: Atom PDF