New AllStar HamVoip SD Card compiled and implemented on the ZS Link Network System

The new AllStar HamVoip SD Card has been compiled and implemented on the ZS Link Network System iro the 49355 HamVoip Node.  Now why would one implement a new SD Card if the one in use was still working.  Well it is quite simple.  As the ZS Link Network expand, certain changes need to be made to accommodate certain functions and setups.  I tried to alter certain settings using the old card but was not successful to change certain files for the new setup.

What changes did I implement on the new SD Card?

• Changed the following settings in the simple-tune-menu: 

• • Change RXONDELAY value to -100.  Rxondelay delays the valid COS signal and is used to stop cyclic keying or ping-pong which can sometime happen.  If you bring up simpleusb-tune-menu and select the "V" view mode.  You can see both the COS input and COS composite displays.  To understand how rxondelay works set it to some high value like 20 or 400ms.  When you transmit to your node you will see the COS input immediately go keyed and the 400ms delay of the composite.  Setting this value to high would cutoff the beginning of a transmission as it delays the actual COS beyond the real COS signal.  The default is 0 and this would be appropriate in most all cases except in the case of the Aasvoëlkop Repeater with a fairly long squelch tail.  In my case -100 did the trick. 
  • Change RXAUDIODELAY value to 5.  Rxaudiodelay is primarily used for squelch tail elimination. It delays the audio in a buffer so that a drop of COS can cutoff a portion of the audio before the COS drops thus eliminating the tail of the transmission where a squelch crash would take place. Since all radios are different this value is adjustable. Valid values are from 0-24 in 20ms increments. Typical values in most cases would range from 5-10 or 100-200 ms. If is obviously not mandatory to use this, some people actually like squelch tails. The default is 0. If you have a way to monitor your node through another node or maybe iaxrpt you can listen when you drop TX on the node you want to adjust and move this value up until the tail is gone. Unless the tail is unusually long you should be able to eliminate it.
  
  
• Repeater / Simplex Settings (rpt.conf): 
  
  
  Go to Repeater / Simplex Node Settings
  Look for duplex = 1
  Change the 1 to 0
  duplex 0
  
  
  
  This means half duplex with no telemetry tones or hang time. I entered this during the setup of the 49355 HamVoip node on the new SD Card. 

• Turn off link connect and disconnect announcements:    
  

         When running a link network we need to turn off those ridiculous connect and disconnect                     announcements which can last a long time and also interrupt the use of the link system.

 

         I edited the following to get rid of the annoying connect/disconnect telemetry messages.

         In rpt.conf look for:

         holdofftelem=1  (Disable courtesy tones) ( 0 = default, 1=Disable)

         telemdefault=0  (Do not make announcements)

         ; 0=voice telemetry off

         ; 1=voice telemetry on

         ; 2=only your telemetry actions

 

• Updated the 49355 Favorites.ini file. Discarded all the old and non-active nodes and added the new and active nodes.
• Tested the AllStar build in DDNS
• Added and setup a dynamic DNS for node 49355 running on a Raspberry PI using Arch Linux.
• Setup a Static IP Address for HamVoip Node 49355.
• Activate Connection Log for HamVoip Node 49355.
• Rewrite the Crontab -e file for HamVoip Node 49355. 

      The following Crontab entries were add:

1.  Auto Connect to the Pretoria Repeater (Monday to Saturday)
2.  Auto Connect to the Aasvoelkop Repeater (Sunday to Saturday)
3.  Auto Connect to the Still Bay Repeater (Sunday to Saturday)
4.  Auto Connect to the East Coast Reflector in the USA (Sunday to Saturday)
5.  Auto Connect to the SARL News Bulletin (Sunday Morning)
6.  Auto Play pre-recorded ZS-Link Network Announcements (Various times of the day)
   

The new SD Card has been in operation for the past week without any issues.  With the old card I did experience some issues which have been fixed by using the new card.  So far I am quite please with the performance and stability of the 49355 ZS Link Hub Network Node.  All the effort and time spend compiling the new card from scratch was a great idea and asset to the network.

Enjoy using the new 49355 HamVoip HUB Node  another valued addition to the SCP ZS Link Network, brought to you by the Southern Cape Link Network Group. 

