On 03/29/2012 03:55 AM, Eren Türkay wrote:
>> I have svxlink working pretty well with my RigExpert TI-5 USB interface,
>> but I do have a few questions.
> Can you please provide more information about the repeater you are
> configuring? It will be useful to state exactly what your configuration is,
> what the typical use scenario is, and what the radios are so that it would be
> easier to solve the problem.
Thanks for your reply, and sure, I'm happy to.
The radio in question is a Kenwood TS-2000. One feature of this radio
is that it has two fully-independent transceivers, and is capable of
full-duplex operation so long as each transceiver is tuned to a
different band. So, for instance, I can have an input frequency on the
2m band, an output frequency on the 70cm band, and I have an instant
repeater... just with a 300MHz offset ;-) In fact, the radio has a
built-in repeater feature, although it is extremely limited in scope.
Furthermore, the TS-2000 has separate audio outputs for both
transceivers, and it can keep one of them open even while it's
transmitting on the other transceiver.
The RigExpert USB interface takes these separate audio outputs from the
TS-2000 and maps one to the left audio channel and the other to the
right audio channel as it feeds them to the PC. The RigExpert is also
capable of full-duplex operation. So I tell svxlink that my transmitter
is on the left channel, the receiver is on the right channel, and there
we have it: instant homebrew repeater, completely full-duplex, like a
regular repeater in every way except the unusually large offset.
> I guess, repeater logic in svxlink was written for full-duplex
> (ie, two radios, rx and tx at the same time with different frequencies). So,
> you should think in that way. The problem you have is really what's written,
> the repeater is not activated :)
> First, you should activate a repeater with some way. These ways include
> sending DTFM digit codes, 1750 tone burst, CTCSS, or SQL. Please see OPEN_ON_
> configuration in man page.
I am using CTCSS for this purpose. It works well.
> I haven't tried the other options other than OPEN_ON_SQL. Normally, I set
> OPEN_ON_SQL=1000, which causes RepaeterLogic to open when squelch is open for
> 1 second. As you may ask, how the squelching is done? Well, you already set
That strikes me as unusually large for a repeater; it would clip the
first second of somebody's transmission. People usually announce
they're ready for a conversation on a repeater by saying something like
"KR0L monitoring", and a 1-second delay would probably clip that
callsign out entirely.
> RX= option in RepeaterLogic. In RX configuration, I detech squelching via
> CTCSS tone 88.5. It means that my repeater is activated via CTCSS 88.5 tone
> sent for 1 second. So, the typical usage of the repeater is:
> 1- User transmits for 1 second and waits for repeater to respond
> 2- Svxlink understands that squelch has opened. And after 1 seconds, it
> activates the repeater
> 3- Svxlink starts to send beginning with a tone that indicates that repeater
> is up.
> 4- User talks, and ends the conversation.
> 5- Svxlink understands that squelch has closed, it continues to send until
> IDLE_TIMEOUT has expired (remember that this is full-duplex)
> 6- After it expires, svxlink stops transmitting and sends a tone that
> repeater is deactivated
OK, that makes some things more clear. Except for item #5, I would be
fine with that for a personal repeater, though it is very different from
what people's expectations are of repeaters in general (at least in the
USA, I've never seen a repeater that behaves like that.)
#5 would continue to be a problem for me. Why would we keep the
transmitter active when there is no audio coming in on the receiver? It
doesn't seem very useful to me. There are also certain regulations that
require an automated transceiver to have a time-out timer, and keying
the transmitter continuously during a QSO would make it likely to fall
afoul of that time-out timer.
> I guess the beep problem is because of the event that is triggered after the
> repeater is down. Please see /usr/share/svxlink/events.d/RepaeterLogic.tcl.
> It is defined in repeater_down() function. You can edit the file and do
> whatever you want after the repeater is closed. Remember that svxlink
> repeater section does not work as we expect. It has it's own characteristic
I'm noticing ;-) I did track down that file, and it looks like it
should play two tones, but I'm only hearing one. But it also does look
like it could explain why I was hearing the repeater identify itself way
more often than I told it to.
> As far as I understand, you want to use your repeater as if simplex node
> with a roger beep? So, your use scenario is:
> 1- User transmits
> 2- Svxlink understands that squelch has opened and begins to repeat it.
> 3- After squelch has closed, send roger beep
> 4- End transmission.
Yes, precisely right. This has the added benefit of being pretty much
what people expect from a repeater ;-)
> So, please specify the user scenario and radio configuration in detail.
> I hope it helps.
As far as user scenario goes, I'm in the "experimentation" phase right
now - trying to learn what svxlink is capable of.