[App_rpt-users] Transmitter steering

Brett Friermood brett.friermood at gmail.com
Tue Jul 21 16:01:18 UTC 2015


Given that the repeaters don't overlap you might benefit to setup simulcast
even though you're not syncing the transmitters. Anywhere you do have
overlap, like on the ridge tops, you're going to get out of sync signals
but I'm guessing that is a low percentage of coverage area. If you could
get one transmitter to capture your receiver, even just a little, you
should have mostly intelligible reception at those locations. Maybe walking
down from the ridge top a little ways.

Alternatively, do you have a location that can cover all the ridge tops?
Use a different transmit frequency to cover those spots that the
psuedo-simulcast causes interference at. Instead of the many different
channels you would end up programming and using with separate input tones,
you would now have only two, the main channel and the secondary transmitter
channel.

The receiver at this alternate site could be the same frequency and voted,
or just have transmit only since the other voted receivers would be
providing coverage.

--------

Those commands in your linked message look to be easily scripted from an
external control script. I haven't played with the RTCM's yet but can you
somehow see which site is being voted from the command line? Doesn't AllMon
do this? If so it should be relatively easy to watch the voted sites and
pick the appropriate transmitter. Might need a little special logic
built-in.

Brett KQ9N

On Mon, Jul 20, 2015 at 3:46 PM, Tom Hayward <tom at tomh.us> wrote:

> On Mon, Jul 20, 2015 at 12:54 PM, David McGough <kb4fxc at inttek.net> wrote:
> >
> > Hi Tom,
> >
> > AllStar nor RTCM's implement this functionality, as far as I know.
>
> It's not a terribly complex operation, just activating a single
> transmitter instead of many. Maybe this configuration could be
> adapted:
> http://ohnosec.org/pipermail/app_rpt-users/2015-April/011662.html
>
> > Honestly, I'm not sure that this type of system would be a good fit for a
> > ham radio repeater system--all it would take is one mischievous
> Kerchunker
> > to greatly impair the systems operation (by "locking out" all but the
> site
> > the Kerchunker is closest to). The Kerchunker might not even realize that
> > Emergency Comms were in progress on a distant repeater, which they
> > couldn't hear.
> >
> > Just being curious, what kind of repeaters are you currently running, and
> > how many, over how big an area?
>
> We have a few homebrew repeaters with S-COM 7330 controllers. The
> transmitters and receivers are various from Motorola and Kenwood. We
> would standardize on just one model before implementing voting. We'd
> probably eliminate the 7330 too, in favor of just RTCMs and app_rpt.
>
> We'd like to serve a ring around Mt. Rainier. The area is mostly
> wilderness with no inhabitance and deep valleys. There would be almost
> no overlap between transmitters--just at the tops of ridges.
>
> Many similar systems in the region use a different tone for each
> repeater. We could do it this way, but I'd prefer to let a computer
> make the decision about which site is best.
>
> Tom KD7LXL
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down
> to the bottom of the page. Enter your email address and press the
> "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20150721/a2b7b68f/attachment.html>


More information about the App_rpt-users mailing list