CHIRP

+1

I have tried to use the KG-UV9D Plus driver, which worked after I added
or.self._rev=="03"
in line 862 of kguv9dplus.py.

With this I could read out the memory, edit the channels and write everything back without any errors. However, after reading back the memory with the wouxun software some settings where wrong (DTMF control, tx power).
So I guess most mappings are the same, and some are wrong or missing.
I haven't used chirp before so I don't really know how to proceed and won't go any further.

+1
compared with the original software CHIRP is a lot more user friendly
what can I do to help with the development?

Looking at the programming software this seems like a clone of the KG-UV9D Plus, perhaps a cost cutting version with simpler screen? If files from the original programming software will help I will be happy to provide them as soon as my radio arrives.

The radio is a clone of the KG-UV9D with the added 8.33. Nothing more, nothing less. (The screen is the same, I was confused by the packaging).
Like Ra ul already said it should be a matter of changing some "mappings", in order to accommodate the new step. If anyone was to try, message me and I can provide files from CHIRP, factory software, or anything else you need.

I have used this program http://www.wouxun.com/resource/UV9K_SEN01.rar , but feel more comfortable using CHIRP. Please let me know if there's an update for this series. Thanks

The workaround mentioned on the first post works fine for copy pasting large amounts of memories from other radios, until proper support is implemented this is the way to go.

Hello!

Is it possible to c duplicate the KG-UV9D Plus driver, patch it and include it in the Chirp binary package as KG-UV9K so people can
use Chirp with that Radio?

Thank you ..

Andrew Hedge wrote:

Hello!

Is it possible to c duplicate the KG-UV9D Plus driver, patch it and include it in the Chirp binary package as KG-UV9K so people can
use Chirp with that Radio?

Thank you ..

I have patched the driver and it works at least for mass memory editing, but can't compile a standalone exe since the compile instructions for windows are outdated and/or non existent. Sadly for now the only way is to install python etc, and run it like this.
Let's hope someone finally makes a proper driver since it seems the radios are identical other than the 8.33 step.

Hello!
Sorry I overlooked your reply!

I downloaded the source but how do I run CHIRP w/o compiling?
Are you on Linux?

Hmmm ... who is in charge of development?

Did any progress get made on this? I just purchased one myself and the Wouxun software isn't as nice to use as Chirp. I am happy to help in any way I can.

I have been trying to get this to work with no success. I tried changing the driver file as suggested in the first comment but unfortunately the document https://chirp.danplanet.com/projects/chirp/wiki/DevelopersWin32Environment is out of date and I can't get all the required libraries installed. For example the website linked to retrieve PyLibXML2 hasn't been working for at least 24 hours now which suggests more than a temporary error, and PyWin32 now seems to be Python 3 only.

As a short term measure, and to allow those of us with the radio to do some testing, could the file kguv9dplus.py be changed as follows.

Line 862 (if no changes have been made) reads...

if self._rev == "02" or self._rev == "00":

Could this be changed to

if self._rev == "03" or self._rev == "02" or self._rev == "00":

Since that would add in the rev 3 that the first post suggests without breaking existing models. Since Chirp warns you that this driver is in development and may not work as expected you are already warning users up front.

This is the only workaround I have found in order to mass paste/edit memories in Chirp. Watch out for the 8.33k step though, this can complicate things since its not properly implemented in the existing driver. I usually do the edits in the modified Chirp then confirm everything in the factory software and re-write to the radio.

Hello,
I'm also very interested in this model!

Would it be possible to add the proposed trick on the daily build?

As Jay Smith, I don't manage to get a build environnement to try :(

Thanks

The latest Chirp-Next Build allows the UV9D_Plus driver to open all revisions of radios that identify as themselves as "KG-UV9D".

This should allow you to complete the Download from radio and view channel memories and settings as long as your radio revision uses the default UV9D Plus memory map and settings decoding.

If the settings tab blanks out, then your radio uses settings that are not consistent with the UV9D Plus and the debug.log would be needed to further debug your model.

https://chirp.danplanet.com/projects/chirp/repository/github/revisions/323d36ada75177834477ea93ee8ba430fbe10c6c/diff

Seems your driver updates are spot on. It can read and write from a KG-UV9K that has 8.33 channels on it, the settings menu works fine after reading, editing, writing to the radio and reading again. I guess the settings menu will need a bit more testing in case some setting bytes have been assigned to something else, but I doubt it. I think this should be included in the next release so further testing can be done by others.

I don't use handhelds much but I will use my KG-UV9K whenever I can in order to test this some more. Thank you so much for providing a solution within few minutes of being asked.

The step setting on Area A and Area B settings also works fine. Can be read and written to the radio without any problems.

DJ kourampies wrote in #note-23:

The step setting on Area A and Area B settings also works fine. Can be read and written to the radio without any problems.

DJ, Can you post an .img file from you 9k here so I can use it for new model driver submission...thanks

Mel Terechenok wrote in #note-25:

DJ kourampies wrote in #note-23:

The step setting on Area A and Area B settings also works fine. Can be read and written to the radio without any problems.

DJ, Can you post an .img file from you 9k here so I can use it for new model driver submission...thanks

Do you need something full and complicated or a few dozen memories of all types are enough?

I have lots of memories that are not for sharing and need to clean it up quite a bit before making it public.

Just something with a couple channels. Definitely nothing with data you don't want share. It could even be a factory reset image.