CHIRP

There is no bug here. CHIRP is working correctly and as expected.

When Tone Mode is set to Tone, only the Tone field is used to designate the TX CTCSS tone. There is no RX CTCSS tone because carrier squelch is used for RX. The ToneSql and Cross Mode fields are not used and any values in them are ignored by CHIRP when Tone Mode is set to Tone.

It is easier see how this works if, instead of looking at the Memory Properties editor, you would look at the spreadsheet style memory editor with the the "Hide Unused Fields" setting enabled (this setting is enabled by default for new CHIRP installations). As you can see from the attached screen capture, the ToneSql and Cross Mode fields are blank since they are currently unused based on the Tone Mode selection. Their values (as seen in the Memory Properties editor) are currently being ignored and do not influence the setting in the radio.

You can confirm this by checking the display of the handheld radio's. When this repeater is selected and the PTT button is not pressed, there will be no CT showing the the radio's left status display area. That means the radio is using carrier squelch for receive. Now if you tap the [*] key to put the radio into reverse mode (or press the [PTT] button causing the radio to transmit) the left status display area will now show a CT which indicates that a CTCSS tone is being used for TX. This exactly matches how the repeater settings were imported from RepeaterBook.

For more information about how the Tone Mode columns work with one another you can review the CHIRP column guides linked to from the Miklor.com "CHIRP Guides, Examples & Spreadsheets":http://www.miklor.com/COM/UV_CHIRP.php#guides Section 6.1 and 6.2 (or go directly to the CHIRP guide in the wiki area by clicking "here":http://chirp.danplanet.com/projects/chirp)./wiki/MemoryEditorColumns).

Jim KC9HI

First, there is never a requirement to use a receive CTCSS tone. The use of a receive CTCSS tone is purely optional.

CHIRP is just reading the data provided by RepeaterBook. If RepeaterBook does not include the RX CTCSS tone, that is on RepeaterBook, not CHIRP.

If you want to use both a TX and RX CTCSS tone and RepeaterBook does not provide both, then yes, you will have to manually change it.

The correct way would be...

Tone Mode: TSQL
ToneSql: 100.0

Sure you could program...

Tone Mode: Cross
Tone: 100.0
ToneSql: 100.0
Cross Mode: Tone->Tone

But CHIRP will automatically switch it to the first way. Cross Mode is only used when the TX and RX tone frequencies are not the same.

There are many repeaters in the same county as the K7DAD repeater that use the 162.2 Hz CTCSS tone. You can change all of these at the same time by highlighting all memory rows requiring the same configuration and then access the Memory Properties editor to make the change. See attached screen capture.

Jim KC9HI

I appreciate your response Jim. The screenshots in the original issue post, show that the Repeaterbook Query shows 100.0 for both Tone and Tone SQL, but the mode stays as Tone.

When the Repeaterbook is imported to the Radio, the Tone SQL is ignored.

I have attached the Repeaterbook Screenshot that shows that repeaterbook does include the Downlink tone.

I understand that there is no specific requirement to use R-CTCS, but it makes my rig a whole lot less noisy when people aren't honoring the Band Plan in the area. Its a pain to use the import, only to then have to go and change all the R-CTCS tones so that I can focus on just repeater traffic.

The issue as i see it is that Repeaterbook does include both the Uplink and Downlink Tone. The Repeaterbook query in Chirp shows 100.0/100.0 but doesn't correctly choose TSQL or Cross. And hence when it gets imported to the radio, because TSQL or Cross aren't detected by Chirp due to the Repeaterbook information, they are ignored when the are imported to the Radio.

No more traffic on this ticket. Please let us know if we should keep this open.