Dank en Waardering - Skenking van 2m Tait Herhaler deur Fred ZS5SAM

Die administrateurs van die ZS-Link Netwerk Groep will langs die weg graag vir Fred ZS5SAM bedank vir die skenking van 'n Tait 2m Herhaler ter uitbreiding van die bestaande netwerk.  Baie dankie aan Fred vir die skenking van die herhaler.  Die hehaler kan baie handig aangewend word ter uitbreiding van die ZS Link Netwerk.

Op 'n vorige geleentheid het Fred ook 70cm Dipool Antennas geskenk.  Klik HIER vir meer besonderhede.

Die skenking word hoog op prys gestel en is weereens 'n aanduiding van die goeie amateur radio gees en oop-hand welwillendheid wat daar heers in die ZS Link Netwerk Groep!!

Important: Broadcasting of Amateur Radio News Bulletins and reporting in on a Sunday via the ZS Link Network

It has become necessary to provide more information on how the broadcasting of amateur radio Sunday news bulletins work and what you need to know. 

Please take note of the following:

1.  Sunday is quite a busy day with regards to bulletins.  
2.  At 08h00 the ZS Link Network connects to ZS0JPL in Pretoria.  Call-ins take place from Pretoria until 08h15.  The SARL National Afrikaans Bulletin starts at 08h15.  At 10h00 Amateur Radio Today starts with the relay of the SARL National English Bulletin and other interesting amateur radio inserts.  At 15h00 the Wireless Institute of Australia weekly news bulletin is broadcast.
   
3. If you are connected to the ZS Link Network or you access the Aasvoëlkop Repeater you will NOT be able to report in to any amateur radio news bulletin throughout the Sunday.  The ZS Link Network has been setup in receive only mode to prevent causing any interference, lock-ups or any repeater Ping-Ponging on any network to which the ZS Link Network is connected to.
4. Connecting to any other network even world wide is a privilege and causing any "interference" is not in line with the Amateur Radio Code of Conduct.
5. You might argue that you just want to report in before or after the bulletin. Well you certainly can by using Echolink or AllStar (DVSwitch) on your phone and then directly connect to ZS0JPL-R.  You will then be able to report in directly when the controller allocate a slot for Echolink call-in stations.
   
6. Another reason that receive only mode is used is that in the past many radio amateurs tried to report in via Echolink and AllStar using the ZS Link Network.  The VOIP latency prevented them being heard by the person doing the call-ins.   Latency can be up to 8 seconds and "quick draw stations" prevent call-ins being heard.
7. As can be seen there are many factors that play a roll and can cause "havoc" especially with so many stations trying to call-in during the 15 minute period.
8. The above must please not be seen as complaining.  The ZS Link Network Group believe in the best operating practices possible and would not like to be left red-face before, during or after the SARL National News Bulletins, In the past several network links has simply been disconnected when their systems caused "interference".

Well there you have it.  If you do hear other radio amateurs trying to report in to bulletins on a Sunday via the ZS Link Network, please tell them courteously why they will not be heard by the bulletin controller or refer them to this article on the ZS Link Network Blog.   

How to setup Dynamic DNS on Rasberry Pi (HamVoip) using Arch Linux

 In 2017 when I setup my first AllStar Node I needed a Dynamic DNS provider as my dynamic IP address keep changing regularly.  At the time there were quite a few providers available. I opted for the No-IP provider but I needed software to enable the service.  After many days of searching the Internet I found software to be used with Arch Linux.  Allstar Node 49355 has since been running from 2017 using No-IP.  Recently I wanted to setup a "new" HamVoip installation from scratch.  I do have a back-up of the 2017 installation but wanted a different setup for the direct ZS RF Link.  I tried to install the  noip-duc-linux firmware but it would not install on Arch Linux.

Well searching my backup printed files I found a cryptic note of how I installed ddclient firmware using Arch Linux for HamVoip way back then.

I decided to compile a "How to" for those who would like to setup Dynamic DNS for HamVoip using Arch Linux.  I trust that this will be of use to other amateur radio operators still using HamVoip and yes I know that HamVoip has its own DNS server but I prefer to use No-IP for various reasons.

Herewith the setup that worked for me: 

Setup Dynamic DNS on Raspberry Pi (HamVoip) using Arch Linux

