[arm-allstar] ARRL NewsLine - Allstar Automated Script

[Doug Crompton]

Roselito,

 It already does this. It breaks the file up into about 2.5 minute segments
then breaks for about 20 seconds. The next segment repeats a few seconds of
the tail of the previous for continuity. There are canned voice files that
announce this. ID's are automatic and don't need to be inserted. They will
happen during the 15 -20 second downtime in between segments if the 10
minute period has passed. When nodes are connected it is determined by
their ID timer. This delay is also a window for those who want to
disconnect etc.

Make sure you have holdofftelem=0 on the node you play it on. Otherwise if
someone keys up it will get out of sync. The best thing to do is download
it and play it locally so you can see what it does.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Mon, May 15, 2017 at 12:04 PM, "Roselito de los Reyes via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Hi Doug,
>
> I would like to use the script for our local club, but I would like to
> chop up the recording into 3 min segments and insert the station ID in
> between for repeater reset. Is this currently being implemented or does it
> just play the whole file?
>
> Best regards,
>
> Roselito De Los Reyes
>
>
> > On May 15, 2017, at 8:54 AM, Doug Crompton via arm-allstar <
> arm-allstar at hamvoip.org> wrote:
> >
> > John,
> >
> > Yes. 240000 is 4 minutes  -  (240000/1000)/60 - It was stupid to have
> such
> > granularity in the timers but that's the way it was done in original
> > Allstar. It should just be defined in seconds. There is also a problem
> with
> > the accuracy of some Allstar timers that we are working on right now.
> They
> > are not accurate at this point in any version of Allstar. They tend to
> run
> > about 25-30% long. So setting 4 minutes might mean about 5 minutes.
> > Hopefully we will have a fix for this soon.
> >
> > The other thing you need to consider is any hardware TX timeout that may
> be
> > set. Most radios have a settable TX timeout. I believe many of the
> Motorola
> > radios cannot be set higher than about 3-4 minutes. So you might check
> and
> > be sure it is not the TX itself causing the timeout. Most repeaters set
> > timeout to 3 minutes.
> >
> > The tx_timeout in Allstar was designed around a timeout for repeaters
> which
> > actually announces a timeout but It also works on a simplex node. The
> idea
> > is to stop people from talking too long but also to protect the
> transmitter
> > in the event of a open mic situation. So if you have both software and
> > hardware timeouts generally the SW timeout is set shorter than the HW
> > timeout. The HW timeout being the last line of defense in the event of a
> > failure.
> >
> >
> > On Mon, May 15, 2017 at 10:57 AM, "John Hoser-Smith via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> >> Thanks Doug.  I suspected the ARRL NewsLine (error?) was at their (ARRL)
> >> end.After all - your Bash Script worked for weeks....still worked this
> week
> >> - but pulled an old file.
> >> Mother's Day Special (HA!) I guess.
> >> Doug - I need to increase the Timeout Setting for one of my Allstar
> Nodes.
> >> Inside  rpt.conf  (I  found)
> >>
> >> tx_timeout=240000
> >>
> >> Is this the setting I need to increase to have my Allstar Radio transmit
> >> for longer times before a timeout?
> >> Thanks - 73sN0ECT
> >>
> >>
> >>
> >>
> >>
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>