[chirp_devel] Wouxun OSS software with mods detail
On 4/6/2011 12:19 PM, Dan Smith wrote:
... for the VX7 radio (which is, I think, the only one for which we know about any mods).
Don't know if this is a help, if you want another radio to model for mods, there is another piece of open source software, owx, that is available for the Wouxun KG-UV2D & KG-UVD1P which looks like it has some details for frequency range modifications.
http://owx.chmurka.net/?p=docs
--Rob
6.2. Frequency ranges
There are eight values below the channel table. They correspond to the RX and TX ranges on both bands. By editing them, you can unlock your radio (change it's transmit and receive range), but it's easy to kill your radio by setting invalid values. If the ranges are invalid, the rig will refuse to turn on, probably due to busy-waiting for the PLL loop to lock. YOU WILL NOT BE ABLE TO REPROGRAM MEMORY USING ORDINARY CABLE. We've killed one radio this way and in order to bring it back to life I had to open it, disable the MCU (I just disabled it's clock), connect to the memory I2C bus and manually reprogram it. If you lack appropriate equipment or skills you definitely don't want to do this.
OWX performs some basic checks on the ranges when importing and warns you if any value seems to be bogus, but it doesn't check the ranges (if you mess with their order). Also, bugs in the importing routine are possible. If you see any warning during importing, consider contacting me before putting the resulting file to the radio, as it is easy to brick the radio and not so easy to bring it back to life.
If instead of frequencies you see some hexadecimal values (0xABCD or so) then the decoder (used when exporting) found unexpected pattern and refused to decode the value. Please contact me and provide these raw values. It should be safe to program them back to the radio, but don't change them (they're encoded).
On the Yahoo wouxun group there is an excel spreadsheet with the memory map.
http://f1.grp.yahoofs.com/v1/0CWeTQg_gQfM9NVX7nkvidV1nrPxIqtniGiv_Ofl2WwX26O...
It says the band limit data is at offset 0x0970 for 16 bytes.
band_limit_table_type 0x00 0x02 Band_1_receive_low_limit frequency_limit band_limit_table_type 0x02 0x02 Band_1_receive_high_limit frequency_limit band_limit_table_type 0x04 0x02 Band_2_receive_low_limit frequency_limit band_limit_table_type 0x06 0x02 Band_2_receive_high_limit frequency_limit band_limit_table_type 0x08 0x02 Band_1_transmit_low_limit frequency_limit band_limit_table_type 0x0A 0x02 Band_1_transmit_high_limit frequency_limit band_limit_table_type 0x0C 0x02 Band_2_transmit_low_limit frequency_limit band_limit_table_type 0x0E 0x02 Band_2_transmit_high_limit frequency_limit
The frequency limit values don't appear to be documented there.
participants (1)
-
Robert Terzi