Development work to begin as soon as the radio is received from BuyTwoWayRadios.com.

Mel Terechenok wrote in #note-1:

Development work to begin as soon as the radio is received from BuyTwoWayRadios.com.

Good luck, mine came yesterday and although the new programming software is better than what came before from Wouxun it's still a far cry from CHIRP or RT Systems Inc's tools.

Baby Steps -
Start Byte, command structure and encryption byte are known.
I can send a proper command and get the radio to respond with expected data.
Comm decryption appears to be working.
Decrypted data conversion shows reasonable values like WOUXUN, KG-Q10H, KG-Q332 for model info and 2021-12-24, VC1.00 which match the firmware version of the radio.

Still having trouble with proper checksum calculation though.

1 step forward--- 10 steps back
The radio is not reporting memory contents at a given address consistently. This has stalled development as the downloaded memory contents can not be trusted.

After studying the CPS packet transfers,I think I know what needs to be done to unobfuscate the data transfer. Gonna get back at it. Stay tuned.

I have most of the radio settings mapped. Still working on Channel memories due to Wouxun memory layout choices.

Mel Terechenok wrote in #note-8:

I have most of the radio settings mapped. Still working on Channel memories due to Wouxun memory layout choices.

Watching this closely - The Wouxun software is 'workable.' But I'm not having a fun time importing larger lists of stations for places that I travel. Thanks for your efforts!

I check this update log daily hoping that Mel will have cracked the code for this HT. The Wouxun CPS is atrocious at best. What is it about OEM CPS software that doesn't allow you to copy/paste large groups of frequencies in your list at one time? Such a simple, yet rare feature in anything except Chirp.

Regardless, here's hoping the KG-Q10H gets full Chrip support ASAP! :) Thanks for your efforts so far, Mel!

Still developing the driver. Channel memories are currently still a problem due to Wouxun attempts at preventing 3rd party programmers.

Mel Terechenok wrote in #note-11:

Still developing the driver. Channel memories are currently still a problem due to Wouxun attempts at preventing 3rd party programmers.

Just dropping by to see if there is any new news on this one
Hope y'all have a good weekend!

Started testing writes to the radio.
I can complete a write but the data is not 100% correct yet - likely due to Chirp to Radio memory location manipulation issues.

Working on debugging but I can change some settings and channel memories and the radio accepts them from Chirp.

Upload to Radio is working - All 999 Channel memories can be modified using Chirp.
Settings are also working, but the mapping of all available settings is still not complete.

This is all good news as the Wouxun obfuscation attempts has been remediated and Chirp can now fully communicate and handle the radio programming.

Mel Terechenok wrote in #note-18:

Upload to Radio is working - All 999 Channel memories can be modified using Chirp.
Settings are also working, but the mapping of all available settings is still not complete.

This is all good news as the Wouxun obfuscation attempts has been remediated and Chirp can now fully communicate and handle the radio programming.

I just wanted to take a second to thank you for all of the work you have put into this. I use chirp for all my other radios and appreciate you working to make the new Wouxun supportable.

Mel Terechenok wrote in #note-18:

Upload to Radio is working - All 999 Channel memories can be modified using Chirp.
Settings are also working, but the mapping of all available settings is still not complete.

This is all good news as the Wouxun obfuscation attempts has been remediated and Chirp can now fully communicate and handle the radio programming.

I have the radio arriving tomorrow and I would be willing to Beta test.

I'll be receiving a Q336 next week. I'd gladly beta-test it with the 336 to see if it works. It appears to be the exact same radio as the Q10H with regional differences.

Mel Terechenok wrote in #note-22:

Completed mapping the settings for Mute Mode, Scrambler, Compander, Favorite, Send Location and Call Groups on a per channel basis.
They will be available for configuration on a per channel basis using the Channel Properties feature.
Still working on confirming completeness and correctness of Download and Upload routines and mapping of all the other settings.

Any lock on the channel unlocking?

Hi Mel,

Just gave it a go - looks great! Thanks so much for doing this especially given how annoying they made it and how awful the OEM software is. Couple minor issues:

1. Looks like setting the channel Mode doesn't work at all - not just for AM. I had a few channels set to NFM accidentally and I couldn't get it to set them to FM using either the channel memory or the Properties window. It would let me select FM then just put the channel back to NFM. Once I set them to FM manually on the radio though, chirp read it back correctly.

2. CHIRP cuts off channel names too early. Looks like it only allows 8 chars where the radio can do more. Weirdly, the manual says it's limited to 8 chars, but it comes with channels labeled "2m Calling" and "440 Calling" so it must support at least 11...

Mel you are a god. As a mac user I haven't been able to program anything.

Where can I send a donation.

That said I can verify Justin's #1

to his #2 I will add that that centering items is not possible as it will not accept spaces as a character.

