[chirp_devel] FYI for Wouxun KG-UV6D 199 memory channel radio
FYI, for the maintainer of the wouxun driver. David Behar has done the work to map out the memory format as well as the .tw file format for the newer version of the Wouxun KG-UV6D radio.
This is a newer version with 199 memory channels and 2.5 khz spacing.
Note: the memory format and software between the earlier 128 memory channel HT's (KG-UV1,2,3) and the 199 memory channel is similar but incompatible. There have been reports of people running into problems (including possibly bricking radios) by using incompatible versions including .tw files from a different version of the radio.
The wouxun settings including the band limits seem to be in range of the writable memory area without much protection. It sounds like using the wrong version will unintentionally overwrite those settings with garbage (channel data). I've read that writing band limits outside the range the radio is capable of will cause the PLL to fail to lock and the microcontroller will then hang waiting.
Note: it may be worth mentioning on the chirp pages that the KG-UV(D)[123][PD] driver is not compatible with the kg-uv6d.
I don't know if the UV6D radio sends a different identification or has any reliable way of telling the difference. I don't have one. I'm just sharing what I've seen on other mailing lists as an fyi.
Hope this helps, --Rob
-------- Original Message -------- Subject: Re: [KG-UV_Commander] Re: KG-UV Commander for KG-UV6D? Date: Sat, 4 Feb 2012 01:45:33 -0800 From: David A. Behar To: KG-UV_Commander@yahoogroups.com
I've passed on to Jim a draft memory map of the radio's memory space and of the KG-UV6D TW file format.
I don't know if the UV6D radio sends a different identification or has any reliable way of telling the difference. I don't have one. I'm just sharing what I've seen on other mailing lists as an fyi.
Hmm, yeah, that's not very cool. My experience with other chinese knock-off radios has been that they do not do a good job (or any job) of identifying the different models and sub-models to the software. This likely means that there's not much we can do to help the user avoid this trouble, but if you hear of anyone coming up with a reliable way to identify the devices, let me know.
On 2/5/2012 12:16 PM, Dan Smith wrote:
This likely means that there's not much we can do to help the user avoid this trouble, but if you hear of anyone coming up with a reliable way to identify the devices, let me know.
I haven't looked at it. My wild guess from what I've heard 2nd hand:
if I were to implement something, I would probably start by first attempting to read the band limits from the radio and then sanity check them. The band limits can be changed by the user with some of the available software like Commander, and I think the open source owx.
However there are some reasonableness checks (upper limits higher than lower limits, TX range less than or equal to RX range, UHF range higher than VHF range...
participants (2)
-
Dan Smith
-
Robert Terzi