[arm-allstar] Echolink telemetry

[Doug Crompton]

John,

  OK it is ashame that they don't work separately as in some cases you might want to suppress the allstar connect/disconnect messages while retaining Echolink's. Thanks for testing.

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


Date: Wed, 13 Aug 2014 13:36:34 -0700
From: kd5u at ymail.com
Subject: Re: Echolink telemetry
To: doug at crompton.com
CC: arm-allstar at hamvoip.org


I tested both variables and the only way I was able to get the echolink connect messages all the time was with telemdefault=1. 
thanks again!John KD5U
        From: Doug Crompton <doug at crompton.com>
 To: John S <kd5u at ymail.com> 
Cc: "arm-allstar at hamvoip.org" <arm-allstar at hamvoip.org> 
 Sent: Wednesday, August 13, 2014 2:18 PM
 Subject: RE: Echolink telemetry
   
John,  Good to hear that fixed it. If you ever get the the chance I am curious if telemdefault=2 and setting the echolinktelem=1  gives you echolink messages at all times.73 DougWA3DSPhttp://www.crompton.com/hamradio

Date: Wed, 13 Aug 2014 12:10:53 -0700From: kd5u at ymail.comSubject: Re: Echolink telemetryTo: doug at crompton.comCC: arm-allstar at hamvoip.orgDoug, thank you for the quick reply and suggestions.I finally got a chance to test it this morning.  You nailed it. That's what the difference was between my original installation and this one. telemdefault=1 changed the behavior as you described.  If it get's too noisy with connects / disconnects I can go back. thanks again!John KD5U        From: Doug Crompton
 <doug at crompton.com> To: John S <kd5u at ymail.com> Cc: "arm-allstar at hamvoip.org" <arm-allstar at hamvoip.org>  Sent: Monday, August 11, 2014 9:41 AM Subject: Echolink telemetry   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 aretelemdefault=2  and holdofftelem=1The 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/103Now 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=1http://ohnosec.org/drupal/node/107Lets 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 DougWA3DSPhttp://www.crompton.com/hamradioDate: Mon, 11 Aug 2014 04:00:45 -0700From: kd5u at ymail.comSubject: Re: Raspberry Pi running Allstar
 NodeTo: doug at crompton.comHello 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/20140813/cee991aa/attachment-0001.html>