[App_rpt-users] App_rpt-users Digest, Vol 60, Issue 7

Brett Friermood brett.friermood at gmail.com
Mon Feb 3 20:13:20 UTC 2014


In that case I do not believe it is possible to only use a single RTCM
at a site that contains both a 6m RF device and 2m RF device. Because
they are 2 separate repeater systems each is a separate node in
Asterisk and an RTCM can only be associated with a single node.

Brett

On Mon, Feb 3, 2014 at 11:10 AM, Steve Wright <stevewrightnz at gmail.com> wrote:
> Scuse the top posting;
>
> There is a 2m voter simulcast system.  It can be expanded upon by adding
> more GPSDO transmitters, and more voting receivers - just as any voter
> simulcast system would be.
>
> And there is a 6m voter simulcast system.  It can be expanded upon by adding
> more GPSDO transmitters, and more voting receivers - just as any voter
> simulcast system would be.
>
> The 2m and 6m simulcast systems are NOT connected so they function as a
> cross-band talk-through repeater.
>
> The 2m node AND SEPARATELY the 6m node are independent repeaters in their
> own right.  To the ordinary joe ham radio operator, the only thing in common
> is that you can dial (via asterisk) one from the other in common use.
>
> The only confusing thing about the 2m and the 6m repeaters from the
> technical point of view as noted, is that one physically shares the others'
> site and controller.
>
> So, each, they are not simplex remote bases, but full simulcast repeater
> systems.
>
> Steve
>
>
> On Mon, Feb 3, 2014 at 2:30 PM, Brett Friermood <brett.friermood at gmail.com>
> wrote:
>>
>> The remote base way won't scale beyond two sites while still keeping
>> only a single RTCM per site and keeping the repeaters separate. As
>> soon as another transmitter on the other band is plugged in it will
>> transmit no matter what receiver is receiving.
>>
>> Yes, the terms can get a little confusing when you start messing with
>> non-standard configurations. I generally use the following:
>>
>> A site is a physical location on a map, usually holding a collection
>> of RF hardware, or otherwise defined as where an RTCM(s) sits.
>>
>> A node is a virtual resource existing only within the Asterisk
>> framework and is used to do things including linking to others.
>>
>> A repeater is an RF resource consisting of a transmitter and receiver,
>> which may involve different bands or locations (sites), but function
>> simultaneously.
>>
>> A system consists of multiple pieces of something. Adding links
>> between otherwise standalone repeaters creates a system. I would
>> define multiple sites using voted receivers and simulcast transmitters
>> as a voted/simulcast repeater system. The individual sites do not
>> necessarily contain a repeater because other parts of the system are
>> needed to function. The entire system, however, is a repeater.
>>
>> I understand what you are trying to do as far as the distributed sites
>> to provide the required coverage and reduce duplexer costs. The one
>> thing we have yet to pin you down on is whether the 2m repeater and 6m
>> repeater should exist separately on RF or if they are really just one
>> system? In other words, should a 2m only radio be able to talk to a 6m
>> only radio a) all the time, b) never, or c) only when linked?
>>
>> Brett KQ9N
>>
>> On Sun, Feb 2, 2014 at 6:13 PM, Steve Wright <stevewrightnz at gmail.com>
>> wrote:
>> >>
>> >> The first way to setup the unlinked configuration is to use four
>> >> RTCMs. These would then link back to two separate nodes. This would
>> >> allow the ability to link the two repeaters when needed/wanted. Of
>> >> course this is what you don't want because of excess RTCMs.
>> >
>> >
>> > Yes, exactly.
>> >
>> >
>> >>
>> >>
>> >> The "new" way that Mike (W5JR) [...] Cactus Intertie [..] uses this
>> >> configuration. [...] in-band repeaters [where] the receiver audio is
>> >> linked
>> >> to the rest of the [same band voting] system and not repeated through
>> >> the
>> >> local [non band] transmitter [that is part of an identical and linkable
>> >> node].
>> >>
>> >> [...] two nodes would need to be created. One node for the Site "A"
>> >> RTCM
>> >> and the second for
>> >> the Site "B" RTCM. Then link these through Asterisk. When the A
>> >> receiver picks up a signal the audio would be sent back and sent to
>> >> the B transmitter. Similarly any signal picked up by the B receiver
>> >> would be sent to the A transmitter. Both appearing independent of each
>> >> other.
>> >
>> >
>> > Yes indeedy!
>> >
>> >> Setting duplex=1 will not repeat the audio from receiver to [the same
>> >> site]
>> >> transmitter, but uses half duplex operation for simplex nodes.
>> >
>> >
>> > Thanks Brett, that's perfect!
>> >
>> > If we do this, will our split-site (but same-band) repeater still have
>> > talk-through?
>> >
>> > Also can I arbitrarily add other TX and RX sites to this "repeater"
>> > "node"?
>> >
>> > I add the "", because with split-site operation the definition of "node"
>> > is
>> > not particularly clear with respect to the site.
>> >
>> > So in summary, we are looking at multiple-site voted systems due to not
>> > having good access to one high site, and the few (expensive) high sites
>> > leave some pretty big holes anyway.  We are looking at using the
>> > split-tx/rx
>> > approach as above to avoid the expensive and complicated duplexing.
>> >
>> > Steve
>> >
>> >
>> > _______________________________________________
>> > 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.
>
>
>
>
> --
> Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers
> +64 21 040 5067



More information about the App_rpt-users mailing list