Re: [chirp_users] chirp-daily-20160419-win32: Properties => Smart Tone Modes?
You never had an issue because you understood CHIRP ;-) I was able to change all my power settings to LOW, and, encouraged by that, I attempted to do some more block changes. But I didn't know about the Rx|Tx == 0 feature of the UV-5, and how CHIRP handled that, so I blithely changed a bunch of frequencies, only to find that CHIRP changed them back to 88.5. Why 88.5 instead of another freq is a question, but I suppose that it had to be something. Oh, wait, maybe not. If the real value is 0.0 for the CTCSS, why not make it that?
But I /am/ learning, and making notes. Were it not for the ready replies here, I'd still be thinking of taking a hammer to CHIRP.
~R~ NE1EE
On 2016-04-25 17:27:-0400, you wrote:
On Mon, Apr 25, 2016 at 2:17 PM, Rich Messeder rich.messeder@gmail.com wrote:
I just tried to use the properties dialog, and it reset all sorts of things I was not expecting. Sigh. Shoulda saved before I did that. Single edits for me, then?
~R~ NE1EE
I use the [Properties] dialog all the time. Especially when I want to change multiple multiple channels at the same time (for example when setting all power levels to low or TX inhibiting the FRS, GMRS, MURS and the Part 90 frequencies that I listen to). I have never had an issue.
Jim KC9HI
On Wed, Apr 27, 2016 at 7:44 AM, Rich Messeder rich.messeder@gmail.com wrote:
You never had an issue because you understood CHIRP ;-) I was able to change all my power settings to LOW, and, encouraged by that, I attempted to do some more block changes. But I didn't know about the Rx|Tx == 0 feature of the UV-5, and how CHIRP handled that, so I blithely changed a bunch of frequencies, only to find that CHIRP changed them back to 88.5. Why 88.5 instead of another freq is a question, but I suppose that it had to be something. Oh, wait, maybe not. If the real value is 0.0 for the CTCSS, why not make it that?
But I /am/ learning, and making notes. Were it not for the ready replies here, I'd still be thinking of taking a hammer to CHIRP.
~R~ NE1EE
CHIRP sets the columns back to the default, but it doesn't matter.
When Tone Mode = Tone. Only the value in the Tone column matters. The rest of the columns pertaining to selective squelch (ToneSql, DTCS Code, DTCS Rx Code, DTCS Pol, and Cross Mode) are ignored. Leave them at the default values. They are ignored and won't affect anything. That is why here is an option to "hide" unused fields.
The "CHIRP Reference and Guide" on miklor.com shows which columns are required by each Tone Mode.
http://www.miklor.com/COM/UV_CHIRP.php#guides
Jim KC9HI
participants (2)
-
Jim Unroe
-
Rich Messeder