[arm-allstar] Telemetry Request

[David McGough]

Hi Matt,

Yeah, telemetry handling is another area that needs overhaul. Doug & I
have already been discussing this at length. One feature that's in the
works is carefully separating different types of telemetry into clearly
organized groupings, which may be handled in different ways.  An example
of this is playback command, which gets undesirably "muted" in certain
telemetry modes.

We're considering developing a proposed plan for telemetry mappings and
posting this info for review and comments before writing/changing code. 
There are lots of users out there who have specific needs/desires. 
This will hopefully help accommodate everyone.


73, David KB4FXC


On Sun, 14 Jul 2019, "M Lech via ARM-allstar" wrote:

> Hi Doug,
> 
> A while back I'd inquired of adding an option to the telemetry settings. To
> reiterate in short, we'd be thrilled to have a third Telemetry option. It
> would send only Function Complete (beep-beep) for any Connect or
> Disconnect. Right now, we run our RTCM hub with telemetry set as 2 ("Only
> your telemetry actions, then mutes in 1 minute"). With telemetry = 1, we
> were bombarded by connect and disconnect verbosity. All we want are simple
> beeps to tell us when someone connects or disconnects. We can easily check
> Supermon for more details as needed. Right now, we don't hear anything when
> someone connects and we'd like some indication so we don't seem to ignore
> them. This would really help.
> 
> Is there a way I'm missing where this could be done without modifying the
> actual distro? If so, I'm all ears. Thanks guys!
> 
> 73,
> Matt W6KGB
> GRONK Radio
> _______________________________________________
> 
> 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 web page - http://hamvoip.org
>