Before you begin, you will need:

• A domain name and an account with a Dynamic DNS provider (e.g., DuckDNS, No-IP, or Cloudflare. I use No-IP.com)

• The API key or credentials from your provider for automated updates.

Step 1: Install ddclient

sudo pacman -S ddclient

Step 2: Configure ddclient

The configuration file is located at /etc/ddclient/ddclient.conf.

1. Open the configuration file for editing:

   sudo nano /etc/ddclient/ddclient.conf

   Part of the ddclient.conf file below:

#####################################################

## 

## $Id: sample-etc_ddclient.conf 171 2015-01-20 11:57:13Z wimpunk $

##

## Define default global variables with lines like:

## 	var=value [, var=value]*

## These values will be used for each following host unless overridden

## with a local variable definition.

##

## Define local variables for one or more hosts with:

## 	var=value [, var=value]* host.and.domain[,host2.and.domain...]

##

## Lines can be continued on the following line by ending the line

## with a \

##

##

## Warning: not all supported routers or dynamic DNS services 

##          are mentioned here.

##

######################################################################

daemon=300				# check every 300 seconds

syslog=yes				# log update msgs to syslog

mail=root				# mail all msgs to root

mail-failure=root			# mail failed update msgs to root

pid=/var/run/ddclient.pid		# record PID in file.

ssl=yes					# use ssl-support.  Works with

					# ssl-library

# postscript=script			# run script after updating.  The

					# new IP is added as argument.

#

#use=watchguard-soho,        fw=192.168.111.1:80	# via Watchguard's SOHO FW

#use=netopia-r910,           fw=192.168.111.1:80	# via Netopia R910 FW

#use=smc-barricade,          fw=192.168.123.254:80	# via SMC's Barricade FW

#use=netgear-rt3xx,          fw=192.168.0.1:80		# via Netgear's internet FW

#use=linksys,                fw=192.168.1.1:80		# via Linksys's internet FW

#use=maxgate-ugate3x00,      fw=192.168.0.1:80		# via MaxGate's UGATE-3x00  FW

#use=elsa-lancom-dsl10,      fw=10.0.0.254:80		# via ELSA LanCom DSL/10 DSL Router

#use=elsa-lancom-dsl10-ch01, fw=10.0.0.254:80		# via ELSA LanCom DSL/10 DSL Router

#use=elsa-lancom-dsl10-ch02, fw=10.0.0.254:80		# via ELSA LanCom DSL/10 DSL Router

#use=alcatel-stp,            fw=10.0.0.138:80           # via Alcatel Speed Touch Pro

#use=xsense-aero,            fw=192.168.1.1:80          # via Xsense Aero Router

#use=allnet-1298,            fw=192.168.1.1:80          # via AllNet 1298 DSL Router

#use=3com-oc-remote812,	     fw=192.168.0.254:80	# via 3com OfficeConnect Remote 812

#use=e-tech,                 fw=192.168.1.1:80          # via E-tech Router

#use=cayman-3220h,           fw=192.168.0.1:1080        # via Cayman 3220-H DSL Router

#

#fw-login=admin,             fw-password=XXXXXX		# FW login and password

#

## To obtain an IP address from FW status page (using fw-login, fw-password)

#use=fw, fw=192.168.1.254/status.htm, fw-skip='IP Address' # found after IP Address

#

## To obtain an IP address from Web status page (using the proxy if defined)

## by default, checkip.dyndns.org is used if you use the dyndns protocol. 

## Using use=web is enough to get it working.

## WARNING: set deamon at least to 600 seconds if you use checkip or you could

## get banned from their service.

#use=web, web=checkip.dyndns.org/, web-skip='IP Address' # found after IP Address

#

#use=ip,                     ip=127.0.0.1	# via static IP's

#use=if,                     if=eth0		# via interfaces

use=web,web=checkip.dyndns.com/, web-skip='IP Address'					# via web

#

protocol=dyndns2				# default protocol

#proxy=fasthttp.sympatico.ca:80		# default proxy

server=dynupdate.no-ip.com			# default server

#server=members.dyndns.org:8245		# default server (bypassing proxies)


login=xxxxxxx			  		# your default login user name

password=xxxxxxxx				# you default password

