<HTML><HEAD>
<STYLE><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></STYLE>
</HEAD>
<BODY class=hmmessage dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Tahoma'; COLOR: #000000">
<DIV>If I am using a RTCM why do I need a PC at all? We are talking about
repeaters and I think you are thinking that we are talking about remote bases. I
could be wrong. Or may be. I’m so confused. SMH. LOL. My question was really
about using a PC/Pi rather than a RTCM.</DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=doug@crompton.com
href="mailto:doug@crompton.com">Doug Crompton</A> </DIV>
<DIV><B>Sent:</B> Wednesday, November 18, 2015 10:27 PM</DIV>
<DIV><B>To:</B> <A title=arm-allstar@hamvoip.org
href="mailto:arm-allstar@hamvoip.org">ARM Allstar</A> </DIV>
<DIV><B>Subject:</B> Re: [arm-allstar] BBB/Pi or RTCM</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV dir=ltr><FONT color=#000000 face=Tahoma,sans-serif>The BBB and RPI2 include
(like Acid) the voter channel driver and they do work with the RTCM. For new
installations we recommend the RPi2 rather than the BBB. The RPi2 could be used
to replace a PC acid box to interface with the RTCM's at your remote locations.
The RTCM's would take care of the timing and voting utilizing GPS for the RX
sites you have connected in conjunction with the voter channel driver in the
Allstar code at the central RPi2. <BR><BR>So you could replace any power hungry
PC's with RPi2's but you would still need the RTCM's if you wanted to vote. A
far cheaper but less convenient and functional method would be to just use
RPi2's everywhere in the system and use frequency or PL manual control. A
user would switch input frequency or PL on the same frequency when they were in
different areas. Probably not what you want but a method that is sometimes
used.<BR id=FontBreak></FONT><BR><B><FONT style="FONT-SIZE: 16pt" size=4>73
Doug</FONT><FONT style="FONT-SIZE: 16pt" size=4><BR></FONT><FONT
style="FONT-SIZE: 16pt" size=4>WA3DSP</FONT><FONT style="FONT-SIZE: 16pt"
size=4><BR></FONT><FONT style="FONT-SIZE: 16pt"
size=4>http://www.crompton.com/hamradio</FONT></B><FONT style="FONT-SIZE: 16pt"
size=4><BR></FONT><BR><BR>
<DIV>
<HR id=stopSpelling>
From: allstar@controlservers.net<BR>To: arm-allstar@hamvoip.org<BR>Date: Wed, 18
Nov 2015 21:01:16 -0800<BR>Subject: [arm-allstar] BBB/Pi or RTCM<BR><BR>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Tahoma'; COLOR: #000000">
<DIV>Most of the threads in here are well above my head even though I am a
System Administrator for a hosting company. I build PC’s and load and configure
the OS all the time. I get the OS side of the threads most of the time here. But
I don’t read questions like, should I use a BBB or a Pi instead of a RTCM if I
want a voted RX system with a central TX site. Our Los Angeles area TX can be
heard for 150 miles in most directions due to our great location. But our RX is
compromised by having the outputs of two repeaters within 15KHz of our RX
frequency. So... we need a higher RX field strength. Voting multiple RX sites
seems to be the solution.</DIV>
<DIV> </DIV>
<DIV>So okay... how would a BBB or Pi be a better solution than a
RTCM?</DIV></DIV></DIV><BR>_______________________________________________
arm-allstar mailing list arm-allstar@hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the BBB and
RPi2 web page - http://hamvoip.org</DIV></DIV>
<P>
<HR>
_______________________________________________<BR><BR>arm-allstar mailing
list<BR>arm-allstar@hamvoip.org<BR>http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<BR><BR>Visit
the BBB and RPi2 web page - http://hamvoip.org</DIV></DIV></DIV></BODY></HTML>