CHIRP

Hi Matthew,

Thanks for submitting the needed information. I will try to get this submitted today.

Jim KC9HI

Matthew,

Are you sure that a radio with the M3B064 MCU Version doesn't have an "extra ID"? Or does it use the second "extra ID" that was added to the current driver back in September of 2021?

I'm going to assume the latter is true and attach the driver that I currently expect to submit. Would you please test it in order to confirm the second "extra ID" works with your radio? If it doesn't, attach a debug.log file that I can study.

Thanks,
Jim KC9HI

Matthew Breit wrote:

Hi Jim,
Thanks for this! Your driver works fine over here. It's slower, but still very usable and it makes sense after I read the notes about the static delay.
I found the driver I posted from some other post buried in here somewhere; yes it is pretty old I see now.
(I downloaded the daily about two days ago and got the 'radio identification failed' error, which prompted my searching).

Thanks so much again!

• Matt

Yeah... the "slower" has been a problem for a few year. Using the older driver that you were using probably predated the change that made things slow, so you never noticed.

Recently I have been making an effort to figure out what is causing the driver to be slow at uploading and try to eliminate it. A new build was released today that should help but I am even working on a better solution.

The test driver that I just attached to this issue incorporates this new method. Would you please test this and let me know if it works or fails for you. I am anxious to get this new method tested. If I can get favorable report from several volunteers I can get it submitted.

In the mean time I will submit a patch to add the M3B064 MCU Version support to CHIRP. Thank you for your help.

Jim KC9HI

A patch has been submitted to add this new MCU Version for the KT-8900R. Support will be in the next CHIRP daily build following acceptance.

Jim KC9HI

Applied in changeset commit:4d991cdfc502.