February 2014 - App_rpt-users - lists.keekles.org

Monitoring the Output & Injeting Weather to Specific RPTRs
by Bob - AF6D 03 Feb '14

03 Feb '14

Our three site voted/simulcast system has progressed nicely. We have three excellent locations with commanding coverage of the mountain recreational areas that we wish to service, plus general coverage of surrounding areas. Here's question #1 of 2. If an errant ham attempts to dial up our repeater in a hurry and fails but can get the output setup is it possible that we can monitor the output over the network and still hear him? I know that CHP in California does just this. #2, we are adding RC-210 controllers as unvoted controllers through which IRLP, weather and an earthquake monitor will be input regionally. We would like to output the FIPS code for the desert machine out over the desert machine only since it isn't relevant to the other RPTs. Can this be done? We just had our first severe weather advisory go out to all three regions and two of them weren't affected. Huge thanks in advance!

1 0

Co-located Split Site Repeaters
by Brett Friermood 03 Feb '14

03 Feb '14

On Sun, Feb 2, 2014 at 2:00 PM, Steve Wright <stevewrightnz(a)gmail.com> wrote: > Ok unless I have misread, we have two opposing opinions stated as fact. > > Anyone care to offer insight, quote sources or offer configs, or otherwise > generally assist in the scientific principle of distilling collective > opinion for fact? I'll take another shot at it. First, let's define a couple things: In one of your previous emails you specified Site "A" has a transmitter on 6 meter and a receiver on 2m. Site "B" is the opposite with a transmitter on 2 meter and a 6 meter receiver. Since you are using RTCMs you can do everything with one Asterisk/app_rpt server which can be located at either site, as long as there is an active network connection between all points. Ignoring anything Asterisk related, traditionally a system such as this will normally be configured in one of two ways. Either each repeater is individual, where 6m and 2m users are not able to talk to each other, or they are linked together, where a user transmitting on either the 2m or 6m input will be output on both bands. I did not see this explicitly specified in previous emails so I will cover both configurations below. If setup for the linked configuration, a single RTCM can be used at each site for a total of 2. The node configuration would consist of a single node number that uses both RTCMs as voting receivers and multicast transmitters. Only one receiver can actually receive anything due to different bands, but the voting process with handle that. Once the audio is voted it will then be sent out to both transmitters. 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. The "new" way that Mike (W5JR) brought up is to configure the sites as duplex bases. I believe the Cactus Intertie is a network that uses this configuration. These networks are usually set up as in-band repeaters, but the receiver audio is linked to the rest of the system and not repeated through the local transmitter. This is what I think you are wanting to do. To do so 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. Setting duplex=1 will not repeat the audio from receiver to transmitter, but uses half duplex operation for simplex nodes. I don't know how this will function when connected to full duplex radios instead of a half duplex mobile. Someone else would have to way in on this aspect. Hope that helps to clear it up. Brett KQ9N

2 1

Re: [App_rpt-users] App_rpt-users Digest, Vol 60, Issue 7
by Steve Wright 03 Feb '14

03 Feb '14

> > > 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

2 1

Re: [App_rpt-users] App_rpt-users Digest, Vol 60, Issue 3
by Tim Sawyer 02 Feb '14

02 Feb '14

Judging from the folks numerous attempts to answer your question each with different answers, maybe it isn’t so clear what you want to do. It might help if you give example frequencies and a detailed description. For example: Lets say you have site A where 146.52 RX repeats mobiles to 52.525 TX. And you have site B where 52.54 RX repeats mobiles to 147.42 TX. An RTCM at each site will make a cross band repeater at each site, and you could link the two sites together via IP. This is not voting or simulcast, just two linked repeaters. Of course, there has to be a server (on the ground or one of the sites) where the RTCMs log in. That’s not split site repeater. A split site repeater is single repeater where the RX and the TX are in the same band on separate sites with a link in between. This is typically done only on 6M (both RX and TX) repeaters because it’s so expensive to duplex on 6M. -- Tim :wq On Feb 1, 2014, at 11:46 PM, Steve Wright <stevewrightnz(a)gmail.com> wrote: > It's perfectly clear what I am doing. > > Theres a split site 2m repeater, AND a split site 6m repeater. > > The transmitters for each repeater are on the OTHER site. > > Linking is done with outdoor wireless ethernet. > > Site "A" (6m TX and 2m RX) > > Site "B" (6m RX and 2m TX)

