Bug #9349

ToneSql/ cToneFreq not importing into radio .img file.

Added by Niamh Holding 5 months ago. Updated 5 months ago.

Status:Feedback Start date:09/04/2021
Priority:Normal Due date:
Assignee:- % Done:


Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:(All models)


When I import a csv into a radio image the ToneeSql field is not imported.

I can import successfully into a new file which is set as .csv by CHIRP, but then I can't upload that to the radio

Leixen_VV898John_20210904.csv - csv file with ToneSql data. (4 kB) Niamh Holding, 09/04/2021 02:19 am


Updated by Jim Unroe 5 months ago

  • Status changed from New to Feedback

Hi Niamh,

CHIRP, as provided by your example CSV file, is working as expected and as designed.


When Tone Mode is set to Tone (as shown above), only the Tone column (rToneFreq in the CSV file) is used. Any value in the ToneSql field (cToneFreq in the CSV file) is ignored. If the Hide Unused Fields setting of CHIRP is enabled (the default for new CHIRP installations), the ToneSql field will be blank. The radio will use the CTCSS tone from the Tone column as the TX CTCSS tone. Carrier squelch will be used for RX.


If you want a value in the ToneSql column, then you must set the Tone Mode to TSQL (Tone in the CSV file) as shown above. You can populate the rToneFreq field in the CSV file with the default 88.5 or the same value as the cToneFreq field. It doesn't matter either way. The radio will use the CTCSS tone from the ToneSql column (cToneFreq in the CSV file) for both the TX and RX CTCSS tone. CHIRP will ignore the value in the Tone column (rToneFreq in the CSV file) and the Tone field will be blank if the Hide Unused Fields setting is enabled.

For more details about how the CHIRP columns are used and selective squelch columns affect one another, take a look at these reference guides.

CHIRP Programming Reference
Understanding CHIRP's columns


Also available in: Atom PDF