[App_rpt-users] local telemetry

Jim Kehler kh2d at bellsouth.net
Wed Feb 22 12:56:06 EST 2012


That works with "status" commands, i.e.,

  *  1 - Force ID (global)
  *  2 - Give Time of Day (global)
  *  3 - Give software Version (global)
  *  4 - Give GPS location info
  *  5 - Last (dtmf) user
  *  11 - Force ID (local only)
  *  12 - Give Time of Day (local only)

because there are two commands defined for the time/ID functions (local 
or global).

But the question remains how to do that with "ilink" commands, which are 
what do
the standard "70" and "73" DTMF commands. There don't seem to be different
local/global ilink commands for "system status" and "full system status".

  *  5 - System status
  *  15 - Full system status (all nodes)

Maybe there's a way to "turn off" the propagation before the command and 
turn it
back on after it's done? It would be nice to be able to get a full 
system status on
the local node without waking everybody up that's connected.

73, Jim KH2D



On 2/22/2012 8:24 AM, Bill South wrote:
> Check the status values in your "functions" stanza of rpt.conf.  If 
> your "70" shows a 2 digit number beginning with a "1"  it will 
> propagate locally only, a single digit means it propagates everywhere; 
> i.e.
>
> my "80" is set as
>
> 80=status,11
>
> to propagate my ID locally
>
> but I created an "84" to propagate my ID everywhere
>
> 84=status,1
>
>   This is stated (somewhere) in the rpt.conf documentation
>
> 73, Bill, N4SV
>
> --- On *Tue, 2/21/12, Jim Kehler /<kh2d at bellsouth.net>/* wrote:
>
>
>     From: Jim Kehler <kh2d at bellsouth.net>
>     Subject: Re: [App_rpt-users] local telemetry
>     To: app_rpt-users at ohnosec.org
>     Date: Tuesday, February 21, 2012, 7:10 PM
>
>     Node stats (70) and full system status (73) announcements
>     propagate to
>     other connected nodes.
>     I can only go three nodes deep, but if I issue those commands on
>     any of
>     the three, they all
>     get the announcement.
>
>     I just checked, the time doesn't seem to do that. Which is good
>     because
>     it might not be the same
>     time there as it is here :-)
>
>     73, Jim KH2D
>
>
>
>     On 2/21/2012 1:03 PM, Stephen Liggett wrote:
>     > Maybe I am loosing my mind (you know how it gets when you are
>     working on a project "too long" at one stretch).
>     >
>     > Anyway, last night I connected via my Mac to the WAN via 2125 to
>     listen, using my web transceiver designated as W3RX.
>     >
>     > I then went to my HT and via the repeater, brought up that same
>     AllStar node 2125, using the repeater's node W3YT (28325).
>     >
>     > All was well. I then hit the DTMF on the HT for a status report,
>     which I assumed would send the status by LOCAL voice telemetry to
>     the repeater node, so those listening could tell who we were
>     connected to. To my surprise, I heard the telemetry message on the
>     repeater AND on my web transceiver connected to the WAN. That does
>     not seem right. I know that connect and disconnect telemetry is
>     heard at the distant node, but I assumed that other telemetry
>     (like status, or time) would not go further than local output to
>     the repeater.
>     >
>     > Like I said, I could have been in a dazed state, but I did it
>     twice with the same result. Is this supposed to happen? BTW, I use
>     the AllStar/URI as a remote base input to a RC-1000v repeater
>     controller (ie, I don't use AllStar as the controller as of now).
>     Not sure if that matters. I just don't want the local telemetry,
>     including some custom stuff that I have programmed, to push out
>     distantly.
>     >
>     > steve
>     > W3RX
>     > 28325 (A)
>     > 8676 (I)
>     > 86768(E)
>     >
>     >
>     > _______________________________________________
>     > App_rpt-users mailing list
>     > App_rpt-users at ohnosec.org </mc/compose?to=App_rpt-users at ohnosec.org>
>     > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>     >
>     _______________________________________________
>     App_rpt-users mailing list
>     App_rpt-users at ohnosec.org </mc/compose?to=App_rpt-users at ohnosec.org>
>     http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20120222/921a6313/attachment.html>


More information about the App_rpt-users mailing list