Feature #1863
[KG-UV6]Improve Support for the Powerwerx Wouxun KG-UV6X
| Status: | New | Start date: | 08/23/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Jim Unroe | % Done: | 100% |
|
| Category: | - | |||
| Target version: | 0.4.1 | |||
| Chirp Version: | daily | Model affected: | KG-UV6X |
Description
Currently CHIRP treats the KG-UV6D and KG-UV6X the being the same. They are not the same and CHIRP should be updated to support the differences.
PONMSG: This is only supported on the KG-UV6D. The same byte that contains the setting for the KG-UV6D is set to 0xFF in the KG-UV6X since it isn't used. This causes an out-of-range error when read into CHIRP since it doesn't match any of the values CHIRP expects to see for the KG-UV6D.
BANDWIDTH: This is a single setting in the KG-UV6D for each memory and each VFO. It controls the BANDWIDTH setting for both RX and TX. The KG-UV6X on the other hand, has a separate setting for RX BANDWIDTH and TX BANDWIDTH. So it is currently impossible to set the TX BANDWIDTH of the KG-UV6X.
Associated revisions
[KG-UV6]Improve Support for the Powerwerx Wouxun KG-UV6X
Add "iswidex" to structures to accomodate the KG-UV6X's TX Bandwidth
setting
Add "Mode TX" to the mem.extra settings to allow editing each
memory's TX Bandwidth
Add a 4th setting, "N/A(KG-UV6X)", to the options for "ponmsg" to
prevent out-of-range values