Re: [Svxlink-devel] Repeater RF audio not going out internet

[Gustavo C. <gus...@gm...>]

Hi Dave,

   I'm running a couple of systems very similar to yours (remote link 
controlled repeater).
   I have a VHF repeater linked via UHF to the "svxlink" place.  At the 
repeater site there are two Motorola GM300 for VHF RX and TX and one 
Motorola SM50 for UHF simplex link. The interface is homemade and very 
simple: audio link (always connected) between the three radios, and VHF 
TX PTT is a logic OR between VHF RX and UHF radio's COR, UHF PTT is 
handled by VHF COR.
    In my system I've configured the svxlink logic as Simplex, since the 
link radio is half duplex and the "repeat" function is handled by the RF 
repeater. This repeater does not have Echolink access, but in the past 
I've had such a system in service. I also think that, from the Echolink 
network point of view, you should configure your system as a Link, 
because full duplex operation is not possible. From some time now, my 
node LU8WFY-R is working with two GM300 directly connected to the PC.
    The same situation will be valid for a system that uses a VHF radio 
tuned to the repeater's frequency pair.
    This configuration has the limitation that you have no control of 
the repeater function (it's hardwired at the repeater site). For full 
svxlink functionality on your repeater, you should connect the PC 
directly to the repeater or use a full duplex link (another repeater 
pair.....).

Hope this experience could be of any help.

73!

Gustavo - LU8WFY
Patagonia
Argentina

On 04/08/2015 12:02 PM, David Rock wrote:
> * Rob Janssen <pe...@am...> [2015-04-08 09:23]:
>> David Rock wrote:
>>> As you can see, when I key up my HT and send tones, they are going
>>> HT -> RF repeater -> Base radio -> svxlink
>>>
>>> but I always get the "repeater is not up" messages.  I think this is an
>>> illustration of the same problem I'm having with voice audio not getting
>>> handled and sent out the internet.
>>>
>>> I think if I can get a clear understanding of how to get the repeater
>>> (ie, the EchoLink Module) "up," everything will fall into place, but I'm
>>> really misunderstanding something.
>>>
>> Yes I think this is the problem.  For some reason your repeater has not opened on the signal.
>> Our repeater opens on just the squelch opening, and we have this:
>>
>> OPEN_ON_SQL=0
>> OPEN_ON_SQL_AFTER_RPT_CLOSE=0
>> OPEN_SQL_FLANK=OPEN
>>
>> I'm not sure if this is the minimal config but it has been there for a long time and it works.
>> The 0 values can be set to a minimal time of transmission or idle, see the manpage.
>>
>> What is not completely clear from the equipment description you gave is if this is an actual RF repeater
>> (as you specified just a mobile radio that is probably not duplex), or if you have an echolink access point
>> with a halfduplex trx connected.
>>
>> When it works OK as a repeater, via svxlink (i.e. the audio passes through svxlink not directly bypassed,
>> you can verify that by checking that there is a small audio delay between input and output) then of course
>> there is no need to look at soundcard issues or the repeater not opening.
> I think I'm starting to see what the issue is, but not sure what the
> solution is.  Let's start with a more detailed description of my setup:
>
> 1. RF Repeater - Motorola MSF5000 located about 10 miles away
> 2. Radio connected to svxlink - Motorola PM400 in my house
> 3. svxlink hardware - Raspberry Pi model B
> 4. RF test unit - ADI At-401 handheld
> 5. Echolink client test unit - iPhone client
>
> I do not have svxlink directly connected to the MSF5000; I'm using a
> "Remote-link" rather than "Hard-Wired" repeater connection as described on
> http://www.echolink.org/repeater_tips.htm
>
> "With the "remote-link" approach, an FM transceiver is connected to the
> EchoLink PC at a convenient location in range of the repeater, and tuned
> to the frequency pair of the repeater.  In this configuration, the
> transceiver behaves very much like an ordinary local repeater user,
> transmitting on the repeater's input frequency (on behalf of EchoLink
> users) and receiving on the repeater's output frequency.  Although this
> allows the EchoLink equipment to be placed in a more convenient
> location, it presents some challenges with respect to RX control."
>
> Trying the OPEN_ON settings you gave me, it became more obvious that the
> Tx1 is _not_ intended for transmitting out the internet.  Those settings
> resulted in svxlink trying to send the incoming signal from the MSF5000
> to the PM400 back out, locking the TX open indefinitely.  This is not
> what I'm looking for.  As you mentioned earlier, your settings are based
> on direct-connect to an actual repeater (ie, the Hard-Wired described
> above).  I don't need svxlink to transmit (that keys the radio, but
> that's the radio that is receiving the audio; it can't, and shouldn't do
> both); I need it to take the incoming audio from Rx1 and send it to the
> EchoLink network.
>
> So I guess my first question is does svxlink support running in a
> "remote-link" configuration, or is it designed only for "hard-wired"?
>