On Sun, Jul 10, 2016 at 2:09 AM, Rob Janssen <pe1chl@...> wrote:
> I would not suggest such a setup for linking repeaters!
> Maybe it is bearable for linking end-users to the local repeater, but they
> would still have the problem that they can only transmit after the repeater
> has sent its roger beep AND has switched off the transmitter (hang time).
> This will give Echolink users almost no chance to use the repeater.
> But of course they can listen in.
> When the remote is a repeater as well, of course the situation would be
> even worse...
> To have a well-working Echolink connection with a repeater, you best
> integrate the Echolink system with the repeater itself, not over
> the radio link. So change the repeater to use Svxlink as its control
> software and enable the Echolink module there.
> Of course there is no way to configure Svxlink to do it better, after all
> Svxlink does not know what the remote repeater is doing
> (sending roger beep, sending CW ID, someone talking, transmitter on the
> air for tail time, etc) when it is not in control itself.
I am running this exact setup (and I am the repeater owner). We do not have
Internet available at the repeater site yet, so the Echolink connection
needs to be remote. I am using CTCSS signaling, the repeater is configured
to transmit CTCSS only when there is a valid RF user on the input. As soon
as the RF user stops transmitting, CTCSS on the repeater transmitter stops,
the link radio/svxlink detects this and turns around allowing Internet
users to respond. This also prevents courtesy tones and (most) repeater
ID's from going down the link to the Internet users. I have linked our
repeater to another repeater (also owned by me), and the users couldn't
tell who were local and who were remote. Timers are never exceeded.
This is actually a fairly common way to provide Echolink to a repeater
remotely, I know of other repeater owners doing the same thing (only they
use the Windows Echolink software at the remote site). There are still
issues with this setup, and it does take modification to the repeater to
make it work (in our case, the repeater controller supported this with a
simple programming change), but so far it has worked well. I am using the
CTCSS hardware on the remote radio (a Motorola M10) to detect the CTCSS
change, but svxlink link supports this in software as well.