[arm-allstar] AllStar on Local Server

dan at ozment.net dan at ozment.net
Tue Feb 21 15:13:22 EST 2017


Thanks for your comments, Buddy. Unfortunately, I can't put the Pi at 
the repeater site because I don't have internet there.  I understand I 
need to keep duplex=1.  Will do some more testing tonight.

73
Dan

On 2017-02-21 13:55, "Buddy Brannan via arm-allstar" wrote:
> Hi,
> 
> This would be the way to implement if you really really really don't
> have any other choice. If you can't hang the All Star pi off a remote
> port on the controller, or better yet, replace your controller with
> the All Star Pi, this wold be how to handle it.
> 
> If you have your node radio set to decode the PL tone, then COS should
> only operate when squelch opens, so the repeater's tail shouldn't keep
> the node keyed, assuming the transmission of tone stops when the
> repeater user unkeys. (If tone is transmitted the whole time, even
> after the user unkeys, such that you'll also get courtesy tones and
> other things, then really, don't set up your node this way.)
> 
> You'd only use duplex=2 if you're using the Pi as a repeater
> controller. Duplex=2 means that you're full duplex, so the node can
> transmit while it's also receiving. You don't want this. If you've got
> the Pi hanging off a port on the controller, you'd use duplex=0 (which
> has no hang time and no ID or telemetry sent anywhere at all). Likely
> you'll want duplex=1 so that you transmit an ID as required. Blank out
> any courtesy tones, you don't want your node sending those over the
> repeater pair.
> 
> --
> Buddy Brannan, KB5ELV - Erie, PA
> Phone: 814-860-3194
> Mobile: 814-431-0962
> Email: buddy at brannan.name
> 
> 
> 
> 


More information about the arm-allstar mailing list