[arm-allstar] RPi3 code 'Easter Egg'

Wed Mar 30 11:52:56 EST 2016

Hi Doug, 
I am using the alpha test version on a rPi3 private node with just a FOB with an earphone and a BF mic soldered directly. I love the allison ducking feature, I don't need to hear the loud telemetry noises when it's on the air.What I noticed though is that the very first time my node boots up, does an autoconnect to my hub, I am able to listen to allvoice traffic happening the hub but I am unable to transmit.I would then issue an "astres.sh" on my Pi3 then after it reconnects, I am then able to "talk" to the other stations.
That's it for now
73,
Lito KK6OOS
To: arm-allstar at hamvoip.org
Date: Tue, 29 Mar 2016 02:07:31 -0400
Subject: [arm-allstar] RPi3 code 'Easter Egg'
From: arm-allstar at hamvoip.org
CC: doug at crompton.com

I didn't mention it earlier but for those downloading the RPi2-3 beta code there is an Easter Egg in the form of a test of a portion of our code updates which will be in version 2.0. The code changes and available commands are listed below. 

The default boot mode is the V1.01 code updated for the RPi3. So other than the fact it runs on the RPi2 and 3 it is identical except for the updated simpleusb channel driver to the V1.0 RPi2 release of last year.

To enable the alpha-test version, see the "safe_asterisk" command in the file /usr/local/etc/rc.allstar ...Comment out: "/usr/bin/safe_asterisk" and uncomment the line: "/usr/local/hamvoip-alpha-test/sbin/safe_asterisk" Then reboot the system.

The new code -should- be stable, but remember this is beta code at this point!

If you need to switch back to the original stable Asterisk release code, it's as
simple as reversing the above change and rebooting.

Remember this is just a portion of the code changes which will be in our 2.0 release. If you decide to try this please report back any issues you may fine and if you have any questions don't hesitate to ask.

--------------------------------------------------------------------------------------------------------------------
New app_rpt.c changes:

- Removed obsolete uchameleon code (about 2500 lines).

This is obsolete hardware.

app_rpt.conf

 These added commands are on a per node basis and can be added in each node assignment.

Note that in this test mode these commands will have to be added to the appropriate config file.

- 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.

Default rx_timeout is 5 minutes. This should be set to just longer than the maximum expected transmit time into your node. This is typically less than 3 minutes as this is a common repeater timeout value.

- 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.

Note these are independent levels not additive. Default telemnomdb is 0 and telemdduckdb is -6

- 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. 

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 dtmf_relax=[0|1] in the simpleusb.conf and usbradio.conf files, for a given interface stanza.

DO NOT set this to on unless you absolutely need it. Setting  your levels and deemphasis correctly almost always solves the problem of not decoding DTMF. Setting this to on can also cause audio holes due to voice falsing. The default is off if you don't define it. 

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.

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

73 Doug
WA3DSP
http://www.crompton.com/hamradio

_______________________________________________

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/20160330/3750f8c4/attachment-0001.html>