[arm-allstar] Echolink telemetry

[Doug Crompton]

John,

  Congratulations on getting your BBB up and running.

I think I can answer your question about echolink messages. The BBB image is distributed with two commands that are set differently then many might be use to. They are

telemdefault=2  and holdofftelem=1

The telemdefault=2 means that you will only hear connect/disconnect messages when YOU make them and for a short time thereafter. This avoids a constant stream of messages when you are connected to a hub with many stations constantly connecting and disconnecting but it always plays your originated connects/disconnects. If you want to hear everything set it to 1.

The holdofftelem=1 just means it will not announce the connect/disconnect until both you and any other node your are connected to is idle.

Definitions can be found at -

 http://ohnosec.org/drupal/node/110

 http://ohnosec.org/drupal/node/103

Now to your question. There is a similar command for echolink and my suspicion is that it defaults to the same setting as telemdefault if it is not set. The command is -

echolinkdefault  and it has the same definitions as telemdefault.  Set it to echolinkdefault=1 and see if that solves the problem OR if you want to hear everything (allstar and echolink at all times) just set telemdefault=1

http://ohnosec.org/drupal/node/107

Lets me know if this solves your problem.

I am cc'ing this message to the arm-allstar list so others can benefit from it. 

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


Date: Mon, 11 Aug 2014 04:00:45 -0700
From: kd5u at ymail.com
Subject: Re: Raspberry Pi running Allstar Node
To: doug at crompton.com


Hello Doug, thanks again for your response a few months ago. 
Well I finally moved my allstar node to a BBB with your help. Works great.  Wow what great
 documentation.   Made the move smooth and easy. One of the things I love about ham radio is dedicated folks like yourself helping others achieve cool things. 
I did have one quirky thing I thought you might have some ideas on. 
The node works great with one exception.  Inbound echolink connections are not announced unless a previous announcement has recently occurred.  Example:  An inbound echolink will connect and disconnect silently.  I can hit *70 for link status and hear links including an echolink connection if present. If an inbound echolink connection occurs shortly after *70 the echolink connection will be announced.  If waiting for a while it will be silent again.  echolink connections work otherwise.
It's like some process is not being set off when echolink connects / disconnects. But if it is present it will get announced. 
Any thoughts? 
Thanks again for all the great documentation and your dedication to this terrific hobby. John SawyerKD5U

        From: Doug Crompton <doug at crompton.com>
 To: John S <kd5u at ymail.com> 
 Sent: Friday, June 13, 2014 8:12 PM
 Subject: RE: Raspberry Pi running Allstar Node
   
John,  Unfortunately the Pi did not work out but I later went on to the BeagleBone Black and we now have two beta releases and we are about to make the first public release in a few days. I will be announcing it on the app_rpt site.  For now here is the web page which will change a little so make sure you reload it occasionally! Join the BBB mail list also when you get a chance. The link is on the web page.http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/73 DougWA3DSPhttp://www.crompton.com/hamradio
 		 	   		  

     		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140811/5bb12cac/attachment.html>