[arm-allstar] Telemetry Channels?

[Bryan St Clair]

I would also suggest you not connect to WINS less than 5 mins before the
nets.  Almost everyone does, and that's why you hear so many messages.

Connect 10 mins before and telemetry will timeout before the mass gets on.

Just a suggestion.

Bryan
K6CBR

On Sat, Aug 1, 2020, 13:36 "David McGough via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

>
> Hi Dave,
>
> The AllStar telemetry code currently doesn't have the capability to
> differentiate between local and remote nodes, unfortunately.
>
> Setting telemdefault=0 (or 2) is currently the best option.
>
> Resolving telemetry issues (like this one) are on the ToDo list.
>
> 73, David KB4FXC
>
>
>
> On Sat, 1 Aug 2020, "David Andrzejewski via ARM-allstar" wrote:
>
> > The wiki page https://wiki.allstarlink.org/wiki/Telemetry refers to
> several telemetry "channels" that can supposedly be
> individually-controlled, but doesn't seem to tell you how to do it.
>
> What I'm trying to accomplish is disable all "foreign" telemetry.  It's
> annoying when I connect to, say, the WIN system prior to a net and for a
> couple minutes have to listen to all the other nodes connecting.  I want
> to hear an acknowledgement that /my/ node connected, but that's it.  The
> closest I've come is telemdefault=2.
>
> - Dave/AD8G
>
> _______________________________________________
>
> 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
>