CHIRP

Is there any progress on this.
the radio is advertised as dual band and 5W yet the rating sticker behind the battery shows it as 8w UHF

either way im willing to lend any dev a radio if they can do something with it as its just a paperweight to me at the moment

I have managed to get it programmed up now with a speciality lead and some somewhat expensive software..
Still prepared to loan it out to whoever wants to borrow it including the software and lead if they can reverse engineer from that

Daniel Smith wrote:

I have managed to get it programmed up now with a speciality lead and some somewhat expensive software..
Still prepared to loan it out to whoever wants to borrow it including the software and lead if they can reverse engineer from that

Another update i have found the original baofeng software that also works with the nomal programing cable, its abosloutely awful however, starts up in chinesse and takes a bit to find which menu to switch to english when they are all listed as ???

I actually have a UV-8D here (someone donated it to me awhile back). I have it all programmed except for one important thing. I can't figure out how the radio knows when a channel is programmed. I can send channels to the radio with CHIRP but they do not show up in the radio. It apparently doesn't work the same as nearly all other Baofeng radios. Looking at the serial captures and comparing images for a channel that is programmed or not programmed, there aren't any "flags" to indicate if a channel is programmed or not.

The programming software does something that I haven't seen before. If a channel is programmed, it sends the data to the radio as expected, but if the channel isn't programmed, if I remember correctly, it sends the cmd, address and size but no data. It just skips on to the next channel and writes data if programmed and no date if not programmed. So I don't know if the firmware figures out from that if the channels is programmed or not. I just don't know how to have CHIRP suppress sending the data on empty channels to simulate what the OEM software is doing.

I think I could find (or create) serial capture logs to attach to this issue if that would help.

Jim