Tony, if you want to send something to Mel, do it directly. The donate button on the download page goes to me for running the project, but for something directed like this you should make arrangements with Mel directly to make sure the goodness goes to the proper greatness :)

Tony Politi wrote in #note-26:

Mel you are a god. As a mac user I haven't been able to program anything.

Where can I send a donation.

That said I can verify Justin's #1

to his #2 I will add that that centering items is not possible as it will not accept spaces as a character.

I can also confirm that my cheap Amazon bought Baofeng cable is able to program the radio.

Thanks guys. I will be working on the Mode column. Since the radio has 2 AM modes (Rx and RxTx), I will have to add some conditional logic to handle all the various modes correctly.

I will have to look into the names again....the names are able to be up to 12 characters and I have been able to use spaces and see all 12 in my testing. Not sure what you are seeing. Maybe make the columns wider to confirm they are not just being hidden by short width columns?

Either way. I will be verifying everything I can and making fixes as quickly as I can.

Mel Terechenok wrote in #note-29:

Thanks guys. I will be working on the Mode column. Since the radio has 2 AM modes (Rx and RxTx), I will have to add some conditional logic to handle all the various modes correctly.

I will have to look into the names again....the names are able to be up to 12 characters and I have been able to use spaces and see all 12 in my testing. Not sure what you are seeing. Maybe make the columns wider to confirm they are not just being hidden by short width columns?

Either way. I will be verifying everything I can and making fixes as quickly as I can.

Thanks for the beta!! I can read and write to my Q336. It saves all the pertinent info (confirmed with the stock programming software).

However, I get a " 'NoneType' object is not iterable" error going into the settings tab

Kevin S wrote in #note-30:

Thanks for the beta!! I can read and write to my Q336. It saves all the pertinent info (confirmed with the stock programming software).

However, I get a " 'NoneType' object is not iterable" error going into the settings tab

That means some settings are out of range. Most likely because the 336 and Q10H have different options or the data is in a slightly different memory location.
The Debug.log will tell you what the issue is. If you post it I can give it a quick look. Right now I am focusing on the Q10H but it is good to know the base comms and Ch memories seem the same. That means a 336 driver would not be hard to make at some point.

Kevin S wrote in #note-34:

Mel Terechenok wrote in #note-32:

Beta 1p1 - Fixes Channel Name entry limit of 8 Characters - New limit is 12 which is the max of the radio.

I am able to type more than 8 characters but when I change to the next line it drops everything 8.

To my issue of adding spaces that was not the issue. THere were spaces on the end of my string of characters once I removed them I was able to upload.

Mel,

12 character names are looking good! Thanks!

Disregard my issue had to close and reload Chirp now I can make 12 character names

Kevin S wrote in #note-34:

Thanks for the beta!! I can read and write to my Q336. It saves all the pertinent info (confirmed with the stock programming software).

However, I get a " 'NoneType' object is not iterable" error going into the settings tab

Here you are! Thanks

Kevin - your issue on the Q336 settings tab is due to a problem with at least the Scan Mode setting - likely due to slight memory map changes.

• SCANMODE_LIST[_settings. IndexError: list index out of range*

without having a 336 to test with - I won't be able to fix it right now as I would have to mess with radio settings to see what is at the address that Scan Mode is expected to be at.
Maybe after the Q10H driver is complete we can work together on the 336 specific memory map.
You might consider putting in a separate request for new model support for the 336.

Mel

Hi Mel,

Beta 1p2 fixes all the issues I've found so far! Thanks again!

Mel,

I haven't had cause to test the new color settings yet but I can confirm that download, modify, and upload of the beta 2 images work without issue!

Looks good Mel! Mine supports 20k steps and I confirmed that option is available in chirp.

@Mel Any chance we will be able to able to expand the 10H to receive the CB bands?

Tony Politi wrote in #note-53:

@Mel Any chance we will be able to able to expand the 10H to receive the CB bands?

I don't know yet. Still working on figuring out the Freq Limit values. NO PROMISES.

Beta 2.6 (New Model #10692) is working perfectly for me. The only minor glitch I encountered was getting it to recognize presets for FM radio (76-108 MHz), but that's not a feature I use anyway, and it could have been my error. This build allowed me to easily reprogram the top button to a different function than the factory default FM radio selector. Great work Mel!

JD. Please explain exactly what issue you are having with FM presets. It should be working. I will double check but details of your issue will be helpful.

JD Hamster wrote in #note-64:

Beta 2.6 (New Model #10692) is working perfectly for me. The only minor glitch I encountered was getting it to recognize presets for FM radio (76-108 MHz), but that's not a feature I use anyway, and it could have been my error. This build allowed me to easily reprogram the top button to a different function than the factory default FM radio selector. Great work Mel!

I retested the driver and setting of FM presets works just fine. If you have more details on what you are experiencing, let me know.