anytone778uv: Fix incorrect DTCS handling

This driver has been broken forever in how it handles DTCS tone mode.
It was always using the rx_dtcs field, which should only be honored
in a ->DTCS cross mode. The new GUI, being in hide-unused-fields mode
always made this clear, as it appeared to be snapping back to 023
always when the user selected a different value.

Note that the test is *also* broken, which I will fix at the end of
this series.

Fixes: #11506
This commit is contained in:
Dan Smith 2024-08-29 17:07:37 -07:00 committed by Dan Smith
parent f23c71fafb
commit fb87356ec8

View File

@ -1040,10 +1040,10 @@ class AnyTone778UVBase(chirp_common.CloneModeRadio,
elif mem.tmode == 'DTCS':
_mem.dtcs_encode_en = 1
_mem.dtcs_encode_code, _mem.dtcs_encode_code_highbit = \
dtcs_code_val_to_bits(mem.rx_dtcs)
dtcs_code_val_to_bits(mem.dtcs)
_mem.dtcs_decode_en = 1
_mem.dtcs_decode_code, _mem.dtcs_decode_code_highbit = \
dtcs_code_val_to_bits(mem.rx_dtcs)
dtcs_code_val_to_bits(mem.dtcs)
_mem.tone_squelch_en = 1
elif mem.tmode == 'Cross':
txmode, rxmode = mem.cross_mode.split('->')