====SVXLink==== The current role of //Svxlink//, is as a single and complete package of softwares providing connectivity between amateur radio users and nodes in the following ways: 1. A duplex and simplex repeater controller, based upon the small size factor computers such as the raspberry pi, using as few external components as possible. A Raspberry Pi and 16 Gb SDCard and a CM108 USB Sound card are the only three components required to which to attach an FM Transceiver. 2. A reflector controller providing a server for a group of duplex or simplex repeater nodes to link passively with the server and dynamically with other nodes similarly linked. As an example a link is provided below. A number of Repeaters and nodes are already available. 3. A remote link controller for remote receivers and transmitters, providing fill-in sites for black spots on an existing repeater coverage. Each node can be its own EchoLink controller, with other facilities built in such as Metar Information, Propagation Information, and audio messaging, subject to configuration within the node itself. Primarily for FM mode (frequency modulation), advanced facilities exist permitting connection to other digital modes. Some nodes have been modified for HF (high frequency) use. With a passive connection to a server, users on a connected node can dynamically connect, using a stream of DTMF tones, to another node or nodes equally passively connected, on a system of Talk Groups, that each node can monitor within their configuration. The current system provides that in a passive state, a node has talkgroup 0 or ‘off’ selected. By calling by DTMF 91235#, on a node… 91 meaning ‘standby, a talk group follows’ 235 ‘ talk group’s # ‘activate’, the node makes the reflector server open a dynamic path to all nodes that have 235 in their monitoring list. Thus a user can now be heard on all nodes that have 235 included. Materially each node has a built-in fail safe that times out a module after a period of disuse, returning it to default passive state. Each repeater is independent and can be used locally, with the addition of regional or national capability as required, dependant on the prevailing talkgroups. More than one connection at a time by different talkgroups can be achieved on the reflector. There is a proviso that if any of the independent EchoLink or Metar services are in use, the passive reflector link is for the time being suspended, returning to default when those other services are terminated. The obvious questions are: What do I need? How’s much does it cost? How do I do it? I already have all-star, why do I need this? First of all, SvxLink is designed by Tobias Bloomberg SM0SVX, firstly around 2006/7, as a means to access EchoLink via a Linux platform, but linking analog modes. AllStar is built around 2013 from Asterisk a PABX package for telephones. (Linking the two systems together while possible is inadvisable.) In Svxlink, no node numbers are required, just the natural callsign, and password provided to the reflector keeper by the node builder for the passive connectivity. The reflector maintains the callsign information in a dataset that is displayed by another software package called SvxPortal that can be viewed publicly here [[http://svxportal-uk.ddns.net:81]], so users can view the available stations and the talkgroups available. Each node user can update an entry on the svxportal to describe his station for public view, to further enhance his/her presence. HubNet is already available on the UK portal svxportal-uk.ddns.net. To build a node, all that is required is almost any spare transceiver, a raspberry pi and its power pack, a 16 Gb SD card, a CM108 USB sound card, a 10K 1/4 watt resistor, and a 2N2222 transistor. A full tutorial is shown here in this link [[https://www.marrold.co.uk/2018/04/converting-cm108-usb-fob-for-amateur.html]]. You will need access to a Mac/PC, with a card slot to write the operating system with RaspberryPi Imager in the first instance, and an internet connection. Only a little knowledge of Linux and Shell script is required, but it’s very simple, provided the directions are followed carefully. Because there are so many different systems, it is not possible to provide a “one size-fits all” image, that is capable of being updated, so some technical knowledge is required. There are so many sources of the software that have been adulterated by others to fit particular devices, that I would recommend sticking with the main source of svxlink that of SM0SVX. Within my pages I refer to scripts of my own making that can help a user build this system. **Full instructions** are found on [[https://github.com/f5vmr/svxlinkbuilder]] of which the new version 24-02.1 making the build even simpler is now available. Firstly always follow the instructions, NEVER use root to run the software, and always follow the instructions…….. Yes I did say that twice because you ignored it the first time and wondered why it didn’t work. The menu system in this script allows you to build a node or repeater with minimal programming knowledge, provided you read the instructions... This is an example of what you get with password protected full editing capability for the sysop, including the settings for the soundcard. If you wish to know more then please go to [[https://g4nab.co.uk]] where you will find more information. {{:screenshot_2024-05-05_at_17.06.10.png?direct&400|}} {{::screenshot_2024-06-17_at_19.19.38.png?direct&400|}} {{::screenshot_2024-06-16_at_16.15.01.png?direct&400|}} {{::screenshot_2024-06-18_at_14.49.57.png?direct&400|}} ((The current version of the SVXLink package is Version 24-02.1 and is not yet currently available as an dpkg. But this is in the pipeline. If you do find a dpkg on the current version of Bookworm, it is an old version 19 and has several features absent, such as the gpiod functionality, and full connection to the svxreflector. Other versions of SVXLink have existed including one from the OpenRepeaterProject in the US, but again this version is also out of date, although that group is working on the next version.))