[arm-allstar] telemetry control

[larry]

Patrick,

My Apology ... wasn't trying to start an Issue but I will say...

I don't understand the need to broadcast some others stations connect 
and disconnect messages.

*Its like I want to keep an eye on who is using who's node - and from 
where.*  Not only that but if you happened to miss hearing a connect 
message, you wouldn't know who remains connected even on your own nodes, 
unless you check it by some other means.  If you want to monitor just 
certain node connections, a small script will pick out an array of 
chosen node numbers from the overall Allstar Status Database and list 
only their connections, ignoring the rest of the worlds nodes.

Larry - N7FM


On 1/27/22 5:51 PM, "Patrick Perdue via ARM-allstar" wrote:
> Yep, I knew something like this would happen if I brought it up.
>
> I get where everyone is coming from here, but as someone who runs a 
> multi-mode, multi-node system, and not always near a dashboard, it is 
> sometimes good to have that info. Also note that I don't use the 
> standard Allison voice, preferring something much faster, I.E. about 
> 550 WPM, and also use call signs instead of node numbers, so telemetry 
> takes a lot less time to transmit. At the same time, though, this is 
> really, really annoying during large nets.
>
> I personally kept my telemetry off almost entirely on RF nodes, and on 
> when using a radioless/full duplex system, where it wouldn't slow 
> anything down if it's activated. I would sure never want that sort of 
> output on a repeater if I had one, but I keep hearing this over and 
> over again since the December update on my system. When is telemetry 
> going to work again? So, I'm just passing it on. There are people who 
> still prefer the old way of announcing things, even if the majority 
> don't.
>
>
> On 1/27/2022 8:27 PM, "Larry via ARM-allstar" wrote:
>> David,
>>
>> My Feeling you do enough already ...why waste your time on something 
>> like that. You've got it right already.
>>
>> I don't see why it matters what "neighboring nodes" do. That is like 
>> asking to broadcast who is monitoring RF links on a system. We sure 
>> don't need to broadcast all that garbage even if we knew who was 
>> lurking about. If a station wants to talk fine identify yourself and 
>> talk. Otherwise who cares who comes and goes.
>>
>> If he means he wants his own system to broadcast connects/disconnects 
>> from his own nodes out his HUB ... build a script to monitor all the 
>> coming and going from the different LOG files on his own network and 
>> announce it some where locally but certainly not to the entire 
>> network if his node is connected outbound.
>>
>> Larry - N7FM
>>
>>
>> On 1/27/22 2:37 PM, "David McGough via ARM-allstar" wrote:
>>> Okay, I'm going to have to investigate a solution.  The issue is that
>>> telemetry from the "neighbor node" indicating the connection change
>>> probably isn't being passed to your hub, no matter how telemenabled 
>>> is set
>>> at your end. So, you don't know a node has connected to a neighbor, 
>>> other
>>> than by monitoring linkslist data, as seen in Supermon, etc. Note 
>>> that the
>>> linkslist data is updated.
>> _______________________________________________
>>
>> ARM-allstar mailing list
>> ARM-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org