Thank you all for some fresh ideas. I too like the hub idea even though it
means a Linux server at the repeater site. The problem with Linux at a repeater
site is power outrages. I work for the hosting company that has allowed me to
place our high powered hub in a rack (dual Intel processors, quad core, 16GB
RAM, RAID [ to be replaced with SSD ]) with a 100MBit pipe. We will be able to
handle a lot of connections. At the repeater site we need to make sure that we
at least have a UPS installed that will give the site owners generator time to
come online. Otherwise Linux sucks when it scrambles. It may take hours to do a
FSCK. That means a trip to the site unless we add a KVM over IP device. $$$ all
the way around.
We have three repeater sites. We have three RC-210’s. I propose adding a
RTCM on the 4th port of the RC-210 and then port 1 –> 2m port 2 –> 440
port 3 –> 900.
Here’s the price breakdown:
1 PC: $300
3 URI’s: $297
1 APC SmartUPS UPS: $500
1 KVM/IP: $305
==>> $1397
Compared to:
1 Arcom RC-210: $400
1 RTCM: $269
==>> $669
The difference here besides the price is that each repeater cannot be
individually linked via Allstar. But the RC-210 can allow all three repeaters to
connect to one RTCM. From what Chris Kurtis tells us the RC-210 worked out
fine.
I’d love to read more ideas.
Wayne @ Node 41660
Sent: Saturday, March 21, 2015 9:26 AM
Subject: RE: [App_rpt-users] Multiple Repeaters Per
Site
I
used a port on the 210 for IRLP and then later
allstarlink.
Works
fine.
You
still need a sound fob in between the PC and the 210
though.
The
210 treats the fob as a radio and the fob treats the 210 as a
radio.
210
port àfobß
PC
No
problem at all.
From:
app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org]
On Behalf Of R. Wayne
Sent: Saturday, March 21, 2015 10:32
AM
To: app_rpt-users@ohnosec.org
Subject: Re:
[App_rpt-users] Multiple Repeaters Per Site
But what about using
an external controller like a Arcom RC-210?