Squelch Tail Crash Elimination

Hello,

I have ASL running a Dell Slim Form computer all seems to be work quite well, connections, Echolink and local repeater with great audio reports however… I like to know how to eliminate the squelch crash on the tail maybe adding some milliseconds
to the receiver audio?

The system is a Yaesu DR-1X interfaced with the URIx controller using SimpleUSB in ASL version 20180417

The computer: Dell SFF Version 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64.

I am very novice with Linux and Asterisk but learning bits and pieces…

Thank you

John de KE5RS

. . … ._. …

Well, I don’t want to lead you astray… as I’m not for sure on
this…

Had to think on it a while…

  You might try adding some time to rxondelay (ms)� but I'm not

sure that will delay the repeated audio.

I think it may only delay the cor activation time.

But, if nobody chimes in with the ‘right stuff’ give it a try.

I’m thinkin you might need to create a special audio delay.

73,

…mike/kb8jnm

···

On 6/5/2018 10:10 PM, John W Benedict
wrote:

Hello,

      I have ASL running a Dell Slim Form

computer all seems to be work quite well, connections,
Echolink and local repeater with great audio reports however�
I like to know how to eliminate the squelch crash on the tail
maybe adding some milliseconds to the receiver audio?

      The system is a Yaesu DR-1X interfaced with

the URIx controller using SimpleUSB in ASL version 20180417

      The computer: Dell SFF Version

4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07)
x86_64.

      I am very novice with Linux and Asterisk

but learning bits and pieces�

Thank you

        John

de KE5RS

        _._ . ..... ._. ...




_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit 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.

App_rpt-users@lists.allstarlink.orghttp://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-usershttp://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

I think that if you feed direct discriminator audio to the usb interface and use usbradio then it automatically takes care of the necessary delays and avoids loosing any audio in the process. For best results you can grab the direct discriminator audio from the cable that runs from inside the Receiver Unit to the Filter Unit (shown below), I can’t remember if I used the L-in or the R-in. Or second best you can use the DSP processed discriminator output in the DB15 connector (center pin in center row, pin 8) but it isn’t as good and has more delay.

···

On Tue, Jun 5, 2018 at 9:41 PM, Mike mm@midnighteng.com wrote:

  Well, I don't want to lead you astray... as I'm not for sure on

this…

Had to think on it a while…

  You might try adding some time to rxondelay (ms)  but I'm not

sure that will delay the repeated audio.

I think it may only delay the cor activation time.

But, if nobody chimes in with the ‘right stuff’ give it a try.

I’m thinkin you might need to create a special audio delay.

73,

…mike/kb8jnm

  On 6/5/2018 10:10 PM, John W Benedict

wrote:

Hello,

      I have ASL running a Dell Slim Form

computer all seems to be work quite well, connections,
Echolink and local repeater with great audio reports however…
I like to know how to eliminate the squelch crash on the tail
maybe adding some milliseconds to the receiver audio?

      The system is a Yaesu DR-1X interfaced with

the URIx controller using SimpleUSB in ASL version 20180417

      The computer: Dell SFF Version

4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07)
x86_64.

      I am very novice with Linux and Asterisk

but learning bits and pieces…

Thank you

        John

de KE5RS

        _._ . ..... ._. ...
_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)

To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.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 Chuck and Mike,

Chuck,

Yes… I thought USBRadio with more complexity, not simple would be what was needed… I am using pin 9 now from the 15 pin and going to pin 21 at the URIx. I will look at what you show below and see if that is the direction to go. As you
described “Best results”, I will check into grabbing the discriminator audio being a little nervous with my skill set
:blush:

Thank you.

Mike,

I did play some with the “rxondelay” but with no luck. What I remember, adding time to “rxondelay “ gave me a short burst of initial audio out the front speaker with more time getting a longer audio burst before it gets muted. This audio
burst would only happen if the squelch tale drops completely from the previous transmission. I did not hear a difference with what was heard on the air from the transmitter including the squelch crash was still present.

Thank you for your reply…

John de KE5RS

. . … ._. …

On Behalf Of Chuck Henderson

···

I think that if you feed direct discriminator audio to the usb interface and use usbradio then it automatically takes care of the necessary delays and avoids loosing any audio in the process. For best results you can grab the direct discriminator
audio from the cable that runs from inside the Receiver Unit to the Filter Unit (shown below), I can’t remember if I used the L-in or the R-in. Or second best you can use the DSP processed discriminator output in the DB15 connector (center pin in center row,
pin 8) but it isn’t as good and has more delay.