2 1

RTCM clock generator details pls
by Steve Wright 02 Feb '14

02 Feb '14

Can someone please link me to the details for the RTCM clock generator. Many thanks, Steve -- Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers +64 21 040 5067

2 2

Re: [App_rpt-users] App_rpt-users Digest, Vol 60, Issue 6
by Steve Wright 02 Feb '14

02 Feb '14

> > The RTCM has a single connections for a receiver and transmitter, however > they cannot work independently. > [....] if you would like to have the 2m and 6m repeater separate from each > other you will need 4 RTCMs. > [.....] If you configure the two AllStar nodes as duplex without local repeat, I > believe you can tie the nodes together where one feeds the other and vice > versa - a pair of split site repeaters using just 2 nodes and 2 RTCMs. Ok unless I have misread, we have two opposing opinions stated as fact. Anyone care to offer insight, quote sources or offer configs, or otherwise generally assist in the scientific principle of distilling collective opinion for fact? Steve -- Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers +64 21 040 5067

1 0

Re: [App_rpt-users] App_rpt-users Digest, Vol 60, Issue 4
by Steve Wright 02 Feb '14

02 Feb '14

> RTCM's don't care what the frequency of operation is... just that one > transmits and one receives. > > Pretty much like duplexers don't care what radios are connected to > them... nor does Asterisk care what equipment is on the other side of > the URIx ... COR/COS, Audio in, Audio out, PTT and Ground. > > It's up to you to figure out which radio gets what connection ;-) > I'm pretty sure it doesn't care what antenna is connected either. But this doesn't answer my question. Permit me to rephrase. Again. Two split-site repeaters. Each repeater receiver has its' corresponding transmitter on a geographically distant site (that's what a split site repeater is you know! ;) The sites are linked with outdoor wireless ethernet 802.11an Site "A" 6m TX 2m RX Site "B" 6m RX 2m TX Do I need two RTCMs or four? Steve

3 2

Re: [App_rpt-users] MSF 5000 URI interface
by Bryan D. Boyle 02 Feb '14

02 Feb '14

ok, so I forgot the obvious. mea culpa. it's as obvious as downloading the manual(s) off R-B, looking at the section on the SSCB, and reading the description of the test points. And, oh, having read through WA1MIK's painfully complete theses on the MSF5k, what others have done, and having a copy of the RSS to program the box. -- Bryan Sent from my iPhone 5...small keyboard, big fingers...please forgive misspellings... > On Feb 1, 2014, at 22:53, Brian Gieryk <ke6iyc(a)mac.com> wrote: > > Ummmm, how does the URI key the MSF, seeing as the MSF does not have VOX functionality? > > Curious, nothing more. > > Brian > KE6IYC > >> On Feb 1, 2014, at 7:31 PM, Bryan D. Boyle wrote: >> >> you only need 4 wires. discriminator audio, ground, tx audio. and ground. you can find them on the test points on the main control board. the manuals are on repeater builder, incredibly simple to do. you can terminate the wires to go on to the TPs using .062 molex female pins. >> >> -- >> Bryan >> Sent from my iPhone 5...small >> keyboard, big fingers...please >> forgive misspellings... >> >> >> >>> On Feb 1, 2014, at 21:54, Lu Vencl <vencl(a)att.net> wrote: >>> >>> 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(a)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(a)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. >

1 0

MSF 5000 URI interface
by Lu Vencl 02 Feb '14

02 Feb '14

Anyone have the diagram for URI interface to an MSF 5000? Sent from my iPhone, Lu Vencl

3 2

VOTER boards - separating rx/tx
by Steve Wright 02 Feb '14

02 Feb '14

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

3 2