[chirp_users] Keeping Repeater setting

Jim Unroe rock.unroe at gmail.com
Tue Jul 24 13:07:54 PDT 2018


On Tue, Jul 24, 2018 at 3:21 PM, AC1CX via chirp_users
<chirp_users at intrepid.danplanet.com> wrote:
> The problem I have, and it was apparent in earlier versions but seems to be a serious issue with the most recent early July version.    while programming when you move to the next line the settings for the PL tones on the previous line you just used change, whether or not you hit the save button; The most common setting reverting to is a PL tone of 88.5.    Also does not want to keep settings when repeater use a stone instead of TSQL (A one-sided tone repeater).   I am having great difficulty programming a B Tech hand held in 220.

When changing a cell in Windows, you must press enter or click into
another cell to make the change permanent. If you cursor to another
cell, the change will be lost the next time CHIRP is refreshed
(download, upload, save file, load file, click [Refresh], etc.). This
it not a necessary step when CHIRP is use with the Linux or MacOS X
operating systems.

Cells that are unused retain the default values for that column. For
CTCSS it is 88.5. For DTCS it is 023.

Example 1: If Tone mode is set to Tone then the field in the Tone
column holds the value of the TX CTCSS tone. The field in the ToneSql
column is unused so it will retain the default value of 88.5.

Example 2: If Tone mode is set to TSQL then the field in the ToneSql
column holds the value of the TX and RX CTCSS tone. The field in the
Tone column is unused so it will retain the default value of 88.5.

If you don't like to see the default values in the "unused" cells,
then click "View" in the menu bar and enable "Hide Unused Fields"
(which is the default for new CHIRP installations).

The miklor.com website has links to CHIRP guides that explain how the
columns work. http://www.miklor.com/COM/UV_CHIRP.php#guides

Jim KC9HI



More information about the chirp_users mailing list