I'm not surprised.
Ruzhuo Li wrote:
When Tone set to Cross and Cross mode set to "->Tone", the export csv file lost Cross mode information.
This programs the channel to have an RX only CTCSS tone and no TX CTCSS tone. This would require the radio that you are communicating with to TX the matching CTCSS tone but have no RX CTCSS tone because you aren't transmitting one (just the reverse of your radio). Not a very practical way to use CTCSS tones.
When exporting to a CSV file, rToneFreq (the TX CTCSS tone) gets set to the default 88.5 Hz even though it isn't getting used and cToneFreq (the RX CTCSS tone) gets to 100.0 Hz.
Then, after importing from the csv file, the Tone has a value and Cross mode becomes "Tone->Tone".
Then when the CSV file is imported, CHIRP interprets the "Cross" in the "Tone" column as meaning the TX-CTCSS tone is 88.5 Hz and the RX CTCSS tone is 100.0 Hz which would be Tone Mode = Cross and Cross Mode = Tone->Tone.
Please see the attachment.
Basically for CTCSS tones to work with a CSV file you must limit your use one of the following...
Tone Mode = Tone (TX CTCSS tone only)
Tone Mode = TSQL (TX CTCSS and RX CTCSS tone are the same)
Tone Mode = Cross | Cross Mode = Tone->Tone (TX CTCSS tone and RX CTCSS tone are different)
I don't think any of the other Cross Mode choices will work.
Jim KC9HI