zs1iallstar1.ddns.net 			#yourhostname

#mx.for.your.host				# default MX

#backupmx=yes|no				# host is primary MX?

#wildcard=yes|no				

4. Save the file and exit the editor by pressing Ctrl + X, then Y, and then Enter. 

Step 3: Test the configuration

You can run ddclient in a debug mode to test if your configuration is correct and that it can successfully update your IP address. 

sudo ddclient -daemon=0 -noquiet -debug
sudo systemctl status ddclient.service

You should see output indicating that ddclient has successfully connected to your provider and updated your DNS record. 

Step 4: Enable and start the ddclient service

Once you have a working configuration, you can enable and start the ddclient systemd service to have it run automatically. 

sudo systemctl enable ddclient.service
sudo systemctl start ddclient.service

ddclient will now check for and update your public IP address on a regular basis. 

Step 5: Configure port forwarding

For your Raspberry Pi to be accessible from outside your local network, you must configure port forwarding on your router.

1. Find your Raspberry Pi's local IP address by running ip a on the terminal.

   #ip a

2. Log in to your router's administration page. The IP address is usually 192.168.1.1 or 192.168.8.1.

3. Navigate to the Port Forwarding section. The name and location of this setting vary by router, but it is often under "Advanced," "WAN," or "Network" settings.

4. Create a new rule to forward the desired external port to your Raspberry Pi's internal IP address and corresponding port.

   • For SSH: Forward port 222 on the Raspberry Pi's internal IP.

   • For a web server: Forward ports 80 and 443 to your Raspberry Pi's internal IP. 

Step 5: Test your setup

You can test your dynamic DNS configuration and connectivity by using another device outside your network.

1. Check the DDNS record: Log in to your DDNS provider's website and verify that your domain is now pointing to your current public IP address.

2. Attempt a connection: Try to SSH into your Raspberry Pi using the hostname you configured with your DDNS provider.

 

Bloemfontein ZS4RM AllStarLink Node now active!

 

Yet again another AllStar Node has been activated. This time it is the node of  Roelhof ZS4RM from Bloemfontein.

Bloemfontein is located in the central region of South Africa, within the Free State province. It is the capital of the Free State and serves as the judicial capital of South Africa.  

Key details about its location:

    Country: South Africa.
    Province: Free State.
    Geographic Position: Situated in the center of the country.
    Nickname: Known as "The City of Roses" due to its abundant rose bushes.
    Sesotho Name: Its Sesotho name is Mangaung, meaning "place of cheetahs".

Now lets look at the ZS4RM AllStar Node 

Images:  (Click on images for larger view.)

Herewith information and connection details:

Node Number: 647030

Node hardware = Raspberry Pi

Link Radio = Motorola Radius

Frequency = 145.550 Mhz

AllStar Software = ASL3

Location:  Bloemfontein, South Africa

Finally:  Next time you visit Bloemfontein you most welcome to use the node to talk to the World.  A big thank you to Rulhof ZS4RM who undertook this project and made it a reality.  Well done Rulhof!!  

Images:  (Click on images for larger view.) 

New ZS6CM0 70cm AllStarLink Repeater - Alberton

(Click on images for larger view.)

Curtis ZS6CMO recently completed his 70cm AllStarLink Repeater.  In the video the repeater was connected to the ZS-Link Network in the Southern Cape.  Audio quality was excellent way better than the normal Echolink audio.  The repeater consists of the following equipment:

• Dell Wyse 3040 Mini Computer
• R1-2023 BH7NOR Controller for AllStar
• Motorola Repeater Interface
• 2 x Motorola Radios
• Mobile Cavity Filter 
• Yellow 3D Printed Holder for the equipment

Congratulations to Curtis on constructing a good looking "Mobile" UHF Repeater with excellent audio quality!!

 

SARL HF National Field Day- and SARL VHF/UHF FM Mode Contest at Heuningklip, Saturday, 6 September 2025 Mossel Bay

 

On Saturday the 6 September 2025 a field station was established at Heuningklip near Herbertsdale by a few local radio amateurs that participated in the SARL National Field Day Contest as well as the SARL VHF/UHF FM Mode Contest.

