[App_rpt-users] Squelch Tail Elimination

[Ken]

There are two squelch tails.  One in the user’s receiver which  can be eliminated by using tone squelch and turning off the PL some time before dropping the carrier.  Some commercial rigs respond to the reverse phase tone burst. That is unusual in amateur rigs I think. And some amateur rigs require the tone to be turned off longer that the app_rpt default.  This all has to do with the squelch tail being generated in the user’s receiver. 

 

But if you want the *repeater* not to transmit a squelch tail - from its own receiver - then you need:

  Rxsquelchdelay  in usbradio.con 

as previously discussed in :

 <http://ohnosec.org/pipermail/app_rpt-users/2014-April/009175.html> http://ohnosec.org/pipermail/app_rpt-users/2014-April/009175.html

 

for example

rxsquelchdelay=50 ; delayline in ms, carrier squelch tail eliminator

 

this requires use of the usbradio channel driver.

 

73

Ken

 

 

 

From: R. Wayne [mailto:allstar at controlservers.net] 
Sent: Sunday, March 29, 2015 1:34 AM
To: app_rpt-users at ohnosec.org
Subject: [App_rpt-users] Squelch Tail Elimination

 

After relocating our MSF 5000 to a new location and adjusting the squelch as low as we could reliably go we noticed that we have a squelch tail. Our coordination requires that we don’t. It appears that the MSF has a fixed squelch tail elimination method an no control other than cranking up the squelch again. This is surprising since we use PL encode / decode. I would think that the PL would mute as soon as the user unkeys.

 

With this said is there anything in Allstar that would help with this situation?

 

Wayne

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20150329/6d16ec99/attachment.html>