<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 11.00.10240.16603"></HEAD>
<BODY id=MailContainerBody class=hmmessage
style="PADDING-TOP: 15px; PADDING-LEFT: 10px; PADDING-RIGHT: 10px" leftMargin=0
topMargin=0 CanvasTabStop="true" name="Compose message area">
<DIV>THANKYOU!</DIV>
<DIV> </DIV>
<DIV>Thanks<BR>73 Neil Sablatzky K8IT<BR>Allstar Node 41838
KITLINK<BR>Allstar Node 42087 KITLINK HUB<BR>IRLP Node exp0068<BR>Echolink
K8IT-L<BR>WIRES-X K8IT 11479 Room 21479</DIV>
<DIV style="FONT: 10pt Tahoma">
<DIV><BR></DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=doug@crompton.com
href="mailto:doug@crompton.com">Doug Crompton</A> </DIV>
<DIV><B>Sent:</B> Saturday, January 09, 2016 2:44 PM</DIV>
<DIV><B>To:</B> <A title=arm-allstar@hamvoip.org
href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</A> </DIV>
<DIV><B>Subject:</B> [arm-allstar] Update version 1.3 BBB/RPi2 now in
testing</DIV></DIV></DIV>
<DIV><BR></DIV>
<DIV dir=ltr>
<STYLE><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></STYLE>
<DIV dir=ltr><FONT face=Tahoma,sans-serif>I am pleased to announce that version
1.3 of the BBB and RPi2 images are now in Alpha testing. The 1.3 versions will
bring the BBB and RPi2 to the same level of updates and code capability. This
update will also mark a split in the code. The 1.x versions will continue with
maintenance updates as needed but a new 2.x version will be appearing in 2016.
The 2.x versions will mark a very significant branch from the current code
including a completely different code concept and many new features and
capabilities. More on that will be coming out soon. The 1.x versions are
considered stable and will be supported into the future during transition to the
2.x code. Here is a list of significant changes for version 1.3 -</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif>Both the BBB and RPi2 have been updated to 4.x kernels
and all associated software has been updated.</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif>New app_rpt.c changes:</FONT><FONT
face=Tahoma,sans-serif><BR></FONT>
<DIV><FONT face=Tahoma,sans-serif></FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif> - Removed
obsolete uchameleon code (about 2500 lines).</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif>
<BR> This is obsolete hardware.</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> - Added COS timeout, with COS flap suppression (new
rx_timeout, rx_cosflap rpt.conf parameters)</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> This is an attempt at
eliminating single node hangups of connected networks. Often a single
node,</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> due to radio or interface
failure, can cause a COS hangup tying up an entire network. If the
timeout<BR> is set COS is monitored and the
indication of asserted COS to the network is dropped if the time is<BR>
exceeded. The COS timeout is</FONT><FONT face=Tahoma,sans-serif>
set in the same way as a TX timeout. The COS </FONT><FONT
face=Tahoma,sans-serif>unasserted indication to<BR> the
network will remain until the hardware COS is cleared. COSFLAP can also be set
and will attempt<BR> to catch conditions where a squelch is
</FONT><FONT face=Tahoma,sans-serif>"flapping" by not resetting the timer during
this condition and<BR> allowing the timeout period to
proceed. </FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif> - Added
telemetry gain levels (new telemnomdb rpt.conf parameter)</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> This will allow a level
adjustment of telemetry (connect, disconnect, etc.) messages. The level
</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> change is in dB like the
Echolink level adjustments. This will eliminate the need to change
the</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> level of audio files.
</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif> - Added
telemetry ducking (AKA: Allison ducking) (new telemduckdb rpt.conf
parameter)</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> This optionally reduces telemetry
levels when a voice signal is present. </FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> - Changed tx timeout variable name from totime to
tx_timeout (the old variable is deprecated,</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif>
</FONT><FONT face=Tahoma,sans-serif> but still works after printing a
console warning)</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> <BR> This was done to avoid the
confusion between TX and RX timeouts. TX timeout is applied
only<BR> to the local transmitter. It is often in addition to
a TX timeout that is set at a longer time in the<BR> radio itself
ensuring double protection for a hung transmitter. The RX timeout, added in
this<BR> update, would normally be set slightly longer than the TX
timeout to offer the same protection <BR> to the network from a COS
hardware failure. <BR> <BR></FONT><FONT
face=Tahoma,sans-serif>New core Asterisk changes:</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif>- Removed need to recompile to enable/disable
RADIO_RELAX</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif> This
command when on reduces the DTMF decode requirements but can also cause DTMF
"Falsing"<BR> RADIO _RELAX is OFF by default and has been in ALL BBB
and RPi2 compiles. This command</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif>
previously required a menuselect change and recompile to enable. It is now added
as a runtime</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> option in the simpleusb.conf and
usbradio.conf files.</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif>
IMPORTANT NOTE - this command should be used with caution and NEVER used
indiscriminately.</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> It loosens the DTMF decoding
requirements but also can cause voice "falsing" which can severely</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif>
effect the audio. The "falsing" causes muting that sounds like dropouts. In
99.9% of cases you do<BR> not need to enable this</FONT><FONT
face=Tahoma,sans-serif> command. Proper pre/de-emphasis and level settings solve
most all DTMF <BR> problems and should always be the first thing
tried. I have run with this off in all the time I have<BR> used
Allstar and never had a problem. In all but one case so far, that I know of,
using the<BR> BBB/RPi2 images DTMF issues have been solved with
proper settings. So be aware that this<BR> command can potentially
cause as many problems as it might solve. <BR><BR></FONT><FONT
face=Tahoma,sans-serif></FONT><FONT face=Tahoma,sans-serif></FONT><FONT
face=Tahoma,sans-serif> New chan_simpleusb.c changes:</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> - Added code to resolve annoying variable
transmitted audio delay</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif> This
has plagued simpleusb on all platforms since it was added to the ACID code. It
is more prevalent<BR> on the small</FONT><FONT
face=Tahoma,sans-serif> boards and especially the RPi2. The symptoms
generally only appear when Allstar<BR> is used on a</FONT><FONT
face=Tahoma,sans-serif> repeater. A user would hear their own voice for a few
syllables or a word after<BR> unkeying. This</FONT><FONT
face=Tahoma,sans-serif> update totally fixes the problem and the delay through
the system is now constant<BR> and short in </FONT><FONT
face=Tahoma,sans-serif>length.</FONT><FONT face=Tahoma,sans-serif>
</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif><BR> The delay elimination update has been in
beta testing on several repeaters for the last month <BR> with
excellent results.<BR><BR></FONT><FONT face=Tahoma,sans-serif>Other
updates<BR><BR> - Cleaned up all compiler warnings. in app_rpt.c and
chan_simpleusb both now compile cleanly,</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif> no
warnings at all. Added flags to allow compiles using new gcc for new and
old versions of the</FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> code</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif> - The weather scripts are updated to "work around"
the loss of Google voice.<BR><BR> - With the kernel update the BBB now has
GPIO capability for external control like the RPi2. <BR></FONT><FONT
face=Tahoma,sans-serif></FONT><FONT face=Tahoma,sans-serif><BR></FONT><FONT
face=Tahoma,sans-serif>While these are the significant changes in 1.3 there are
other programs and scripts added and updated.</FONT><FONT
face=Tahoma,sans-serif><BR></FONT><FONT face=Tahoma,sans-serif>There may be more
options added and further updates before the release date and a complete
listing<BR>will be available at that time.</FONT><BR><BR><FONT
face=Tahoma,sans-serif>Many thanks to Dave, KB4FXC and Chris, W0ANM for these
updates.<BR><BR>I am hoping we can move this to distribution by the end of
January early February time frame.<BR><BR>73, Doug
<BR>WA3DSP<BR><BR></FONT><BR></DIV></DIV></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR><BR>arm-allstar
mailing
list<BR>arm-allstar@hamvoip.org<BR>http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<BR><BR>Visit
the BBB and RPi2 web page - http://hamvoip.org</BODY></HTML>