[arm-allstar] Update version 1.3 BBB/RPi2 now in testing

Pierre Martel petem001 at gmail.com
Sun Jan 10 17:57:24 EST 2016


And by the way great job!!!


2016-01-10 17:57 GMT-05:00 Pierre Martel <petem001 at gmail.com>:

> Will the hardware headers will be available with that release ?? (the i/o
> pin on both the BBB and rpi) so that we could use a simple dongle without
> mods and input/and outpu connection could be driven directly to the embeded
> device?
>
>
>
> 2016-01-09 14:44 GMT-05:00 Doug Crompton <doug at crompton.com>:
>
>> 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 -
>>
>> Both the BBB and RPi2 have been updated to 4.x kernels and all associated
>> software has been updated.
>>
>> New app_rpt.c changes:
>>
>>  - Removed obsolete uchameleon code (about 2500 lines).
>>
>>       This is obsolete hardware.
>>
>>  - Added COS timeout, with COS flap suppression (new rx_timeout,
>> rx_cosflap  rpt.conf parameters)
>>
>>       This is an attempt at eliminating single node hangups of connected
>> networks. Often a single node,
>>       due to radio or interface failure, can cause a COS hangup tying up
>> an entire network. If the timeout
>>       is set COS is monitored and the indication of asserted COS to the
>> network is dropped if the time is
>>       exceeded. The COS timeout is set in the same way as a TX timeout.
>> The COS unasserted indication to
>>       the network will remain until the hardware COS is cleared. COSFLAP
>> can also be set and will attempt
>>       to catch conditions where a squelch is "flapping" by not resetting
>> the timer during this condition and
>>       allowing the timeout period to proceed.
>>
>>  - Added telemetry gain levels (new telemnomdb rpt.conf parameter)
>>
>>      This will allow a level adjustment of telemetry (connect,
>> disconnect, etc.) messages. The level
>>      change is in dB like the Echolink level adjustments. This will
>> eliminate the need to change the
>>      level of audio files.
>>
>>  - Added telemetry ducking (AKA: Allison ducking) (new telemduckdb
>> rpt.conf parameter)
>>
>>     This optionally reduces telemetry levels when a voice signal is
>> present.
>>
>>  - Changed tx timeout variable name from totime to tx_timeout (the old
>> variable is deprecated,
>>     but still works after printing a console warning)
>>
>>     This was done to avoid the confusion between TX and RX timeouts. TX
>> timeout is applied only
>>     to the local transmitter. It is often in addition to a TX timeout
>> that is set at a longer time in the
>>     radio itself ensuring double protection for a hung transmitter. The
>> RX timeout, added in this
>>     update, would normally be set slightly longer than the TX timeout to
>> offer the same protection
>>     to the network from a COS hardware failure.
>>
>> New core Asterisk changes:
>>
>> - Removed need to recompile to enable/disable RADIO_RELAX
>>
>>    This command when on reduces the DTMF decode requirements but can also
>> cause DTMF "Falsing"
>>    RADIO _RELAX is OFF by default and has been in ALL BBB and RPi2
>> compiles.  This command
>>    previously required a menuselect change and recompile to enable. It is
>> now added as a runtime
>>    option in the simpleusb.conf and usbradio.conf files.
>>
>>    IMPORTANT NOTE - this command should be used with caution and NEVER
>> used indiscriminately.
>>    It loosens the  DTMF decoding requirements but also can cause voice
>> "falsing" which can severely
>>    effect the audio. The "falsing" causes muting that sounds like
>> dropouts. In 99.9% of cases you do
>>    not need to enable this command. Proper pre/de-emphasis and level
>> settings solve most all DTMF
>>    problems and should always be the first thing tried. I have run with
>> this off in all the time I have
>>    used Allstar and never had a problem. In all but one case so far, that
>> I know of, using the
>>    BBB/RPi2 images DTMF issues have been solved with proper settings. So
>> be aware that this
>>    command can potentially cause as many problems as it might solve.
>>
>>  New chan_simpleusb.c changes:
>>
>>  - Added code to resolve annoying variable transmitted audio delay
>>
>>    This has plagued simpleusb on all platforms since it was added to the
>> ACID code. It is more prevalent
>>    on the small boards and especially the RPi2.  The symptoms generally
>> only appear when Allstar
>>    is used on a repeater. A user would hear their own voice for a few
>> syllables or a word after
>>    unkeying. This update totally fixes the problem and the delay through
>> the system is now constant
>>    and short in length.
>>
>>    The delay elimination update has been in beta testing on several
>> repeaters for the last month
>>    with excellent results.
>>
>> Other updates
>>
>>  - Cleaned up all compiler warnings. in app_rpt.c and chan_simpleusb both
>> now compile cleanly,
>>    no warnings at all.  Added flags to allow compiles using new gcc for
>> new and old versions of the
>>    code
>>
>>  - The weather scripts are updated to "work around" the loss of Google
>> voice.
>>
>>  - With the kernel update the BBB now has GPIO capability for external
>> control like the RPi2.
>>
>> While these are the significant changes in 1.3 there are other programs
>> and scripts added and updated.
>> There may be more options added and further updates before the release
>> date and a complete listing
>> will be available at that time.
>>
>> Many thanks to Dave, KB4FXC and Chris, W0ANM for these updates.
>>
>> I am hoping we can move this to distribution by the end of January early
>> February time frame.
>>
>> 73, Doug
>> WA3DSP
>>
>>
>>
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2 web page - http://hamvoip.org
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160110/634faceb/attachment-0001.html>


More information about the arm-allstar mailing list