CHIRP

Hi Chris,

CHIRP is working as intended. The problem is that there is a misunderstanding of how CHIRP handles the Tone Mode selections. This is then causing some mistakes to be made when configuring them.

1. The Hide Unused Fields selection has been disabled (it is enabled by default in new CHIRP installations). When enabled, CHIRP "hides" (blanks out) all of the fields that are currently unused and are being ignored by CHIRP based on the current Tone Mode (and Cross Mode when applicable) selections.

2. When Tone Mode is set to TSQL, the value selected in the ToneSql field is used for both the TX CTCSS tone and RX CTCSS tone. The value in the Tone field is unused and ignored by CHIRP.

3. When either the Tone, ToneSql, DTCS Code or DTCS Rx Code fields is currently not being used by CHIRP (based on the current Tone Mode selection), the unused field is always populated with a default value (88.5 for CTCSS, 023 for DTCS). When you change the value of an unused field, CHIRP will change it back to the default value. If the Hide Unused Fields setting would have been enabled (the default for new CHIRP installations), all of these currently unused/ignored fields would be blank so you wouldn't "see" the hidden (and ignored) values "underneath".

4. Setting Tone Mode to Cross is only used when the TX and RX selective squelch values are different. If you set Tone Mode = Cross and Cross Mode = Tone->Tone, CHIRP expects the values selected in the Tone and ToneSql fields to be different. When they aren't, CHIRP switches Tone Mode = TSQL and uses the value selected in the ToneSql field for both TX and RX.

I would recommended that you enable the Hide Unused Fields setting (in the View drop down menu) as it was when you installed CHIRP. It will help you to understand which fields are used (and which fields are ignored) for each of the various Tone Mode (and Cross Mode when applicable) settings. This way when you make a Tone Mode selection, you will know to only select values in the fields that are not blank. You will also know that any fields that are blank are currently unused and any value entered into them will be ignored by CHIRP. Once you gain an understanding for which fields are used and when, you can disable the Hide Unused Fields selection again, if you wish.

I have included screen captures of your three CHIRP Radio Images (.img) files with Hide Unused Fields setting enabled.

Also you may wish to review the "column guides":https://www.miklor.com/COM/UV_CHIRP.php#guides that are linked to at the "Miklor":https://www.miklor.com website.

Jim KC9HI

I Turned on 'Hide Unused Fields'. I also have 'Smart Tone Fields' enabled. Documentation doesn't seem to describe what 'Smart Tone Fields' does at:
https://chirp.danplanet.com/projects/chirp/wiki/MemoryEditorColumns

If I change the 'Tone Mode' from "Tone" to "TSQL" on the first two channels, CHIRP changes the tone from 162.2 (and 156.7) to 88.5. I did not expect CHIRP to do that either.

Thank you,
Chris Shaker, KJ7BLE

Jim:

With your advice, I was able to successfully edit the radio setup. Attached the results, if you want to see it.

Changing "Tone Mode" from 'Tone' to 'Cross' saved the Transmit tone for me, as I had hoped.

Thank you,
Chris Shaker, KJ7BLE

It turns out that our HiDarg repeaters do not transmit a tone on their transmissions, so I can't use TSQL. Had to change all HiDarg repeaters back to 'Tone'. That reset all of their tones to 88.5. It would be nice to be able to switch between Tone and TSQL without having to reset the TX tone each time.

Thank you!
Chris Shaker, KJ7BLE