Actions
Bug #5771
closedImport of TSQL tones missing outgoing tone
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/05/2018
Due date:
% Done:
0%
Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
MacOS
I read the instructions above:
Description
Chirp is not properly setting the outgoing tone when importing a CSV of channels when the squelch mode is TSQL. For example if a channel has a 123 input and output tone and the channel tone mode in the CSV is set to TSQL, only the input tone gets set, the output tone defaults to 88.5 (88.5, 123 as seen with the default column order). When the tone is set to Tone, the opposite is true, the input tone does not import from the CSV and defaults to 88.5 (123, 88.5). Running the 2018-04-12 daily build.
Actions