On Tue, Jun 5, 2018 at 9:41 PM, Mike mm@midnighteng.com wrote:

Well, I don’t want to lead you astray… as I’m not for sure on this…

Had to think on it a while…

You might try adding some time to rxondelay (ms) but I’m not sure that will delay the repeated audio.

I think it may only delay the cor activation time.

But, if nobody chimes in with the ‘right stuff’ give it a try.

I’m thinkin you might need to create a special audio delay.

73,

…mike/kb8jnm

On 6/5/2018 10:10 PM, John W Benedict wrote:

Hello,

I have ASL running a Dell Slim Form computer all seems to be work quite well, connections, Echolink and local repeater with great audio reports however… I like to know how to eliminate
the squelch crash on the tail maybe adding some milliseconds to the receiver audio?

The system is a Yaesu DR-1X interfaced with the URIx controller using SimpleUSB in ASL version 20180417

The computer: Dell SFF Version 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64.

I am very novice with Linux and Asterisk but learning bits and pieces…

Thank you

John de KE5RS

. . … ._. …

_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)
To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://lists.allstarlink.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.

Using the channel driver usbradio, did you run radio-tune-menu and adjust the squelch?
It sounds to me, like the squelch is wide open, and you’re using usbradio.conf to define the pl tone(s). If your squelch is wide open, you will hear that bit of squelch crash after the tone is dropped, and before the repeater drops.

There are 2 ways to go on the settings, and I don’t remember which is which so there’s a 50/50 shot at this… but “as I recall” (and I’m not remembering well, these days) the Lower the number, the ‘looser’ the squelch.

For experimentation, you might try turning the tone requirement for the receiver off, and adjusting that value, while listening to the output of the repeater (while not hooked up to anyone) and determine where the squelch level should be.

best of luck es 73
-Geoff/W5OMR (29655)

···

On Wed, Jun 6, 2018 at 5:37 AM, John W Benedict John@ke5rs.com wrote:

Thank you Chuck and Mike,

Chuck,

Yes… I thought USBRadio with more complexity, not simple would be what was needed… I am using pin 9 now from the 15 pin and going to pin 21 at the URIx. I will look at what you show below and see if that is the direction to go. As you
described “Best results”, I will check into grabbing the discriminator audio being a little nervous with my skill set
:blush:

Thank you.

Mike,

I did play some with the “rxondelay” but with no luck. What I remember, adding time to “rxondelay “ gave me a short burst of initial audio out the front speaker with more time getting a longer audio burst before it gets muted. This audio
burst would only happen if the squelch tale drops completely from the previous transmission. I did not hear a difference with what was heard on the air from the transmitter including the squelch crash was still present.

Thank you for your reply…

John de KE5RS

. . … ._. …

From: App_rpt-users app_rpt-users-bounces@lists.allstarlink.org
On Behalf Of Chuck Henderson
Sent: Tuesday, June 5, 2018 10:45 PM
To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Squelch Tail Crash Elimination

I think that if you feed direct discriminator audio to the usb interface and use usbradio then it automatically takes care of the necessary delays and avoids loosing any audio in the process. For best results you can grab the direct discriminator
audio from the cable that runs from inside the Receiver Unit to the Filter Unit (shown below), I can’t remember if I used the L-in or the R-in. Or second best you can use the DSP processed discriminator output in the DB15 connector (center pin in center row,
pin 8) but it isn’t as good and has more delay.

On Tue, Jun 5, 2018 at 9:41 PM, Mike mm@midnighteng.com wrote:

Well, I don’t want to lead you astray… as I’m not for sure on this…

Had to think on it a while…

You might try adding some time to rxondelay (ms) but I’m not sure that will delay the repeated audio.

I think it may only delay the cor activation time.

But, if nobody chimes in with the ‘right stuff’ give it a try.

I’m thinkin you might need to create a special audio delay.

73,

…mike/kb8jnm

On 6/5/2018 10:10 PM, John W Benedict wrote:

Hello,

I have ASL running a Dell Slim Form computer all seems to be work quite well, connections, Echolink and local repeater with great audio reports however… I like to know how to eliminate
the squelch crash on the tail maybe adding some milliseconds to the receiver audio?

The system is a Yaesu DR-1X interfaced with the URIx controller using SimpleUSB in ASL version 20180417

The computer: Dell SFF Version 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64.

I am very novice with Linux and Asterisk but learning bits and pieces…

Thank you

John de KE5RS

. . … ._. …

_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)
 
To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://lists.allstarlink.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.


App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.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.

Operating your AM rig without a scope is like driving our car at night without headlights. (~K4KYV)

