I think what he is asking is whether the weather the Rx and Tx streams
of the RTCM can be used on different nodes. In other words, at a
specific site with only a single RTCM, can the transmitter be part of
node A while the receiver is part of node B.

Looking at his message
again that may not actually be what he is looking for, though.

Steve, as long as there is only one Asterisk node involved, meaning a
single repeater "system" although using multiple bands, a single RTCM
at a site will work. If configured this way all the 6m and 2m
receivers would link back and be voted into a single stream which
would then be sent out to all the 6m and 2m transmitters at the
different sites. When used like this as far as app_rpt is concerned it
behaves no differently than having a voted/simulcast system on a
single band.

Brett KQ9N

On Sat, Feb 1, 2014 at 6:20 PM, Tim Sawyer <tim.sawyer@mac.com> wrote:
> Of course each RTCM can transmit and receive. The receive only sites don't have the transmit parameter in voter.conf. But you seem to be asking a different question. If so, could you restate it?
> --
> Tim
> :wq
>
> On Feb 1, 2014, at 10:23 AM, Steve Wright <stevewrightnz@gmail.com> wrote:
>
>> Gurus!
>>
>> Can I operate arbitrary recievers and transmitters with the voter boards, and separate them in config at chan_voter?
>>
>> Background: Our terrain does not lend itself to a few high-sited duplexed repeaters (or rather we are not inclined to pay for it), so we are taking the non-duplexed distributed approach of locating recievers and transmitters at various sites on a non-contending basis and GPS locking them all together.  It seems to us that if we have a hole in some coverage, that it would easy (read - cheap) to throw another GM300 at the problem..
>>
>> That is, site A has either a 6M transmitter and other 2M receiver, or otherwise non-contending combinations, and the corresponding pair for each repeater receiver or transmitter is actually located on a nearby site linked with 802.11an.
>>
>> SO!  It looks at first glance that I must use a VOTER board for each rx AND each tx, but perhaps I can use some clever config and halve the number of VOTER boards I use.
>>
>>
>> Many thanks,
>> Steve
>>
>>
>> --
>> Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers
>> +64 21 040 5067
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users@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.
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users@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.


------------------------------

Message: 6
Date: Sat, 1 Feb 2014 21:54:41 -0500
From: Lu Vencl <vencl@att.net>
To: "<app_rpt-users@ohnosec.org>" <app_rpt-users@ohnosec.org>
Subject: [App_rpt-users] MSF 5000 URI interface
Message-ID: <D9035249-1E4C-4EF8-AB58-75B4784784B4@att.net>
Content-Type: text/plain;       charset=us-ascii

Anyone have the diagram for URI interface to an MSF 5000?

Sent from my iPhone, Lu Vencl


------------------------------

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users


End of App_rpt-users Digest, Vol 60, Issue 3
********************************************