Bug #5771
closedImport of TSQL tones missing outgoing tone
0%
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.
Updated by Dan Smith almost 6 years ago
- Status changed from New to Feedback
the rtone and ctone fields are not "input" and "output" values. In TSQL mode, ctone is used for both input and output, while in Tone mode, rtone is used This mirrors how many of the radios behave that chirp was first designed for (i.e. Icom and Kenwood), as well as how most amateurs program their radios. If you want to control the RX and TX tones separately, you want "Cross" tone mode, and "Tone->Tone" (which is the default). Then, rtone is the transmit tone and ctone is the receive/squelch tone.
Updated by Christopher Simpson almost 6 years ago
Thanks, I misunderstood how this was intended to be used and now know how to adjust my CSV accordingly.
Updated by Dan Smith almost 6 years ago
- Status changed from Feedback to Rejected
No problem, thanks :)