73 = Best Regards,
-Geoff/W5OMR

Are you using AllStar to generate the TX PL tone?? If so, there
is a setting to turn the PL off before the TX. If the user radio
has a PL decode set and the it responds quickly, the user radio
will mute before the repeater TX drops. (Seems to work here,
YMMV).

  txtoctype = notone      ; Transmit tone control type:

no,phase,notone

                          ; no - CTCSS tone encoding with no hang

time

                          ; phase - encode CTCSS and reverse phase

                          ; AKA ("reverse burst") before unkeying TX

                          ; notone - encode CTCSS and stop sending

tone before unkeying TX

                          ; AKA ("chicken burst")

…STeve - KF5VH

···

On 6/6/2018 9:24 AM, ARS W5OMR wrote:

      Using the

channel driver usbradio, did you run radio-tune-menu and
adjust the squelch?

      It sounds to me, like the squelch is wide open, and you're

using usbradio.conf to define the pl tone(s). If your squelch
is wide open, you will hear that bit of squelch crash after
the tone is dropped, and before the repeater drops.

      There are 2 ways to go on the settings, and I don't remember

which is which so there’s a 50/50 shot at this… but “as I
recall” (and I’m not remembering well, these days) the Lower
the number, the ‘looser’ the squelch.

      For experimentation, you might try turning the tone

requirement for the receiver off, and adjusting that value,
while listening to the output of the repeater (while not
hooked up to anyone) and determine where the squelch level
should be.

      best of luck es 73

      -Geoff/W5OMR (29655)
      On Wed, Jun 6, 2018 at 5:37 AM, John W

Benedict John@ke5rs.com
wrote:

Thank you Chuck and Mike,

Chuck,

              Yes… I thought USBRadio with more

complexity, not simple would be what was needed… I am
using pin 9 now from the 15 pin and going to pin 21 at
the URIx. I will look at what you show below and see
if that is the direction to go. As you described
“Best results”, I will check into grabbing the
discriminator audio being a little nervous with my
skill set
:blush:

Thank you.

Mike,

              I did play some with the

“rxondelay” but with no luck. What I remember, adding
time to “rxondelay “ gave me a short burst of initial
audio out the front speaker with more time getting a
longer audio burst before it gets muted. This audio
burst would only happen if the squelch tale drops
completely from the previous transmission. I did not
hear a difference with what was heard on the air from
the transmitter including the squelch crash was still
present.

Thank you for your reply…

                  John de

KE5RS

                  _._ . ..... ._. ...

From: App_rpt-users <app_rpt-users-bounces@lists.allstarlink.org >
On Behalf Of Chuck Henderson
Sent: Tuesday, June 5, 2018 10:45 PM
To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Squelch Tail Crash
Elimination

                    I think that if you feed

direct discriminator audio to the usb interface
and use usbradio then it automatically takes
care of the necessary delays and avoids loosing
any audio in the process. For best results you
can grab the direct discriminator audio from the
cable that runs from inside the Receiver Unit to
the Filter Unit (shown below), I can’t remember
if I used the L-in or the R-in. Or second best
you can use the DSP processed discriminator
output in the DB15 connector (center pin in
center row, pin 8) but it isn’t as good and has
more delay.

                      On Tue, Jun 5, 2018 at 9:41

PM, Mike <mm@midnighteng.com >
wrote:

                          Well, I don't want to lead you astray...

as I’m not for sure on this…

Had to think on it a while…

                          You might try adding some time to

rxondelay (ms) but I’m not sure that will
delay the repeated audio.

                          I think it may only delay the cor

activation time.

                          But, if nobody chimes in with the 'right

stuff’ give it a try.

                          I'm thinkin you might need to create a

special audio delay.

73,

…mike/kb8jnm

                                On 6/5/2018 10:10

PM, John W Benedict wrote:

Hello,

                                  I have ASL

running a Dell Slim Form computer
all seems to be work quite well,
connections, Echolink and local
repeater with great audio reports
however… I like to know how to
eliminate the squelch crash on the
tail maybe adding some
milliseconds to the receiver
audio?

                                  The system is a

Yaesu DR-1X interfaced with the
URIx controller using SimpleUSB in
ASL version 20180417

                                  The computer:

Dell SFF Version 4.9.0-6-amd64 #1
SMP Debian 4.9.88-1+deb9u1
(2018-05-07) x86_64.

                                  I am very

novice with Linux and Asterisk but
learning bits and pieces…

Thank you

                                    John

de KE5RS

                                    _._ . ..... ._. ...
