ON6URE Visits UBA-TLS: SVXLink, Hotspots and Repeaters
ON6URE Visits UBA-TLS: SVXLink, Hotspots and Repeaters
A club evening that began with linked voice systems moved naturally into repeater engineering, personal hotspots, common-mode current and the practical questions that appear when software meets RF.
RF.Guru working definition: Common-mode current is the non-cancelling phasor-sum current in a specified set of conductors, evaluated at a defined cross-section and using a declared current-direction convention. In the intended differential transmission-line mode, the outgoing and return currents are equal and opposite, so their phasor sum is zero. When they do not cancel, the remaining current must close through another reference or return path—such as the outside of a coax shield, a mast, equipment chassis, station wiring, nearby structures, earth, the operator, or distributed coupling through the environment.
This broader working definition is especially useful in practical antenna systems. On transmit, non-cancelling current on the outside of the coax can make the feedline and connected structures part of the radiating antenna system unless that path is intentional, clearly defined and properly controlled—for example by providing the required return path and placing a suitable common-mode choke at the correct boundary.
On Friday 20 June 2025, UBA section TLS—Tussen Leie en Schelde welcomed me for an evening about SVXLink and the RF systems around it. The presentation started at 20:30, ran beyond 22:00 and then opened into questions that kept the room talking until after midnight.
A Friday Evening at Tussen Leie en Schelde
The reason for the visit was specific: explain how SVXLink can connect local radios, repeaters and personal access points without pretending that every installation is the same network. The room included newcomers as well as experienced repeater operators, so I began with the architecture and kept returning to what an operator actually hears and controls.
The official SVXLink project describes its server as a modular voice-services system for amateur radio. Connected to a transceiver, it can control a repeater or work on a simplex channel; services are loaded as modules. Reflector software and network configuration can then link independently operated nodes.
Important distinction: SVXLink is software, not one universal repeater network. Which repeaters share audio, which talkgroup is active, who may connect and how long a link remains open are deployment decisions made by the operators of that network.
One Call Can Reach Several Repeaters—When They Are Linked
I used the local repeater in Gent as a concrete example. A transmission received there can be distributed to several other repeaters when those nodes are connected through the same configured talkgroup or linking logic. It is the active network configuration—not the RF signal from Gent somehow reaching every transmitter—that causes the other sites to retransmit the audio.
That distinction matters. A linked group can change, nodes can disconnect and administrators can apply access rules, timeouts or priorities. The UBA later advertised another of my talks with the same practical proposition: one call can open multiple linked repeaters and a personal hotspot can provide another way into the system. That UBA event description supports the subject of the presentation, but it is not a permanent topology map.
The Hotspot Was a Local Radio Doorway
The hotspot demonstration showed how an operator can use a small local radio interface running suitable software and network configuration instead of reaching a participating repeater directly. From abroad, the Internet side may still reach the configured reflector service, while the operator uses a short local RF path to the hotspot.
That possibility is conditional, not automatic. The hotspot must be accepted by the relevant network, the callsign and talkgroup settings must be correct, and every RF transmission remains subject to the licence and band rules where the transmitter is physically operating. “Remote” in this context describes the network path; it does not remove the local RF station or its operator responsibilities.
I also walked through the logic of configuring a personal SVXLink node. The durable lesson was not a list of settings copied from one machine. It was that the radio interface, audio levels, squelch and PTT control, callsign, reflector credentials and talkgroup behaviour must agree as one system. The project’s official documentation remains the appropriate source for current configuration details.
Linux Met the Antenna System
After a short drink break, the prepared talk became an open RF session. Questions moved from repeater configuration to receive and transmit antennas, matching, unwanted common-mode current and the compromises found in real stations.
Those subjects belong together. A linked repeater can have perfect IP connectivity and still suffer from poor receiver sensitivity at the site, transmitter noise, desensitisation, bad audio alignment or current on an unintended cable path. Conversely, a clean RF installation does not compensate for the wrong talkgroup, unstable network path or badly configured audio processing.
My engineering thread through the evening: name the path before judging the symptom. Separate the local RF link, repeater controller, network link and remote transmitter, then test the part that can actually produce the fault.
Questions Were the Second Half of the Talk
The formal presentation ended, but the useful part of a club visit often begins when members put their own stations on the table. I stayed with individual questions and discussed the constraints behind them rather than prescribing one universal antenna, hotspot or repeater arrangement.
This was a knowledge-sharing visit, not a certification of a particular network, node, product or station design. The event showed why amateur-radio infrastructure stays interesting: software developers, repeater keepers and antenna experimenters can look at the same voice path from different ends and still learn from one another.
It was after midnight when I finally headed home—nearly four hours after the talk began. For more of the RF questions that continued around the table, visit the RF.Guru Knowledge Base or browse the RF.Guru shop and engineering library.
Project and event references
- UBA-TLS / Amateurradioclub De Pinte—the host section and its amateur-radio mission.
- UBA: SVXLink network presentation—a later event notice describing my linked-repeater and personal-hotspot presentation.
- Official SVXLink project repository—server purpose, repeater/simplex operation and modular services.
- Official SVXLink documentation—architecture, installation, configuration examples and user documentation.
Mini-FAQ
- What is SVXLink? It is a modular amateur-radio voice-services system that can control a repeater or simplex station and can connect configured nodes through services such as a reflector.
- Is SVXLink one worldwide repeater network? No. It is software used by separately configured systems. Node membership, talkgroups, access and linking behaviour belong to each deployment.
- Why can one call appear on several repeaters? The receiving node sends audio through an active network link or talkgroup to other participating nodes. The extra transmitters are activated by configuration, not by the original RF signal reaching every site.
- Can a personal hotspot provide access from abroad? It can when the hotspot, network policy, account and Internet path permit it. The local RF transmitter still has to comply with the rules where it is operating.
- Does good Internet connectivity guarantee a good repeater signal? No. Local RF coverage, interference, desensitisation, audio alignment and antenna-system behaviour remain separate parts of the end-to-end path.
- Was the TLS evening a product or network endorsement? No. It was a technical presentation and question session about how linked voice systems and their RF interfaces behave.