I did a little research and checking on this. If you set the tone define to null like:
linkunkeyct=
you will get no tone but you wil get a keyup. If you set:
nounkeyct=1
you will get no tone and no keyup at carrier drop so this is the best way to do it.
nounkeyct=0 is the default on the BBB and the default if it is not defined.
73 Doug
WA3DSP
http://www.crompton.com/hamradio
Date: Thu, 29 Jan 2015 10:02:41 -0600
From: asylthe@kc9ona.com
To: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] Duplex / Telemetry / Courtesy Tone Question_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.Thank you to everyone that replied. I believe I do have it figured out now.Mike, I hear what you're saying regarding the 0,0 tone. My goal was to keep the radio from transmitting altogether. I didn't test it, but I believe your suggestion would have transmitted a silent tone which isn't what I was trying to accomplish.Steve, I commented out the 'idrecording=' configuration option under my node stanza, and that has effectively disabled the ID. I didn't have to touch anything in the [telemetry] stanza.So, right now my node is set to duplex=1, there is no ID, and I only hear a courtesy tone when a networked user unkeys.Here are the pertinent configuration options I set under my node stanza to accomplish this:duplex=1;idrecording=|iKC9ONA/L; Telemetry & Courtesy Tone Optionstelemetry=telemetry;unlinkedct=ct2 ; Sent when not connected to another node;remotect=ct3 ; Sent when remote base connectedlinkunkeyct=ct8 ; sent when a network user unkeysnolocallinkct=1eannmode=2echolinkdefault=0echolinkdynamic=0nounkeyct=1holdofftelem=1telemdefault=0telemdynamic=0guilinkdefault=0guilinkdynamic=0phonelinkdefault=0phonelinkdynamic=0Thanks!On Wed, Jan 28, 2015 at 1:27 PM, Andrew Sylthe <asylthe@kc9ona.com> wrote:Hello All,I'm struggling to configure my simplex node in a particular way. As of right now I have duplex=0 specified for my node in rpt.conf. My goal is to maintain the functionality of duplex=0, but do want a courtesy tone to transmit ONLY when a remotely connected AllStar node unkeys. I do not want the simplex node to ID or transmit a courtesy tone for local transmissions. Has anyone else configured their node in such a way? If so, would you be willing to share your configuration.I've tried setting duplex=1 in rpt.conf along with the following settings with no luck:; Telemetry & Courtesy Tone Optionstelemetry=telemetry;unlinkedct=ct2 ; Sent when not connected to another noderemotect=ct3 ; Sent when remote base connectedlinkunkeyct=ct8 ; sent when a network user unkeysnolocallinkct=1eannmode=2echolinkdefault=0echolinkdynamic=0nounkeyct=0holdofftelem=1telemdefault=0telemdynamic=0guilinkdefault=0guilinkdynamic=0phonelinkdefault=0phonelinkdynamic=0Thank you in advance for anyone that is able to help!--Andrew Sylthe
KC9ONA--Andrew Sylthe
KC9ONA
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.