_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)

To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.
                        _______________________________________________

                        App_rpt-users mailing list

                        App_rpt-users@lists.allstarlink.org

                        [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)



                        To unsubscribe from this list please visit [
                          http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.

        _______________________________________________

        App_rpt-users mailing list

        App_rpt-users@lists.allstarlink.org

        [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)



        To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.


Operating
your AM rig without a scope is like driving our car at night
without headlights. (~K4KYV)

      73 = Best Regards,

      -Geoff/W5OMR



_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit 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.


Virus-free. www.avast.com

App_rpt-users@lists.allstarlink.orghttp://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-usershttp://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

Geoff, Steve and other curious,

My Yaesu DR-1 repeater has been originally configured for HamVOIP using the RPi3, Simple USB with the ComSpec TS64 at the URIx to generate the PL for TX. Typical squelch setting, not opened at the repeater
receiver. The cable interface, custom pinout comes right off the stock repeater 15pin connector connected to the 25pin connector on the URIx. It all works very good. As a standalone repeater.

HamVOIP does has a feature, “rxaudiodelay” in SimpleUSB that delays the audio eliminating the squelch crash. That also works well…

The repeater system works very well as a standalone repeater but… with network traffic such as connected links including Echolink, occasionally I get a little audio flutter, hesitation like dropouts and sometimes
the hesitation, like stuttering, the time builds into larger delays like a couple to few seconds. This has been driving us nuts… I have a couple Linux sharp ham buddies near me who have been helping me. We have checked the Roadrunner bandwidth and the Pi
CPU usage right during the audio flutter activity and all seems well capable with plenty to spare should not be a problem or cause.

It was suggested by another friend in the area I try the ASL image with Debian on a computer. I purchased the DELL SFF 64GB solid state drive and installed the ASL image from Allstar now all up and running
I think may have cured the audio flutter problem but now having the squelch crash feature.

Using the Tone Squelch at the user end will probably work that but I thought I like to take care of it at the repeater transmitter side if I can.

That’s where I’m at now.

At this point I may investigate the discriminator audio, pick it off in the receiver and use USBRadio configuration suggested by Chuck. If I can get motivated
:blush:.

I really appreciate all the help and replies.

Thank you.

···

John de KE5RS

From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org]
On Behalf Of Steve Mahler
Sent: Wednesday, June 06, 2018 9:41 AM
To: app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Squelch Tail Crash Elimination

Are you using AllStar to generate the TX PL tone?? If so, there is a setting to turn the PL off before the TX. If the user radio has a PL decode set and the it responds quickly, the user radio will mute before the repeater TX drops. (Seems to work here,
YMMV).

txtoctype = notone ; Transmit tone control type: no,phase,notone

                    ; no - CTCSS tone encoding with no hang time

                    ; phase - encode CTCSS and reverse phase

                    ; AKA ("reverse burst") before unkeying TX

                    ; notone - encode CTCSS and stop sending tone before unkeying TX

                    ; AKA ("chicken burst")

…STeve - KF5VH

On 6/6/2018 9:24 AM, ARS W5OMR wrote:

Using the channel driver usbradio, did you run radio-tune-menu and adjust the squelch?

It sounds to me, like the squelch is wide open, and you’re using usbradio.conf to define the pl tone(s). If your squelch is wide open, you will hear that bit of squelch crash after the tone is dropped, and before the repeater drops.

There are 2 ways to go on the settings, and I don’t remember which is which so there’s a 50/50 shot at this… but “as I recall” (and I’m not remembering well, these days) the Lower the number, the ‘looser’ the squelch.

For experimentation, you might try turning the tone requirement for the receiver off, and adjusting that value, while listening to the output of the repeater (while not hooked up to anyone) and determine where the squelch level should be.

best of luck es 73

-Geoff/W5OMR (29655)

On Wed, Jun 6, 2018 at 5:37 AM, John W Benedict John@ke5rs.com wrote:

Thank you Chuck and Mike,

Chuck,

Yes… I thought USBRadio with more complexity, not simple would be what was needed… I am using pin 9 now from the 15 pin and going to pin 21 at the URIx. I will look at what you
show below and see if that is the direction to go. As you described “Best results”, I will check into grabbing the discriminator audio being a little nervous with my skill set
:blush:

Thank you.

Mike,

I did play some with the “rxondelay” but with no luck. What I remember, adding time to “rxondelay “ gave me a short burst of initial audio out the front speaker with more time
getting a longer audio burst before it gets muted. This audio burst would only happen if the squelch tale drops completely from the previous transmission. I did not hear a difference with what was heard on the air from the transmitter including the squelch
crash was still present.

