New Model #10880
openWouxun KG-Q336/332
0%
Description
Hello.
On the request of Mel I've made this request for the Q336 and Q332, as i suspect the 332 has the same memory mapping as the stock software is for the 332.
Mel's beta for the Q10H allows me to download, read, edit, and upload frequencies to the radio. However I can't access the settings because of a NoneType object error (see attached debug log)
I can't lend out my radio but I'm more than happy to be active in the development, uploading logs and whatever else I could provide to be of help.
Files
Updated by Kevin S about 1 year ago
Specifically "SCANMODE_LIST[_settings. IndexError: list index out of range*"
Kevin S wrote:
Mel's beta for the Q10H allows me to download, read, edit, and upload frequencies to the radio. However I can't access the settings because of a NoneType object error (see attached debug log)
Updated by Tony Fuller about 1 year ago
Hi Kevin,
If you attach the img file that CHIRP downloaded, others can take a look without the radio.
Thanks,
Tony
Updated by Kevin S about 1 year ago
Tony Fuller wrote in #note-2:
Hi Kevin,
If you attach the img file that CHIRP downloaded, others can take a look without the radio.
Thanks,
Tony
Noted, and attached
Updated by Mel Terechenok about 1 year ago
The image posted clearly shows many issues with using the Q10H driver on the 336/332 radio.
First - the Scan Group name has an invalid character in a scan name Åkeri- the Å is not a valid character in Chirp base ASCII character set being used by the driver. Change it to Akeri and it will be ok. I tried using Åkeri in the Top Message and Area Message on the Q10H and the radio does not display it correctly - either using Chinese Characters or displaying a default value instead.
But beyond that - I don't believe the 332 has the same memory map for settings as the Q10H.
I found 3 settings (stopped looking after that) that have values outside the expected ranges of the Q10H settings expected at the location (meaning they are likely values for different settings). Scanmode, PowerOnMessage and DTMF Sidetone (likely many more).
As I mentioned before - the driver will need to be updated with a memory map for the specific 336/332 radio for Chirp to ever work with it.
Unless/until someone determines / provides a map the 336/332 will not be usable with Chirp.