[App_rpt-users] local telemetry
kh2d at bellsouth.net
Tue Feb 21 14:10:28 EST 2012
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.
> 28325 (A)
> 8676 (I)
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
More information about the App_rpt-users