Thank you for your reply…

John de KE5RS

. . … ._. …

From: App_rpt-users app_rpt-users-bounces@lists.allstarlink.org
On Behalf Of Chuck Henderson
Sent: Tuesday, June 5, 2018 10:45 PM
To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Squelch Tail Crash Elimination

I think that if you feed direct discriminator audio to the usb interface and use usbradio then it automatically takes care of the necessary delays and avoids loosing any audio in
the process. For best results you can grab the direct discriminator audio from the cable that runs from inside the Receiver Unit to the Filter Unit (shown below), I can’t remember if I used the L-in or the R-in. Or second best you can use the DSP processed
discriminator output in the DB15 connector (center pin in center row, pin 8) but it isn’t as good and has more delay.

On Tue, Jun 5, 2018 at 9:41 PM, Mike mm@midnighteng.com wrote:

Well, I don’t want to lead you astray… as I’m not for sure on this…

Had to think on it a while…

You might try adding some time to rxondelay (ms) but I’m not sure that will delay the repeated audio.

I think it may only delay the cor activation time.

But, if nobody chimes in with the ‘right stuff’ give it a try.

I’m thinkin you might need to create a special audio delay.

73,

…mike/kb8jnm

On 6/5/2018 10:10 PM, John W Benedict wrote:

Hello,

I have ASL running a Dell Slim Form computer all seems to be work quite well, connections, Echolink and local repeater with great audio reports however… I like to know how to eliminate
the squelch crash on the tail maybe adding some milliseconds to the receiver audio?

The system is a Yaesu DR-1X interfaced with the URIx controller using SimpleUSB in ASL version 20180417

The computer: Dell SFF Version 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64.

I am very novice with Linux and Asterisk but learning bits and pieces…

Thank you

John de KE5RS

. . … ._. …

_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)
To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://lists.allstarlink.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.


App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://lists.allstarlink.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.

Operating your AM rig without a scope is like driving our car at night without headlights. (~K4KYV)

73 = Best Regards,

-Geoff/W5OMR

_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)
To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.

Virus-free.

www.avast.com

Why did you use the TS-64 instead of the radio’s PL signal?

Thanks,

Bob

K6ECM

73

···

On Jun 6, 2018, at 12:31 PM, John W Benedict John@ke5rs.com wrote:

Geoff, Steve and other curious,

My Yaesu DR-1 repeater has been originally configured for HamVOIP using the RPi3, Simple USB with the ComSpec TS64 at the URIx to generate the PL for TX. Typical squelch setting, not opened at the repeater
receiver. The cable interface, custom pinout comes right off the stock repeater 15pin connector connected to the 25pin connector on the URIx. It all works very good. As a standalone repeater.

HamVOIP does has a feature, “rxaudiodelay” in SimpleUSB that delays the audio eliminating the squelch crash. That also works well…

The repeater system works very well as a standalone repeater but… with network traffic such as connected links including Echolink, occasionally I get a little audio flutter, hesitation like dropouts and sometimes
the hesitation, like stuttering, the time builds into larger delays like a couple to few seconds. This has been driving us nuts… I have a couple Linux sharp ham buddies near me who have been helping me. We have checked the Roadrunner bandwidth and the Pi
CPU usage right during the audio flutter activity and all seems well capable with plenty to spare should not be a problem or cause.

It was suggested by another friend in the area I try the ASL image with Debian on a computer. I purchased the DELL SFF 64GB solid state drive and installed the ASL image from Allstar now all up and running
I think may have cured the audio flutter problem but now having the squelch crash feature.

Using the Tone Squelch at the user end will probably work that but I thought I like to take care of it at the repeater transmitter side if I can.

That’s where I’m at now.

At this point I may investigate the discriminator audio, pick it off in the receiver and use USBRadio configuration suggested by Chuck. If I can get motivated
:blush:.

I really appreciate all the help and replies.

Thank you.

John de KE5RS

<image001.png>

From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org]
On Behalf Of Steve Mahler
Sent: Wednesday, June 06, 2018 9:41 AM
To: app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Squelch Tail Crash Elimination

Are you using AllStar to generate the TX PL tone?? If so, there is a setting to turn the PL off before the TX. If the user radio has a PL decode set and the it responds quickly, the user radio will mute before the repeater TX drops. (Seems to work here,
YMMV).

