There seem to be several settings for the BaoFeng F8+ radio that are of not particular consequence. One that has been confusing me is the “Tone Mode” Doesn’t seem to work on “Tone.” Should I be doing “TSQL” instead? or what? Is there somewhere I can get an explanation of the various settings needed to program the radio. The template is quite different from the sample I have from a friend with another model. Any ideas?
Thanks, Whit k3wb
Someone else will hopefully correct me if I'm wrong, (and I didn't look this up) but I believe that in this usage, "Tone" applies when transmitting only. TSQL, or Tone Squelch applies to both transmitting & receiving.
"Tone" is more common. If you use TSQL when you should have used Tone, others will be able to hear you, but you will only be able to hear them if they also use the same tone. To complicate things slightly, many repeaters require a tone to activate them, but many repeaters strip out the tone as the re-transmit. It is often a good idea to start with "tone" and only use TSQL if needed.
Best, Dave Nathanson KG6ZJO
On Jul 21, 2014, at 4:14 PM, "Dr. Whit Woodard" towhit@me.com wrote:
There seem to be several settings for the BaoFeng F8+ radio that are of not particular consequence. One that has been confusing me is the “Tone Mode” Doesn’t seem to work on “Tone.” Should I be doing “TSQL” instead? or what? Is there somewhere I can get an explanation of the various settings needed to program the radio. The template is quite different from the sample I have from a friend with another model. Any ideas?
Thanks, Whit k3wb _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Yes, TSQL sets the CTCSS or DCS tone on both TX and RX. (Not Recommended). Tone sets CTCSS or DCS on TX only. This explains in a bit more detail. http://www.miklor.com/COM/UV_CTCSS.php I hope this helps...
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dave Nathanson Sent: Monday, July 21, 2014 7:22 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Someone else will hopefully correct me if I'm wrong, (and I didn't look this up) but I believe that in this usage, "Tone" applies when transmitting only. TSQL, or Tone Squelch applies to both transmitting & receiving.
"Tone" is more common. If you use TSQL when you should have used Tone, others will be able to hear you, but you will only be able to hear them if they also use the same tone. To complicate things slightly, many repeaters require a tone to activate them, but many repeaters strip out the tone as the re-transmit. It is often a good idea to start with "tone" and only use TSQL if needed.
Best, Dave Nathanson KG6ZJO
Curious why you say that using tone squelch on both TX and RX is not recommended???
THX. Forrest
On Jul 21, 2014, at 6:51 PM, John LaMartina JohnLa@usa.net wrote:
Yes, TSQL sets the CTCSS or DCS tone on both TX and RX. (Not Recommended). Tone sets CTCSS or DCS on TX only. This explains in a bit more detail. http://www.miklor.com/COM/UV_CTCSS.php I hope this helps...
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dave Nathanson Sent: Monday, July 21, 2014 7:22 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Someone else will hopefully correct me if I'm wrong, (and I didn't look this up) but I believe that in this usage, "Tone" applies when transmitting only. TSQL, or Tone Squelch applies to both transmitting & receiving.
"Tone" is more common. If you use TSQL when you should have used Tone, others will be able to hear you, but you will only be able to hear them if they also use the same tone. To complicate things slightly, many repeaters require a tone to activate them, but many repeaters strip out the tone as the re-transmit. It is often a good idea to start with "tone" and only use TSQL if needed.
Best, Dave Nathanson KG6ZJO
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Hi Forrest et al,
The TX tone (CTCSS DCL and other names) may be required for the ham repeaters that use it. Modern radios' menus may set the tone independently for each channel or for the entire rig. This tells the repeater that "I really want to talk thru you" and I'm not some skip-signal coming from a different part of the country.
Historically (a hundred years ago?) commercial repeaters had several to many business users on them, as they were expensive and each business that used, ie. paid for the repeater service, had a different tone to open only that businesses own radios: a taxi had one tone, the road-repair company another tone, and the delivery company another tone and so on. They had to share the resource (the repeater) and not interfere with each other any more than necessary. CTCSS is the modern technical name of that tone process that used to be called PL - Private Line (Motorola), CG - Channel Guard, General Electric, and privacy codes for various FRS radios, plus other names.
It is the tone ENGAGED on the RECEIVER end that can be problematic: the exact tone MUST be present on the transmitted signal for the receiver squelch (TSQL) to open so you can hear the other station on that frequency; which may or may not be what you want.
As an example, I setup a simplex ham voice channel for myself and XYL to use as a 'Private Line' (Motorola trademark) only for us: car-house, car-car etc. This is fine for us, and I have TSQL set on both radios for this channel. On this 'unused' simplex channel she can only hear me and I can only hear her. If someone else hears us, which they could, and then tries to answer me, I would not hear them unless they figured out and then transmitted our 'PL' tone.
As an aside, this feature, as implemented on the FRS private channel radios, means that you can only hear people transmitting your private code on your channel; people with no (RX) tone set can hear you too, so not really very private, but helps reduce chatter from other users when listening on a shared resource/channel. The implication is that, if you use your FRS channel 1, by convention, as an emergency receiver, make sure the privacy codes are turned off, so you will be able to hear everyone on channel 1, even if they have a privacy tone enabled.
other comments?
73 de Bill WB2SXY
--
On 7/22/2014 12:26 PM, Forrest wrote:
Curious why you say that using tone squelch on both TX and RX is not recommended???
THX. Forrest
On Jul 21, 2014, at 6:51 PM, John LaMartinaJohnLa@usa.net wrote:
Yes, TSQL sets the CTCSS or DCS tone on both TX and RX. (Not Recommended). Tone sets CTCSS or DCS on TX only. This explains in a bit more detail. http://www.miklor.com/COM/UV_CTCSS.php I hope this helps...
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dave Nathanson Sent: Monday, July 21, 2014 7:22 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Someone else will hopefully correct me if I'm wrong, (and I didn't look this up) but I believe that in this usage, "Tone" applies when transmitting only. TSQL, or Tone Squelch applies to both transmitting& receiving.
"Tone" is more common. If you use TSQL when you should have used Tone, others will be able to hear you, but you will only be able to hear them if they also use the same tone. To complicate things slightly, many repeaters require a tone to activate them, but many repeaters strip out the tone as the re-transmit. It is often a good idea to start with "tone" and only use TSQL if needed.
Best, Dave Nathanson KG6ZJO
Bill, Thanks, that is very helpful. The question that comes to my mind is why then does chirp require us to put some value in the ToneSql column on every memory channel? I have just put in the lowest tone, because the software does not allow me to leave it blank. It would be very helpful if we had the option of leaving unnecessary columns blank. We can only do that with a couple of the entries. I would just amend the template to eliminate those columns, but I do not know which are necessary and which are not. I hope in time I will gain a better understanding of the template which apparently is restricted by both the hardware and the chirp software. Your arrangement for communication just with your family is a great idea. I would like to do something very similar. Do you employ that on a repeater so that you can obtain better coverage? or must you just set it up on simplex?
73 Whit k3wb
On Jul 22, 2014, at 10:29 AM, Bill Kasper williamkasper@frontiernet.net wrote:
Hi Forrest et al,
The TX tone (CTCSS DCL and other names) may be required for the ham repeaters that use it. Modern radios' menus may set the tone independently for each channel or for the entire rig. This tells the repeater that "I really want to talk thru you" and I'm not some skip-signal coming from a different part of the country.
Historically (a hundred years ago?) commercial repeaters had several to many business users on them, as they were expensive and each business that used, ie. paid for the repeater service, had a different tone to open only that businesses own radios: a taxi had one tone, the road-repair company another tone, and the delivery company another tone and so on. They had to share the resource (the repeater) and not interfere with each other any more than necessary. CTCSS is the modern technical name of that tone process that used to be called PL - Private Line (Motorola), CG - Channel Guard, General Electric, and privacy codes for various FRS radios, plus other names.
It is the tone ENGAGED on the RECEIVER end that can be problematic: the exact tone MUST be present on the transmitted signal for the receiver squelch (TSQL) to open so you can hear the other station on that frequency; which may or may not be what you want.
As an example, I setup a simplex ham voice channel for myself and XYL to use as a 'Private Line' (Motorola trademark) only for us: car-house, car-car etc. This is fine for us, and I have TSQL set on both radios for this channel. On this 'unused' simplex channel she can only hear me and I can only hear her. If someone else hears us, which they could, and then tries to answer me, I would not hear them unless they figured out and then transmitted our 'PL' tone.
As an aside, this feature, as implemented on the FRS private channel radios, means that you can only hear people transmitting your private code on your channel; people with no (RX) tone set can hear you too, so not really very private, but helps reduce chatter from other users when listening on a shared resource/channel. The implication is that, if you use your FRS channel 1, by convention, as an emergency receiver, make sure the privacy codes are turned off, so you will be able to hear everyone on channel 1, even if they have a privacy tone enabled.
other comments?
73 de Bill WB2SXY
--
On 7/22/2014 12:26 PM, Forrest wrote:
Curious why you say that using tone squelch on both TX and RX is not recommended???
THX. Forrest
On Jul 21, 2014, at 6:51 PM, John LaMartinaJohnLa@usa.net wrote:
Yes, TSQL sets the CTCSS or DCS tone on both TX and RX. (Not Recommended). Tone sets CTCSS or DCS on TX only. This explains in a bit more detail. http://www.miklor.com/COM/UV_CTCSS.php I hope this helps...
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dave Nathanson Sent: Monday, July 21, 2014 7:22 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Someone else will hopefully correct me if I'm wrong, (and I didn't look this up) but I believe that in this usage, "Tone" applies when transmitting only. TSQL, or Tone Squelch applies to both transmitting& receiving.
"Tone" is more common. If you use TSQL when you should have used Tone, others will be able to hear you, but you will only be able to hear them if they also use the same tone. To complicate things slightly, many repeaters require a tone to activate them, but many repeaters strip out the tone as the re-transmit. It is often a good idea to start with "tone" and only use TSQL if needed.
Best, Dave Nathanson KG6ZJO
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Whit, This is explained in the Guide mentioned previously under Tone Mode. http://kc9hi.dyndns.org/uv5r/programming/CHIRP%20Guide.pdf A description of each field and its options can be found there.
An entry in the ToneSql field is not required. If the Tone Mode selection is (none), the Tone and ToneSql fields are ignored. The 88.5 is a filler default.
I hope this helps . . .
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dr. Whit Woodard Sent: Tuesday, July 22, 2014 1:48 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Tone Settings TX, RX (TSQL & DCL) discussion
Bill, Thanks, that is very helpful. The question that comes to my mind is why then does chirp require us to put some value in the ToneSql column on every memory channel? I have just put in the lowest tone, because the software does not allow me to leave it blank. It would be very helpful if we had the option of leaving unnecessary columns blank. We can only do that with a couple of the entries. I would just amend the template to eliminate those columns, but I do not know which are necessary and which are not. I hope in time I will gain a better understanding of the template which apparently is restricted by both the hardware and the chirp software. Your arrangement for communication just with your family is a great idea. I would like to do something very similar. Do you employ that on a repeater so that you can obtain better coverage? or must you just set it up on simplex?
73 Whit k3wb
On Jul 22, 2014, at 10:29 AM, Bill Kasper williamkasper@frontiernet.net wrote:
Hi Forrest et al,
The TX tone (CTCSS DCL and other names) may be required for the ham repeaters that use it. Modern radios' menus may set the tone independently for each channel or for the entire rig. This tells the repeater that "I really want to talk thru you" and I'm not some skip-signal coming from a different part of the country.
Historically (a hundred years ago?) commercial repeaters had several to many business users on them, as they were expensive and each business that used, ie. paid for the repeater service, had a different tone to open only that businesses own radios: a taxi had one tone, the road-repair company another tone, and the delivery company another tone and so on. They had to share the resource (the repeater) and not interfere with each other any more than necessary. CTCSS is the modern technical name of that tone process that used to be called PL - Private Line (Motorola), CG - Channel Guard, General Electric, and privacy codes for various FRS radios, plus other names.
It is the tone ENGAGED on the RECEIVER end that can be problematic: the exact tone MUST be present on the transmitted signal for the receiver squelch (TSQL) to open so you can hear the other station on that frequency; which may or may not be what you want.
As an example, I setup a simplex ham voice channel for myself and XYL to use as a 'Private Line' (Motorola trademark) only for us: car-house, car-car etc. This is fine for us, and I have TSQL set on both radios for this channel. On this 'unused' simplex channel she can only hear me and I can only hear her. If someone else hears us, which they could, and then tries to answer me, I would not hear them unless they figured out and then transmitted our 'PL' tone.
As an aside, this feature, as implemented on the FRS private channel radios, means that you can only hear people transmitting your private code on your channel; people with no (RX) tone set can hear you too, so not really very private, but helps reduce chatter from other users when listening on a shared resource/channel. The implication is that, if you use your FRS channel 1, by convention, as an emergency receiver, make sure the privacy codes are turned off, so you will be able to hear everyone on channel 1, even if they have a privacy tone enabled.
other comments?
73 de Bill WB2SXY
--
On 7/22/2014 12:26 PM, Forrest wrote:
Curious why you say that using tone squelch on both TX and RX is not recommended???
THX. Forrest
On Jul 21, 2014, at 6:51 PM, John LaMartinaJohnLa@usa.net wrote:
Yes, TSQL sets the CTCSS or DCS tone on both TX and RX. (Not Recommended). Tone sets CTCSS or DCS on TX only. This explains in a bit more detail. http://www.miklor.com/COM/UV_CTCSS.php I hope this helps...
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dave Nathanson Sent: Monday, July 21, 2014 7:22 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Someone else will hopefully correct me if I'm wrong, (and I didn't look this up) but I believe that in this usage, "Tone" applies when transmitting only. TSQL, or Tone Squelch applies to both transmitting& receiving.
"Tone" is more common. If you use TSQL when you should have used Tone, others will be able to hear you, but you will only be able to hear them if they also use the same tone. To complicate things slightly, many repeaters require a tone to activate them, but many repeaters strip out the tone as the re-transmit. It is often a good idea to start with "tone" and only use TSQL if needed.
Best, Dave Nathanson KG6ZJO
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4716 / Virus Database: 3986/7900 - Release Date: 07/22/14
Thanks, Jim. I select the “Tone” option in the Tone Mode column; the Repeater PL in the Tone column; “88.5” in the ToneSql column; “023” in both the DTCS Code and DTCS Rx Code columns; and finally “Tone->Tone” in the Cross Mode column. All but the Tone column do not allow me a blank or “none” option. Does that sound right to you?
Whit k3wb On Jul 22, 2014, at 1:47 PM, John LaMartina JohnLa@usa.net wrote:
Whit, This is explained in the Guide mentioned previously under Tone Mode. http://kc9hi.dyndns.org/uv5r/programming/CHIRP%20Guide.pdf A description of each field and its options can be found there.
An entry in the ToneSql field is not required. If the Tone Mode selection is (none), the Tone and ToneSql fields are ignored. The 88.5 is a filler default.
I hope this helps . . .
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dr. Whit Woodard Sent: Tuesday, July 22, 2014 1:48 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Tone Settings TX, RX (TSQL & DCL) discussion
Bill, Thanks, that is very helpful. The question that comes to my mind is why then does chirp require us to put some value in the ToneSql column on every memory channel? I have just put in the lowest tone, because the software does not allow me to leave it blank. It would be very helpful if we had the option of leaving unnecessary columns blank. We can only do that with a couple of the entries. I would just amend the template to eliminate those columns, but I do not know which are necessary and which are not. I hope in time I will gain a better understanding of the template which apparently is restricted by both the hardware and the chirp software. Your arrangement for communication just with your family is a great idea. I would like to do something very similar. Do you employ that on a repeater so that you can obtain better coverage? or must you just set it up on simplex?
73 Whit k3wb
On Jul 22, 2014, at 10:29 AM, Bill Kasper williamkasper@frontiernet.net wrote:
Hi Forrest et al,
The TX tone (CTCSS DCL and other names) may be required for the ham repeaters that use it. Modern radios' menus may set the tone independently for each channel or for the entire rig. This tells the repeater that "I really want to talk thru you" and I'm not some skip-signal coming from a different part of the country.
Historically (a hundred years ago?) commercial repeaters had several to many business users on them, as they were expensive and each business that used, ie. paid for the repeater service, had a different tone to open only that businesses own radios: a taxi had one tone, the road-repair company another tone, and the delivery company another tone and so on. They had to share the resource (the repeater) and not interfere with each other any more than necessary. CTCSS is the modern technical name of that tone process that used to be called PL - Private Line (Motorola), CG - Channel Guard, General Electric, and privacy codes for various FRS radios, plus other names.
It is the tone ENGAGED on the RECEIVER end that can be problematic: the exact tone MUST be present on the transmitted signal for the receiver squelch (TSQL) to open so you can hear the other station on that frequency; which may or may not be what you want.
As an example, I setup a simplex ham voice channel for myself and XYL to use as a 'Private Line' (Motorola trademark) only for us: car-house, car-car etc. This is fine for us, and I have TSQL set on both radios for this channel. On this 'unused' simplex channel she can only hear me and I can only hear her. If someone else hears us, which they could, and then tries to answer me, I would not hear them unless they figured out and then transmitted our 'PL' tone.
As an aside, this feature, as implemented on the FRS private channel radios, means that you can only hear people transmitting your private code on your channel; people with no (RX) tone set can hear you too, so not really very private, but helps reduce chatter from other users when listening on a shared resource/channel. The implication is that, if you use your FRS channel 1, by convention, as an emergency receiver, make sure the privacy codes are turned off, so you will be able to hear everyone on channel 1, even if they have a privacy tone enabled.
other comments?
73 de Bill WB2SXY
--
On 7/22/2014 12:26 PM, Forrest wrote:
Curious why you say that using tone squelch on both TX and RX is not recommended???
THX. Forrest
On Jul 21, 2014, at 6:51 PM, John LaMartinaJohnLa@usa.net wrote:
Yes, TSQL sets the CTCSS or DCS tone on both TX and RX. (Not Recommended). Tone sets CTCSS or DCS on TX only. This explains in a bit more detail. http://www.miklor.com/COM/UV_CTCSS.php I hope this helps...
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dave Nathanson Sent: Monday, July 21, 2014 7:22 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Someone else will hopefully correct me if I'm wrong, (and I didn't look this up) but I believe that in this usage, "Tone" applies when transmitting only. TSQL, or Tone Squelch applies to both transmitting& receiving.
"Tone" is more common. If you use TSQL when you should have used Tone, others will be able to hear you, but you will only be able to hear them if they also use the same tone. To complicate things slightly, many repeaters require a tone to activate them, but many repeaters strip out the tone as the re-transmit. It is often a good idea to start with "tone" and only use TSQL if needed.
Best, Dave Nathanson KG6ZJO
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4716 / Virus Database: 3986/7900 - Release Date: 07/22/14
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Whit,
You must have missed my earlier post. New CHIRP users like yourself that are confused by the displayed default values that are unused, ignored and don't matter based on the Tone Mode selected, should enable "Hide Unused Fields". With this feature enabled, the default values in the columns that are unused, ignored and don't matter are shown blank. Here is how you enable this feature.
1. click "View" in the menu bar 2. click "Hide Unused Fields" so that it is enabled (a check mark is displayed to the left)
Jim KC9HI
On Tue, Jul 22, 2014 at 5:18 PM, Dr. Whit Woodard towhit@me.com wrote:
Thanks, Jim. I select the “Tone” option in the Tone Mode column; the Repeater PL in the Tone column; “88.5” in the ToneSql column; “023” in both the DTCS Code and DTCS Rx Code columns; and finally “Tone->Tone” in the Cross Mode column. All but the Tone column do not allow me a blank or “none” option. Does that sound right to you?
Whit k3wb
Yes Jim, I did miss that. Wow what a difference. I just finished making a form to keep track of my input to the template and now I can simplify it considerably. Thanks a million. May I presume that if for any reason I have a setting that requires one of the hidden columns it will re=appear? This software gets better and better. What a wonderful help it is and how generous of those who devised it. Many, many thanks.
73 Whit k3wb
On Jul 22, 2014, at 3:58 PM, Jim Unroe rock.unroe@gmail.com wrote:
Whit,
You must have missed my earlier post. New CHIRP users like yourself that are confused by the displayed default values that are unused, ignored and don't matter based on the Tone Mode selected, should enable "Hide Unused Fields". With this feature enabled, the default values in the columns that are unused, ignored and don't matter are shown blank. Here is how you enable this feature.
- click "View" in the menu bar
- click "Hide Unused Fields" so that it is enabled (a check mark is displayed to the left)
Jim KC9HI
On Tue, Jul 22, 2014 at 5:18 PM, Dr. Whit Woodard towhit@me.com wrote: Thanks, Jim. I select the “Tone” option in the Tone Mode column; the Repeater PL in the Tone column; “88.5” in the ToneSql column; “023” in both the DTCS Code and DTCS Rx Code columns; and finally “Tone->Tone” in the Cross Mode column. All but the Tone column do not allow me a blank or “none” option. Does that sound right to you?
Whit k3wb
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
May I presume that if for any reason I have a setting that requires one of the hidden columns it will re=appear?
Whit,
Yes. Test it.
Select Tone as the Tone Mode and you will see 88.5 (or some other value) in the Tone column and the ToneSql column will be blank. Then change the Tone Mode selection to TSQL and you will see the Tone column become blank and the 88.5 will appear in the ToneSql column.
Note: Be sure that when you change the Tone Mode selection that you click onto another cell to make the selection "stick". Otherwise it will look selected when it really isn't. If you click the [Go] button and value stays, you had it selected properly. If the setting reverts back to the original setting, it wasn't.
Jim KC9HI
- click "View" in the menu bar
- click "Hide Unused Fields" so that it is enabled (a check mark is
displayed to the left)
Jim, I thought we made this the default a while back? Maybe I just imagined that? If not, I think we should make this change as it seems to clearly help users understand what's going on :)
--Dan
On Tue, Jul 22, 2014 at 7:51 PM, Dan Smith dsmith@danplanet.com wrote:
- click "View" in the menu bar
- click "Hide Unused Fields" so that it is enabled (a check mark is
displayed to the left)
Jim, I thought we made this the default a while back? Maybe I just imagined that? If not, I think we should make this change as it seems to clearly help users understand what's going on :)
--Dan
I agree. I'll look to see and if it isn't the default I will submit a change. Jim
Greetings Whit & list,
Hope this is not getting too far off Chirp-topic.
Other than having had to program about 40 radios with Chirp, which worked vy well, I have almost no knowledge of it so I have to defer your template question to someone who knows a lot more about it than I do.
The voice channel that my wife (also a ham) and I use is a simplex one not far from some other simplex channels. Using around 50 watts on 2m we are able to talk about 25 miles house-to-car; J-Pole on our house with some elevation, hence the reason that repeaters were invented, to increase range.
If you contacted your local repeater council people and asked for a repeater pair of frequencies, they may be able to assign them to you. If you did not want others to use it, your repeater would be considered 'closed' I think. The Council members would have to look into your questions.
Also, as John mentioned, a repeater may require a tone to get into it, but the repeater may or may not transmit a tone out.
73 de Bill WB2SXY
---
On 7/22/2014 1:48 PM, Dr. Whit Woodard wrote:
Bill, Thanks, that is very helpful. The question that comes
to my mind is why then does chirp require us to put some value in the ToneSql column on every memory channel? I have just put in the lowest tone, because the software does not allow me to leave it blank. It would be very helpful if we had the option of leaving unnecessary columns blank. We can only do that with a couple of the entries. I would just amend the template to eliminate those columns, but I do not know which are necessary and which are not. I hope in time I will gain a better understanding of the template which apparently is restricted by both the hardware and the chirp software. Your arrangement for communication just with your family is a great idea. I would like to do something very similar. Do you employ that on a repeater so that you can obtain better coverage? or must you just set it up on simplex?
73 Whit k3wb
On Jul 22, 2014, at 10:29 AM, Bill Kasperwilliamkasper@frontiernet.net wrote:
Hi Forrest et al,
The TX tone (CTCSS DCL and other names) may be required for the ham repeaters that use it. Modern radios' menus may set the tone independently for each channel or for the entire rig. This tells the repeater that "I really want to talk thru you" and I'm not some skip-signal coming from a different part of the country.
Historically (a hundred years ago?) commercial repeaters had several to many business users on them, as they were expensive and each business that used, ie. paid for the repeater service, had a different tone to open only that businesses own radios: a taxi had one tone, the road-repair company another tone, and the delivery company another tone and so on. They had to share the resource (the repeater) and not interfere with each other any more than necessary. CTCSS is the modern technical name of that tone process that used to be called PL - Private Line (Motorola), CG - Channel Guard, General Electric, and privacy codes for various FRS radios, plus other names.
It is the tone ENGAGED on the RECEIVER end that can be problematic: the exact tone MUST be present on the transmitted signal for the receiver squelch (TSQL) to open so you can hear the other station on that frequency; which may or may not be what you want.
As an example, I setup a simplex ham voice channel for myself and XYL to use as a 'Private Line' (Motorola trademark) only for us: car-house, car-car etc. This is fine for us, and I have TSQL set on both radios for this channel. On this 'unused' simplex channel she can only hear me and I can only hear her. If someone else hears us, which they could, and then tries to answer me, I would not hear them unless they figured out and then transmitted our 'PL' tone.
As an aside, this feature, as implemented on the FRS private channel radios, means that you can only hear people transmitting your private code on your channel; people with no (RX) tone set can hear you too, so not really very private, but helps reduce chatter from other users when listening on a shared resource/channel. The implication is that, if you use your FRS channel 1, by convention, as an emergency receiver, make sure the privacy codes are turned off, so you will be able to hear everyone on channel 1, even if they have a privacy tone enabled.
other comments?
73 de Bill WB2SXY
--
On 7/22/2014 12:26 PM, Forrest wrote:
Curious why you say that using tone squelch on both TX and RX is not recommended???
THX. Forrest
On Jul 21, 2014, at 6:51 PM, John LaMartinaJohnLa@usa.net wrote:
Yes, TSQL sets the CTCSS or DCS tone on both TX and RX. (Not Recommended). Tone sets CTCSS or DCS on TX only. This explains in a bit more detail. http://www.miklor.com/COM/UV_CTCSS.php I hope this helps...
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dave Nathanson Sent: Monday, July 21, 2014 7:22 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Someone else will hopefully correct me if I'm wrong, (and I didn't look this up) but I believe that in this usage, "Tone" applies when transmitting only. TSQL, or Tone Squelch applies to both transmitting& receiving.
"Tone" is more common. If you use TSQL when you should have used Tone, others will be able to hear you, but you will only be able to hear them if they also use the same tone. To complicate things slightly, many repeaters require a tone to activate them, but many repeaters strip out the tone as the re-transmit. It is often a good idea to start with "tone" and only use TSQL if needed.
Best, Dave Nathanson KG6ZJO
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4716 / Virus Database: 3986/7861 - Release Date: 07/16/14
Thanks for the follow-up, Bill. While I do have a Tech license, more often I’m involved in public safety communications and just as you say, we look to to exclude signals (on the same freq) by way of tone squelch. As you know, these signals, while often distant geographically, will come in via skip or even direct sometimes and involve many thousands of watts and can disrupt what you’re trying to accomplish locally.
We were looking at the same issue from different standpoints and it just hadn’t occurred to me to say ‘not recommended’ involving use of tone or DCS on receive. It boils down to ‘it depends’. :)
Regards, Forrest
On Jul 22, 2014, at 12:29 PM, Bill Kasper williamkasper@frontiernet.net wrote:
Hi Forrest et al,
The TX tone (CTCSS DCL and other names) may be required for the ham repeaters that use it. Modern radios' menus may set the tone independently for each channel or for the entire rig. This tells the repeater that "I really want to talk thru you" and I'm not some skip-signal coming from a different part of the country.
Historically (a hundred years ago?) commercial repeaters had several to many business users on them, as they were expensive and each business that used, ie. paid for the repeater service, had a different tone to open only that businesses own radios: a taxi had one tone, the road-repair company another tone, and the delivery company another tone and so on. They had to share the resource (the repeater) and not interfere with each other any more than necessary. CTCSS is the modern technical name of that tone process that used to be called PL - Private Line (Motorola), CG - Channel Guard, General Electric, and privacy codes for various FRS radios, plus other names.
It is the tone ENGAGED on the RECEIVER end that can be problematic: the exact tone MUST be present on the transmitted signal for the receiver squelch (TSQL) to open so you can hear the other station on that frequency; which may or may not be what you want.
As an example, I setup a simplex ham voice channel for myself and XYL to use as a 'Private Line' (Motorola trademark) only for us: car-house, car-car etc. This is fine for us, and I have TSQL set on both radios for this channel. On this 'unused' simplex channel she can only hear me and I can only hear her. If someone else hears us, which they could, and then tries to answer me, I would not hear them unless they figured out and then transmitted our 'PL' tone.
As an aside, this feature, as implemented on the FRS private channel radios, means that you can only hear people transmitting your private code on your channel; people with no (RX) tone set can hear you too, so not really very private, but helps reduce chatter from other users when listening on a shared resource/channel. The implication is that, if you use your FRS channel 1, by convention, as an emergency receiver, make sure the privacy codes are turned off, so you will be able to hear everyone on channel 1, even if they have a privacy tone enabled.
other comments?
73 de Bill WB2SXY
--
On 7/22/2014 12:26 PM, Forrest wrote:
Curious why you say that using tone squelch on both TX and RX is not recommended???
THX. Forrest
On Jul 21, 2014, at 6:51 PM, John LaMartinaJohnLa@usa.net wrote:
Yes, TSQL sets the CTCSS or DCS tone on both TX and RX. (Not Recommended). Tone sets CTCSS or DCS on TX only. This explains in a bit more detail. http://www.miklor.com/COM/UV_CTCSS.php I hope this helps...
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dave Nathanson Sent: Monday, July 21, 2014 7:22 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Someone else will hopefully correct me if I'm wrong, (and I didn't look this up) but I believe that in this usage, "Tone" applies when transmitting only. TSQL, or Tone Squelch applies to both transmitting& receiving.
"Tone" is more common. If you use TSQL when you should have used Tone, others will be able to hear you, but you will only be able to hear them if they also use the same tone. To complicate things slightly, many repeaters require a tone to activate them, but many repeaters strip out the tone as the re-transmit. It is often a good idea to start with "tone" and only use TSQL if needed.
Best, Dave Nathanson KG6ZJO
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Forrest, As described below, not every station/repeater that requires a tone for access will transmit one back. Sending a tone back to you is not required. Reference to this can be found at http://www.miklor.com/COM/UV_CTCSS.php
Setting a channel Tone to TSQL Requires your radio to hear a tone from the other station or your receiver will not open to receive it. Always start with TX tone only.
I hope this helps... John http://www.miklor.com/
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Forrest Sent: Tuesday, July 22, 2014 12:26 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Curious why you say that using tone squelch on both TX and RX is not recommended???
THX. Forrest
On Jul 21, 2014, at 6:51 PM, John LaMartina JohnLa@usa.net wrote:
Yes, TSQL sets the CTCSS or DCS tone on both TX and RX. (Not Recommended). Tone sets CTCSS or DCS on TX only. This explains in a bit more detail. http://www.miklor.com/COM/UV_CTCSS.php I hope this helps...
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dave Nathanson Sent: Monday, July 21, 2014 7:22 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Someone else will hopefully correct me if I'm wrong, (and I didn't look this up) but I believe that in this usage, "Tone" applies when transmitting only. TSQL, or Tone Squelch applies to both transmitting & receiving.
"Tone" is more common. If you use TSQL when you should have used Tone, others will be able to hear you, but you will only be able to hear them if they also use the same tone. To complicate things slightly, many repeaters require a tone to activate them, but many repeaters strip out the tone as the re-transmit. It is often a good idea to start with "tone" and only use TSQL if needed.
Best, Dave Nathanson KG6ZJO
Thanks, John. As I mentioned to Bill, I was looking at the issue from a different perspective, where tone squelch on receive is often a very good or even necessary thing, though generally not related to amateur communications.
Regards, Forrest
On Jul 22, 2014, at 12:31 PM, John LaMartina JohnLa@usa.net wrote:
Forrest, As described below, not every station/repeater that requires a tone for access will transmit one back. Sending a tone back to you is not required. Reference to this can be found at http://www.miklor.com/COM/UV_CTCSS.php
Setting a channel Tone to TSQL Requires your radio to hear a tone from the other station or your receiver will not open to receive it. Always start with TX tone only.
I hope this helps... John http://www.miklor.com/
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Forrest Sent: Tuesday, July 22, 2014 12:26 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Curious why you say that using tone squelch on both TX and RX is not recommended???
THX. Forrest
On Jul 21, 2014, at 6:51 PM, John LaMartina JohnLa@usa.net wrote:
Yes, TSQL sets the CTCSS or DCS tone on both TX and RX. (Not Recommended). Tone sets CTCSS or DCS on TX only. This explains in a bit more detail. http://www.miklor.com/COM/UV_CTCSS.php I hope this helps...
John K3NXU http://www.miklor.com
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dave Nathanson Sent: Monday, July 21, 2014 7:22 PM To: Discussion of CHIRP Subject: Re: [chirp_users] Settings
Someone else will hopefully correct me if I'm wrong, (and I didn't look this up) but I believe that in this usage, "Tone" applies when transmitting only. TSQL, or Tone Squelch applies to both transmitting & receiving.
"Tone" is more common. If you use TSQL when you should have used Tone, others will be able to hear you, but you will only be able to hear them if they also use the same tone. To complicate things slightly, many repeaters require a tone to activate them, but many repeaters strip out the tone as the re-transmit. It is often a good idea to start with "tone" and only use TSQL if needed.
Best, Dave Nathanson KG6ZJO
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
On Tue, Jul 22, 2014 at 12:26 PM, Forrest wfj@usa.com wrote:
Curious why you say that using tone squelch on both TX and RX is not recommended???
THX. Forrest
Forrest,
This is more directed to new users that don't know what tone squelch is or how it works. What happens is that they program both a TX tone and an RX tone for a repeater that does not transmit one and then ask "The green receive light lights up but I can't hear anything. Why doesn't it work?" Programming no RX tone always works. Programming an RX tone when the other station doesn't transmit one, or transmits a different tone than the one programmed, never works (unless your goal is to never hear that station:).
Once it understand how tone squelch works, why it would be needed in a particular application and it is known that the remote station is transmitting the matching tone, it is certainly encouraged to use both.
Jim KC9HI
Agreed, absolutely..
Forrest
On Jul 22, 2014, at 4:01 PM, Jim Unroe rock.unroe@gmail.com wrote:
On Tue, Jul 22, 2014 at 12:26 PM, Forrest wfj@usa.com wrote: Curious why you say that using tone squelch on both TX and RX is not recommended???
THX. Forrest
Forrest,
This is more directed to new users that don't know what tone squelch is or how it works. What happens is that they program both a TX tone and an RX tone for a repeater that does not transmit one and then ask "The green receive light lights up but I can't hear anything. Why doesn't it work?" Programming no RX tone always works. Programming an RX tone when the other station doesn't transmit one, or transmits a different tone than the one programmed, never works (unless your goal is to never hear that station:).
Once it understand how tone squelch works, why it would be needed in a particular application and it is known that the remote station is transmitting the matching tone, it is certainly encouraged to use both.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Dr. Woodard, this page really helped me when I first started using Chirp on my uv-B6: http://chirp.danplanet.com/projects/chirp/wiki/MemoryEditorColumns
Hope it helps you! SteveH KJ6UDN
On 7/21/2014 4:14 PM, Dr. Whit Woodard wrote:
There seem to be several settings for the BaoFeng F8+ radio that are of not particular consequence. One that has been confusing me is the “Tone Mode” Doesn’t seem to work on “Tone.” Should I be doing “TSQL” instead? or what? Is there somewhere I can get an explanation of the various settings needed to program the radio. The template is quite different from the sample I have from a friend with another model. Any ideas?
Thanks, Whit k3wb _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
participants (8)
-
Bill Kasper -
Dan Smith -
Dave Nathanson -
Dr. Whit Woodard -
Forrest -
Jim Unroe -
John LaMartina -
Rock-N-Roll 4x4 Club