On Mon, Apr 1, 2013 at 6:41 AM, Marco IZ3GME <iz3gme.marco@gmail.com> wrote:

It seams that the problem have been introduced in 9/2/2013 "[UV-5R] Add
support for editing the 15 PTT ID Codes" patch.
After analisys of the debug.log I'm pretty sure that he has a value
grather then 15 in any of the memobj.pttid[i].code elements.
This takes one of the "%x" to be 2 char instead of just one.

I asked Bill to email me his .img file and sure enough PTT-ID #1 had a 0x1f in the location where the first digit would normally be. I change it with a hex editor and email it back. I received a report that it is working now.

This is the only explanation I found to have
val = RadioSettingValueString(0, 5, _code, False)
fail because of a _code longer then 5.

That's it. If I change 5 to 6 and load the image the settings tab is available and the PTT-ID #1 is displayed as "1f0202" (6 characters long).

My two cents ..

73 de IZ3GME Marco

So my question now is what is the best way to trap this condition?

Plus while testing, I just discovered that the Baofeng software also allows *, #, A, B, C and D in addition to the 10 digits.

0 = 0x00

1 = 0x01

2 = 0x02

. . .

9 = 0x09

n/a = 0x0a

* = 0x0b

# = 0x0c

A = 0x0d

B = 0x0e

C = 0x0f

D = 0x10

I wouldn't mind adding that to but I've not thought about it long enough to figure out how to do that.

Jim