txtoctype = notone ; Transmit tone control type: no,phase,notone

                    ; no - CTCSS tone encoding with no hang time

                    ; phase - encode CTCSS and reverse phase

                    ; AKA ("reverse burst") before unkeying TX

                    ; notone - encode CTCSS and stop sending tone before unkeying TX

                    ; AKA ("chicken burst")

…STeve - KF5VH

On 6/6/2018 9:24 AM, ARS W5OMR wrote:

Using the channel driver usbradio, did you run radio-tune-menu and adjust the squelch?

It sounds to me, like the squelch is wide open, and you’re using usbradio.conf to define the pl tone(s). If your squelch is wide open, you will hear that bit of squelch crash after the tone is dropped, and before the repeater drops.

There are 2 ways to go on the settings, and I don’t remember which is which so there’s a 50/50 shot at this… but “as I recall” (and I’m not remembering well, these days) the Lower the number, the ‘looser’ the squelch.

For experimentation, you might try turning the tone requirement for the receiver off, and adjusting that value, while listening to the output of the repeater (while not hooked up to anyone) and determine where the squelch level should be.

best of luck es 73

-Geoff/W5OMR (29655)

On Wed, Jun 6, 2018 at 5:37 AM, John W Benedict John@ke5rs.com wrote:

Thank you Chuck and Mike,

Chuck,

Yes… I thought USBRadio with more complexity, not simple would be what was needed… I am using pin 9 now from the 15 pin and going to pin 21 at the URIx. I will look at what you
show below and see if that is the direction to go. As you described “Best results”, I will check into grabbing the discriminator audio being a little nervous with my skill set
:blush:

Thank you.

Mike,

I did play some with the “rxondelay” but with no luck. What I remember, adding time to “rxondelay “ gave me a short burst of initial audio out the front speaker with more time
getting a longer audio burst before it gets muted. This audio burst would only happen if the squelch tale drops completely from the previous transmission. I did not hear a difference with what was heard on the air from the transmitter including the squelch
crash was still present.

Thank you for your reply…

John de KE5RS

. . … ._. …

From: App_rpt-users app_rpt-users-bounces@lists.allstarlink.org
On Behalf Of Chuck Henderson
Sent: Tuesday, June 5, 2018 10:45 PM
To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Squelch Tail Crash Elimination

I think that if you feed direct discriminator audio to the usb interface and use usbradio then it automatically takes care of the necessary delays and avoids loosing any audio in
the process. For best results you can grab the direct discriminator audio from the cable that runs from inside the Receiver Unit to the Filter Unit (shown below), I can’t remember if I used the L-in or the R-in. Or second best you can use the DSP processed
discriminator output in the DB15 connector (center pin in center row, pin 8) but it isn’t as good and has more delay.

<image002.png>

On Tue, Jun 5, 2018 at 9:41 PM, Mike mm@midnighteng.com wrote:

Well, I don’t want to lead you astray… as I’m not for sure on this…

Had to think on it a while…

You might try adding some time to rxondelay (ms) but I’m not sure that will delay the repeated audio.

I think it may only delay the cor activation time.

But, if nobody chimes in with the ‘right stuff’ give it a try.

I’m thinkin you might need to create a special audio delay.

73,

…mike/kb8jnm

On 6/5/2018 10:10 PM, John W Benedict wrote:

Hello,

I have ASL running a Dell Slim Form computer all seems to be work quite well, connections, Echolink and local repeater with great audio reports however… I like to know how to eliminate
the squelch crash on the tail maybe adding some milliseconds to the receiver audio?

The system is a Yaesu DR-1X interfaced with the URIx controller using SimpleUSB in ASL version 20180417

The computer: Dell SFF Version 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64.

I am very novice with Linux and Asterisk but learning bits and pieces…

Thank you

John de KE5RS

. . … ._. …

_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)
To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://lists.allstarlink.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.


App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://lists.allstarlink.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.

Operating your AM rig without a scope is like driving our car at night without headlights. (~K4KYV)

73 = Best Regards,

-Geoff/W5OMR

_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)
To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.

Virus-free.

www.avast.com


App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.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.

Hi Bob

In the beginning, my introduction to Allstar I simply copied an interface cable pinout that was given to me that was already being used with a working Allstar/DR-1 system. I have learned now since, after some
investigation, the Yaesu DR-1 does not have the PL tone available on pin 9, (RX audio out) at the 15pin accessory jack. Pin 9 is the pin I am using with SimpleUSB. I was told if I wanted PL with my transmitted audio I needed to supply a PL source and the
suggestion was to use the TS64. I do not know why PL is not available or if it might be on another pin?

···

John de KE5RS

. . … ._. …

