CHIRP

Hi to all.

This can be a sign that we have a new version of this radios on the wild.

Can you provide a serial log for it? (know how to do it here http://chirp.danplanet.com/attachments/2257/how%20to%20portmon.doc)

Make a patch/fix for this is easy, just remove the spaces in the second ID for the QYT KT-8900 as it is matched with a "if radio._id2 not in id2"

But a peek in the serial log will provide (maybe) more intel about it to pin-point some other clues that may lay in the former space filled area od the id2.

73 de Pavel CO7WT.

Sorry, but my computer is windows 10 on a 64 bit system. So, I can not generate the serial log you requested.

This KT-8900 is about 1 year old. I got it from a friend. There is a startup menu function available to enter a "passcode" into the radio. This passcode ends up being the "extra ID wrong" that chirp does not like. I have not been able to find a way to null out the passcode. The radio insists that six characters be entered before it will process the passcode and go on to normal operation.

Thanks for a great software package and outstanding support.

K0WB - Bill

William Besore wrote:

There is a startup menu function available to enter a "passcode" into the radio. This passcode ends up being the "extra ID wrong" that chirp does not like. I have not been able to find a way to null out the passcode. The radio insists that six characters be entered before it will process the passcode and go on to normal operation.

Good info. That sheds some light on what the "second ID" is used for. Since CHIRP ignores any passcode, really isn't any need to match anything. All CHIRP really needs to do is check to see that 16 bytes have been returned and continue if they have.

Jim

HI all,
I have an SURECOM KT8900D and me too don't communicate with CHIRP (last version CHIRP daily-20171104).
With the original software there is not problem to connect to the radio.
what can I do?
My MTU-Version is VC4284
thanks in advance
IW2-DRU