Bug #2377: Wouxun UV8D V1.01 cannot see "Settings" tab in Chirp - CHIRP

Actions

Copy link

Bug #2377

closed

Wouxun UV8D V1.01 cannot see "Settings" tab in Chirp

Added by Stan White over 9 years ago. Updated over 8 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

03/01/2015

Due date:

% Done:

100%

Estimated time:

Chirp Version:

daily

Model affected:

Wouxun UV-8D, firmware V1.01

Platform:

Windows

Debug Log:

I read the instructions above:

Description

Greetings,

      The issue is as per title. Jim Unroe has helped considerably, and I have reproduced his message below. I used a daily build from February 2nd, and as Jim stated, it then worked.

Actually, I have never had the "settings" tab working since I got the radio May 2014, and it did not work at the time on February 2nd. But since Jim did something to the kguv8d.py file and I loaded that as he suggested, it does work.

Thanks in advance for your time and efforts, it is appreciated.

Regards and 73,

Stan, G4EGH

Stan,

There are two problems.

Problem 1:

The oem information in your radio has invalid (to CHIRP) characters. I have commented out the section of code that fails with those characters.

Problem 2:

Apparently some new CHIRP UI code has broken CHIRP for your radio. If I use the latest daily build, the settings menus are broken. If I use an early February daily build, the menus are there.

Save the attached file to the same place that you keep your .img files.
Install a CHIRP daily build from early February Load CHIRP Click Help in the menu bar and enable "Enable Developer Functions"
Click File -> Load Module and load the files that was saved earlier.

Now you will be able to see the settings.

You will have to open an issue on the CHIRP website to see if the developer working on the KG-UV8D can fix this for you.

Jim KC9HI

Files

Download all files

kguv8d.py (31.7 KB) kguv8d.py	As supplied by Jim Unroe	Stan White, 03/01/2015 02:08 PM
debug.log (10.2 KB) debug.log	Debug log from February 27th	Stan White, 03/01/2015 02:08 PM
G4EGHUV8Dimage.img (32 KB) G4EGHUV8Dimage.img	Image from my radio	Stan White, 03/01/2015 02:08 PM

Actions

Copy link

Updated by Kosta A. over 9 years ago

The issue stems from the fact that the memory address where Stan's version of the radio stores the OEM data appears to contain some characters outside the supported ascii charset. This may be a sign that the actual memory for Stan's older radio version, UV8DV1.01, may have changed compared to the newer sample version, UV8DV1.05, checked into the tree.

A patch is being submitted which addresses one issue where the UV8D driver was not decoding strings from memory, but rather was treating them as raw memory - this will at least prevent the app from attempting to display the raw memory as a string (which it can not do in cases where the string contains null characters, etc..)

Somebody with access to these radios may wish to compare the memory between the various versions and attempt to verify the correct structure. The patch will at the least prevent the exception from being thrown, and thus allow for the ui to construct itself properly.

Stan's Version: UV8DV1.05

There does not appear to be an issue with the CHIRP UI, and it did not appear to work in previous versions either as the exception thrown would have prevented from any settings being constructed by the settings editor.

Actions

Copy link

Updated by Kosta A. over 9 years ago

Status changed from New to In Progress
% Done changed from 0 to 30

Actions

Copy link

Updated by Stan White over 9 years ago

Just installed the daily build for 6th March, and the settings tab DOES appear :-) I did not have to enable developer functions, it worked first time.

Many, many thanks,

Regards,

Stan.

Actions

Copy link