From: App_rpt-users app_rpt-users-bounces@lists.allstarlink.org
On Behalf Of Bob Pyke
Sent: Wednesday, June 6, 2018 3:55 PM
To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Squelch Tail Crash Elimination

Why did you use the TS-64 instead of the radio’s PL signal?

Thanks,

Bob

K6ECM

73

On Jun 6, 2018, at 12:31 PM, John W Benedict John@ke5rs.com wrote:

Geoff, Steve and other curious,

My Yaesu DR-1 repeater has been originally configured for HamVOIP using the RPi3, Simple USB with the ComSpec TS64 at the URIx to generate the PL for TX. Typical squelch setting, not opened at the repeater
receiver. The cable interface, custom pinout comes right off the stock repeater 15pin connector connected to the 25pin connector on the URIx. It all works very good. As a standalone repeater.

HamVOIP does has a feature, “rxaudiodelay” in SimpleUSB that delays the audio eliminating the squelch crash. That also works well…

The repeater system works very well as a standalone repeater but… with network traffic such as connected links including Echolink, occasionally I get a little audio flutter, hesitation like dropouts and sometimes
the hesitation, like stuttering, the time builds into larger delays like a couple to few seconds. This has been driving us nuts… I have a couple Linux sharp ham buddies near me who have been helping me. We have checked the Roadrunner bandwidth and the Pi
CPU usage right during the audio flutter activity and all seems well capable with plenty to spare should not be a problem or cause.

It was suggested by another friend in the area I try the ASL image with Debian on a computer. I purchased the DELL SFF 64GB solid state drive and installed the ASL image from Allstar now all up and running
I think may have cured the audio flutter problem but now having the squelch crash feature.

Using the Tone Squelch at the user end will probably work that but I thought I like to take care of it at the repeater transmitter side if I can.

That’s where I’m at now.

At this point I may investigate the discriminator audio, pick it off in the receiver and use USBRadio configuration suggested by Chuck. If I can get motivated
:blush:.

I really appreciate all the help and replies.

Thank you.

John de KE5RS

<image001.png>

From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org]
On Behalf Of Steve Mahler
Sent: Wednesday, June 06, 2018 9:41 AM
To: app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Squelch Tail Crash Elimination

Are you using AllStar to generate the TX PL tone?? If so, there is a setting to turn the PL off before the TX. If the user radio has a PL decode set and the it responds quickly, the user radio will mute before the repeater TX drops. (Seems to work here,
YMMV).

txtoctype = notone ; Transmit tone control type: no,phase,notone

                    ; no - CTCSS tone encoding with no hang time

                    ; phase - encode CTCSS and reverse phase

                    ; AKA ("reverse burst") before unkeying TX

                    ; notone - encode CTCSS and stop sending tone before unkeying TX

                    ; AKA ("chicken burst")

…STeve - KF5VH

On 6/6/2018 9:24 AM, ARS W5OMR wrote:

Using the channel driver usbradio, did you run radio-tune-menu and adjust the squelch?

It sounds to me, like the squelch is wide open, and you’re using usbradio.conf to define the pl tone(s). If your squelch is wide open, you will hear that bit of squelch crash after the tone is dropped, and before the repeater drops.

There are 2 ways to go on the settings, and I don’t remember which is which so there’s a 50/50 shot at this… but “as I recall” (and I’m not remembering well, these days) the Lower the number, the ‘looser’ the squelch.

For experimentation, you might try turning the tone requirement for the receiver off, and adjusting that value, while listening to the output of the repeater (while not hooked up to anyone) and determine where the squelch level should be.

best of luck es 73

-Geoff/W5OMR (29655)

On Wed, Jun 6, 2018 at 5:37 AM, John W Benedict John@ke5rs.com wrote:

Thank you Chuck and Mike,

Chuck,

Yes… I thought USBRadio with more complexity, not simple would be what was needed… I am using pin 9 now from the 15 pin and going to pin 21 at the URIx. I will look at what you
show below and see if that is the direction to go. As you described “Best results”, I will check into grabbing the discriminator audio being a little nervous with my skill set
:blush:

Thank you.

Mike,

I did play some with the “rxondelay” but with no luck. What I remember, adding time to “rxondelay “ gave me a short burst of initial audio out the front speaker with more time
getting a longer audio burst before it gets muted. This audio burst would only happen if the squelch tale drops completely from the previous transmission. I did not hear a difference with what was heard on the air from the transmitter including the squelch
crash was still present.

Thank you for your reply…

John de KE5RS

. . … ._. …

