CHIRP

Using a non standard CTCSS value (e.g. 75.0) in radio will cause an error in CHIRP (tested with Baofeng UV-5R but the error seems generic for any radio capable of non-standard CTCSS tones).

When CHIRP reads a non-standard CTCSS tone from the radio (e.g. 75.0) the channel information will be grayed out and channel values will either be set to default (e.g. frequency at 0.000000), be left blank or display "ERROR" (i.e. Name) instead of showing the actual values stored in the radio. Note that this happens for both encode and decode non-standard CTCSS values.

Suggestions:

1. Show actual CTCSS values stored read from the radio (i.e. Do not generate an exception for non-standard CTCSS frequencies on read)
2. Offer an option to toggle the CTCSS pull down list from current standard PL tones to just sequential values (i.e. 60.0, 60.1, 60.2 .... 259.8, 259.9)

Workaround: Use the OEM Software to set non-standard CTCSS tone values.

Error in debug log:
-- Exception: --
Traceback (most recent call last):
File "chirpui\common.pyo", line 97, in execute
File "chirp\uv5r.pyo", line 340, in get_memory
File "chirp\chirp_common.pyo", line 313, in __setattr_

ValueError: `75.0' is not in valid list: [67.0, 69.3, 71.9, 74.4, 77.0, 79.7, 82.5, 85.4, 88.5, 91.5, 94.8, 97.4, 100.0, 103.5, 107.2, 110.9, 114.8, 118.8, 123.0, 127.3, 131.8, 136.5, 141.3, 146.2, 151.4, 156.7, 159.8, 162.2, 165.5, 167.9, 171.3, 173.8, 177.3, 179.9, 183.5, 186.2, 189.9, 192.8, 196.6, 199.5, 203.5, 206.5, 210.7, 218.1, 225.7, 229.1, 233.6, 241.8, 250.3, 254.1]¶