[App_rpt-users] Connecting several sites together on a hub using link radios
Stephen - K1LNX
k1lnx at k1lnx.net
Fri Aug 26 13:38:46 UTC 2016
>
> I'm not sure what kind of controllers you've got??
No controllers on 3 out of 5 sadly.. 4 out of 5 of these are DR-1X's, and
the fifth is a GE Master II with a ID-O-Matic IV board. My repeater (also a
DR-1X) will have an SCOM 7330 on it, but has not been brought online yet.
On Fri, Aug 26, 2016 at 8:18 AM, David McGough <kb4fxc at inttek.net> wrote:
>
> Stephen,
>
> Yes, eliminating the Repeater TX hang time, one way or another, is the
> best solution....I'm not sure what kind of controllers you've got?? One
> possibility would be to have a Repeater transmitted PL tone directly
> follow the Repeater COS....Then, the simplex link radios would look for
> that PL tone. If the Repeater's RX COS isn't active, no PL tone
> transmitted, and no ping-pong. Then, you could still have a Repeater
> generated TX carrier hang time.
>
> The problem with rxondelay is that it'll force users to slow down their
> chatter, since the first parts of words during the delay period will get
> chopped off. If TX hang times are long, the rxondelay will be long...Not
> ideal.
>
>
> 73, David KB4FXC
>
>
>
> On Fri, 26 Aug 2016, Stephen - K1LNX wrote:
>
> > David,
> > Yes, this is the exact scenario. I think it can be solved by
> > eliminating the hangtime from propagating across the hub alltogether, but
> > not sure what the best approach is.
> >
> > Thanks,
> > Stephen
> > K1LNX
> >
> > On Fri, Aug 26, 2016 at 6:58 AM, David McGough <kb4fxc at inttek.net>
> wrote:
> >
> > >
> > > Hi Stephen,
> > >
> > > I guess, in your scenario, the ping-pong is generated from repeater TX
> > > hang times? So, something like:
> > >
> > > 1) User keys up "Repeater A" directly.
> > >
> > > 2) Simplex AllStar link "Radio 1" hears "Repeater A" TX audio and/or
> hang
> > > time and repeats to the hub.
> > >
> > > 3) Simple AllStar link "Radio 2" connected to same hub keys and brings
> up
> > > "Repeater B"
> > >
> > > 4) "Repeater A" unkeys, "Radio 1" COS goes inactive, "Radio 2" unkeys.
> > >
> > > 5) "Radio 2" hears "Repeater B" TX audio and/or hang time, keys hub,
> > > "Radio 1" and "Repeater A".
> > >
> > > 6) "Repeater B" unkeys, "Radio 2" COS goes inactive, "Radio 1" unkeys.
> > >
> > > 7) Goto 2 and repeat forever
> > >
> > >
> > > 73, David KB4FXC
> > >
> > >
> > >
> > > On Fri, 26 Aug 2016, Stephen - K1LNX wrote:
> > >
> > > > Hi guys... I am in the midst of deploying a 5 site system. All of the
> > > sites
> > > > with the exception of my own will be using link radios sitting on the
> > > > repeater pair, some sites do not have internet access so this is the
> only
> > > > option. Each node will be permalinked to our hub.
> > > >
> > > > What we discovered when we brought site number 3 online was the
> dreaded
> > > > "ping-pong" effect, and I did some digging and found out about the
> > > > rxondelay parameter, that seems to be the place to start with this.
> > > >
> > > > The other option we are considering is dropping the hang time off
> each
> > > > repeater and using app_rpt to do hang time and courtesy tones instead
> > > > (duplex = 1 instead of 0) but not sure that would work real well or
> be
> > > > optimal.
> > > >
> > > > Anyone have any experience with a setup like this that can offer some
> > > > advice? This is my first foray into this unfortunately, I've always
> just
> > > > interfaced the radio or repeater directly to app_rpt in the past or
> > > through
> > > > a controller so it's been a bit of a challenge.
> > > >
> > > > 73
> > > > Stephen
> > > > K1LNX
> > > >
> > >
> > >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20160826/f80b6bc1/attachment.html>
More information about the App_rpt-users
mailing list