From: App_rpt-users app_rpt-users-bounces@lists.allstarlink.org
On Behalf Of Chuck Henderson
Sent: Tuesday, June 5, 2018 10:45 PM
To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Squelch Tail Crash Elimination

I think that if you feed direct discriminator audio to the usb interface and use usbradio then it automatically takes care of the necessary delays and avoids loosing any audio in
the process. For best results you can grab the direct discriminator audio from the cable that runs from inside the Receiver Unit to the Filter Unit (shown below), I can’t remember if I used the L-in or the R-in. Or second best you can use the DSP processed
discriminator output in the DB15 connector (center pin in center row, pin 8) but it isn’t as good and has more delay.

<image002.png>

On Tue, Jun 5, 2018 at 9:41 PM, Mike mm@midnighteng.com wrote:

Well, I don’t want to lead you astray… as I’m not for sure on this…

Had to think on it a while…

You might try adding some time to rxondelay (ms) but I’m not sure that will delay the repeated audio.

I think it may only delay the cor activation time.

But, if nobody chimes in with the ‘right stuff’ give it a try.

I’m thinkin you might need to create a special audio delay.

73,

…mike/kb8jnm

On 6/5/2018 10:10 PM, John W Benedict wrote:

Hello,

I have ASL running a Dell Slim Form computer all seems to be work quite well, connections, Echolink and local repeater with great audio reports however… I like to know how to eliminate
the squelch crash on the tail maybe adding some milliseconds to the receiver audio?

The system is a Yaesu DR-1X interfaced with the URIx controller using SimpleUSB in ASL version 20180417

The computer: Dell SFF Version 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64.

I am very novice with Linux and Asterisk but learning bits and pieces…

Thank you

John de KE5RS

. . … ._. …

_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)
To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://lists.allstarlink.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.


App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://lists.allstarlink.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.

Operating your AM rig without a scope is like driving our car at night without headlights. (~K4KYV)

73 = Best Regards,

-Geoff/W5OMR

_______________________________________________
App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)
To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.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.

Virus-free.

www.avast.com


App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://lists.allstarlink.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.

I can’t speak to the specific hardware you’re running, but the latency problem if growing seems to be inherent to the audio interface.
I’ve seen it happen on the pci buss type systems before, as well.

Back to the squelch crash, I think using the usbradio channel and letting the DSP decode ok.

Thank you Geoff

I am going to maybe try that maybe using the discriminator audio from Pin 8 on the DR-1x with USBRadio.

John de KE5RS

. . … ._. …

On Behalf Of ARS W5OMR

···

I can’t speak to the specific hardware you’re running, but the latency problem if growing seems to be inherent to the audio interface.

I’ve seen it happen on the pci buss type systems before, as well.

Back to the squelch crash, I think using the usbradio channel and letting the DSP decode ok.

I’ve -got- to stop replying on my phone… sorry for the typos and terse response…
I’m a big guy and those buttons are -sooo- small…

I meant to say “I think using the usbradio channel driver, and letting the DSP software decode the pl would be better.”

There was even some discussion a while back about using different PL’s to allow different functions… ie: use one pl to access the repeater, locally, yet, another pl to access the repeater and it’s linking. That sounds pretty cool… driving around, talking to the local drive-time crowd, hanging out locally on the repeater, then you hear someone come on the machine from across the country… hmmm… lemme change PL’s and talk to -that- guy…
but… what about the locals?
I think the better option there, would be to connect in monitor mode, have the monitor volume about half-muted so as to not interfere with the local traffic, and THEN, if something is of interest, connect fully to that node, and join in.

Or, you could use a second pl to secure access to sending command codes…

lots of options, when using the DSP portion of ASL.

-Geoff/W5OMR

···

On Wed, Jun 6, 2018 at 8:41 PM, John W Benedict John@ke5rs.com wrote:

Thank you Geoff

I am going to maybe try that maybe using the discriminator audio from Pin 8 on the DR-1x with USBRadio.

John de KE5RS

. . … ._. …

From: App_rpt-users app_rpt-users-bounces@lists.allstarlink.org
On Behalf Of ARS W5OMR
Sent: Wednesday, June 6, 2018 7:22 PM
To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Squelch Tail Crash Elimination

I can’t speak to the specific hardware you’re running, but the latency problem if growing seems to be inherent to the audio interface.

I’ve seen it happen on the pci buss type systems before, as well.

Back to the squelch crash, I think using the usbradio channel and letting the DSP decode ok.


App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.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.

Operating your AM rig without a scope is like driving our car at night without headlights. (~K4KYV)

73 = Best Regards,
-Geoff/W5OMR