What is the setup vis a vis Telemetry

We're expanding out network, and adding more repeaters.

7 nodes:

  • 2 with hats (1 that connects by RF to a set of linked Repeaters (which are linked by RF themselves), the other is local only.
  • 2 nodes with dvswitches, 1 of which is connected to dmr tied to 2 repeaters, the other is for connecting to different nets.
  • 2 nodes for connecting/spares
  • 1 node connected directly to the Repeater

I just haven't found the correct settings. We are getting complaints that people are hearing telemetry

The instructions are confusing, as it say duplex = 2 best for repeaters, but it gets telemetry and duplex = 0 no telemetry and

telemdefault = 2 ; 0 = telemetry output off
; 1 = telemetry output on (default = 1)
; 2 = timed telemetry output on command execution and for a short time thereafter.

Three scenario's:

  1. Allstar node no hat
  2. Allstar node with hat
  3. Allstar node with direct connection to repeater

What levers for node-main and (node-number)node-mail should I have for a) optimal performance of node (i.e. repeaters) and Telemetry not going through the Allstar side of the house.

What are these "hats"? Do you mean a SHARI PiHat?

If you are "interfacing" the node to the repeater via RF instead of interfacing directly with a sound card, then the node is going to "hear" everything that any other RF user would hear.

In order for this to work properly, your repeater would have to drop CTCSS during telemetry so that the squelch on node's interface does not open for said telemetry.

If this is how it is set up, then there is nothing you can do in software on the ASL side about it.

duplex = 2 is only for full duplex setups (i.e. direct connection via sound card).

USBRadio hat, but the same concept...

On the Node/Repeater via RF:
I realize that if the Repeater itself which is circa 1980 gives a station ID or whatever, we're stuck. To get around that issue, if connect to a net which is not ours, we just disconnect that Repeater system from our ALLSTAR net.

On the Node/Repeater directly connected to via usb to the Repeater, that is set at duplex =2 as I said telemdefault = 2.

I'm really only interested in preventing telemetry coming through the Allstar connections...

You need to be more specific than "telemetry". What precisely are you looking to suppress? For example, telemetry "beeps" are local only. Readout on joining and departing nodes are controlled per connection/channel type. See Telemetry Messages - AllStarLink Manual. Other things, such as if someone does an rpt playback which is global has no other way of being suppressed.

I changed telemdefault to 0, let's see if that solves the issue (was 2)