Differences

This shows you the differences between two versions of the page.

--- svxlink [2024/06/18 16:46] – Change to link g4nab
+++ svxlink [2025/08/10 20:41] (current) – g4nab
@@ Line 18: / Line 18: @@
 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 after a period of disuse, returning it to default passive state.
+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 by different talkgroups can be achieved on the reflector.
+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.
@@ Line 25: / Line 25: @@
 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.)
+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. As it happens I have made multiple Allstarlink node available as Talkgroups within the svxlink reflector.
-In Svxlink, no node numbers are required, just the natural callsign, and password provided to the reflector keeper 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.
+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]].
+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]]. However there are no some ready-made USB dongle that are quite inexpensive. Check my web-site g4nab.co.uk.
-You will need access to a Mac/PC, with a card slot to write the operating system 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.
+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 bash scripting may be required.
-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.
+Because there are so many different systems, it is not possible to provide a “one size-fits all Operating Systems” image, that is capable of being updated, so some technical knowledge is required.
+That said if you go to the following page and select downloads, you will find an image for raspberry pi. Follow the instructions carefully. https://portal.svxlink.uk:8443 . a DTMF Help sheet is also downloadable.
+{{:screenshot_2025-08-10_at_21.28.01.png?400|}}
+{{:screenshot_2025-08-10_at_21.31.59.png?400|}}
-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.
+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 web-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]] Not in French or German.
+**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.
@@ Line 50: / Line 53: @@
-((The current version of the SVXLink package is Version 24-02.1 and is not yet current 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 and has several features absent, such as the gpiod functionality, and full connection to the svxreflector.
+((The current version of the SVXLink package is Version 24-02.1 and is available as I suggested above as an image. 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.))
+Stop Press:
+While the image for version 24 is still very much valid, a new version 25 is available either from the author SM0SVX that requires full compilation, or as a script package at the latest post on my web-site g4nab.co.uk. However this is very touchy, and will require some babying into a working condition. Stick with the Image Version 24 for ease of use.
+I mentioned in the chat that the OARC Radio channel is now available on the svxlink reflector. As a reminder the SVXLink system is FM, but relies on the OARC Digital ASL Reflector to connect. Tests have proved that this has been highly successful method of interfacing..