The aim of the SARL National Field Day Contest was to work as many stations in Southern Africa as possible on all the HF amateur bands (excluding the 60, 30, 17 and 12 m bands). QSOs with stations outside the SADC region are also allowed. In doing so, to learn to operate in abnormal situations in less-than-optimal conditions. A premium is placed on developing skills to meet the challenges of emergency preparedness as well as to acquaint the public with the capabilities of Amateur Radio.

The aim of the SARL VHF/UHF FM Mode Contest was a test of operator ability and station design; to promote FM activity on the VHF/UHF bands; to encourage Amateurs to work greater distances than usual by operating Field Stations in favourable locations and by optimising equipment and operating techniques at both field and home stations and to provide opportunities for Amateurs to activate and work new grid squares.

An "HF, VHF/UHF field day contest" is a competitive amateur radio event where participants set up and operate radio stations away from their permanent home locations, using non-mains power, to simulate emergency preparedness and test portable operating skills. The contests encourage teamwork and outdoor adventure, with operations lasting typically 24 hours, and focus on making contacts with other portable stations over high-frequency (HF) and VHF/UHF radio bands.

The following radio amateurs were active from Heuningklip on the day:

1.  Jan ZS1CBS

2.  Danie ZS1DJ

3.  Jasper ZS1WT

4.  Jacobus ZS1JDJ

The weather on the day was great as can be seen from the images and videos.  This station was truly a field station away from any natural or man made noise and open in the veld in a beautiful area away from any concrete or man made structures.  Just four radio amateurs with their equipment and the beauty of mother nature all around them.  (see the video)

From all accounts everyone had a great time even on the VHF/UHF bands.  I heard along the "grape vine" that there are already plans for the next field day event.

Thank you to all the photographers for all the images and videos and for sharing you experience with us.  I trust that this event and the excitement that was experienced will motivate other radio amateurs to setup their own field station and experience the same excitement and pleasure that this group experienced.  There are more than enough contests on the yearly SARL calendar to join in on the fun.

Images:  Click on images for larger view.

7 September 2025 Lunar Eclipse Amateur Radio participation in South Africa

(Click on image for larger view.)

This past Sunday, 7 Septermber 2025 the Moon turned blood red — and the world was watching.

One of the most watched lunar eclipses in history went down.

A total lunar eclipse occurred at the Moon's ascending node of orbit on Sunday, September 7, 2025, with an umbral magnitude of 1.3638. A lunar eclipse occurs when the Moon moves into the Earth's shadow, causing the Moon to be darkened. A total lunar eclipse occurs when the Moon's near side entirely passes into the Earth's umbral shadow. Unlike a solar eclipse, which can only be viewed from a relatively small area of the world, a lunar eclipse may be viewed from anywhere on the night side of Earth. A total lunar eclipse can last up to nearly two hours, while a total solar eclipse lasts only a few minutes at any given place, because the Moon's shadow is smaller. Occurring about 2.6 days before perigee (on Wednesday, September 10, 2025, at 8:10 UTC), the Moon's apparent diameter was larger.

This lunar eclipse was the second of an almost tetrad, with the others being on March 14, 2025 (total); March 3, 2026 (total); and August 28, 2026 (partial).

(Click on image for larger view.)

The eclipse was completely visible over east Africa, Asia, and central and west Australia. It was seen when rising over most of Africa and Europe, and when setting over the central Pacific Ocean.

The Sept. 7-8 total lunar eclipse has come and gone, treating stargazers to a breathtaking blood moon that was witnessed by over seven billion people.

Several local radio amateurs in South Africa joined the stargazers and send in images of the event.  Unfortunately the Southern Parts of South Africa was covered by clouds which resulted that the event could not be observed in this area.  None the less our amateur radio friends in other parts of the country provided images of the event. 

Images (Click on images for larger view.)

Above Images:  Christi ZS4CGR,  Luckhoff (Click for larger view.)

 Above Images:  Zayn ZR3VO, Orania (Click for larger view.)

Above Images:  Gordon ZR2GW, Port Elizabeth  (Click for larger view.)

Above Images:  Jimmy ZS1RB,  George (Click for larger view.)

Above Images: Johnny ZS3JDL,  Kimberley (Click for larger view.)

 

 Above Images:  Warren, Bryan, Dennis and others (Click for larger view.)