Why do radio amateurs not leave large enough gaps ("overs") between transmissions?

Does the title of the above article sound familiar? 

On numerous occasions the ZS Link Network experience the "to quick on the trigger (PTT)" habit. Yes it is a bad habit and the author is also guilty at times.  No pointing of fingers here let's find out why this happens.

I wrote the following this morning on the WhatsApp Group:

"Gaps, gaps etc. Stations cannot connect to the ZS Link Network Group's networks. Stations are left out in the cold. We must please leave gaps and not be so quick to press the PTT between overs. There are some of our regulars who want to connect to the DMR links and other systems, but cannot get in. Let's please leave long enough (5-8 seconds) gaps between rounds. We don't want to lose stations because they can't connect/disconnect or log in. No, I have nothing to do with the administration of the network anymore, but just felt like bringing it to everyone's attention again in the interest of the group. - ZS1I"

In amateur radio, failing to leave a gap between "overs" (transmissions) is known as "quick-keying" or "tailgating." Experienced operators strongly advise against this because it disrupts the flow of communication and violates standard Ham Radio Etiquette.

Now why do radio amateurs not leave large enough gaps ("overs") between transmissions?

Radio amateurs often fail to leave sufficient gaps ("overs") between transmissions due to a combination of ingrained habits from crowded operating environments, the desire to prevent others from "stealing" the frequency, and the rapid, conversational nature of "rag-chewing" (casual chatting). 

Common reasons for short breaks or overlapping transmissions include:

• Habit from Crowded Frequencies: Many radio amateurs are accustomed to operating on crowded bands or repeaters (particularly on 10-meter or 75-meter bands), where any significant pause is perceived as an opportunity for another station to "steal" the frequency or interrupt the conversation.
• Fear of "Stealing" the Conversation: There is a common belief that if an operator leaves too long a pause, another user will break into the conversation, leading to a "quick key" reflex.
• "Rag-Chewing" Mentality: In casual, relaxed conversations, operators often treat radio like a telephone call, aiming for a rapid exchange of information rather than the formal, slow pace of traditional radio procedure.
• Misunderstanding Repeater Operation: Some operators do not wait for the repeater's "courtesy tone"—a sound that signals the repeater has reset and is ready for the next transmission—leading to "doubling" (talking over someone) or premature transmission.
• Unfamiliarity with Proper Etiquette: Not all operators are fully trained in, or consistently follow, best practices regarding break times, which recommend a 5-second pause to allow for emergencies or other stations to join.
• Imitating CB Practices: Some amateur radio operators carry over habits from 11-meter (CB) radio, where fast-paced, high-interference communication is common.

Best Practices to Avoid Overlapping:

• Listen First: Always listen for a few seconds before transmitting.
• Wait for the network to reset: On repeaters, wait for the network to reset before keying up.
• Pause intentionally: Leave a 5–8 second gap between "overs" to allow for break-ins, especially for emergency calls.
• Release the PTT: Fully release the push-to-talk button to ensure the repeater resets properly.

As far as DMR communications over the internet is concerned,  here is some information as to why on should leave a large enough gap between overs:

Networked Digital Mobile Radio (DMR) communications over the internet introduce significant and noticeable latency (delay) due to a combination of digital voice encoding and Forward Error Correction (FEC), and internet traffic delays.

Key Aspects of DMR Internet Latency:

• Operational Courtesy: Because of this latency, operators should wait at least 5 seconds after hearing the end of a transmission before initiating a new one to avoid breaking traffic.
• Transmission Delay: It is recommended to wait approximately 2 second after keying the transmitter before speaking to ensure the connection is established.
• Causes: Latency is introduced by the digital encoding of voice at the transmitter, FEC processing at the receiver, and internet packet routing.
• Technical Performance: Specialized DMR over Internet Protocol (DoIP) gateways can achieve a conversion delay of 9.10 ms, with an average jitter of 1.90 ms and low packet loss.

Operational Considerations:
Unlike analog radios, DMR does not have a "repeater squelch tail." The inherent digital delays mean conversations can feel staggered, requiring disciplined, patient, and structured communication protocols to avoid talking over others and to accommodate the shared nature of networked resources.

 

Enough written and we all know now what to do from here-on!!

ZS1I WSPR Beacon now active on 10 Meters from Mossel Bay, Southern Cape, South Africa

(Click on the image for larger view.)

The current WSPR (Weak Signal Propagation Reporter) beacon is set up to transmit low-power signals to monitor global radio wave propagation paths over extended periods, providing data to visualize which radio bands are open and how they are performing

. It's used by amateur radio operators to study atmospheric conditions, test antennas, identify optimal bands for communication, and contribute to a global database of propagation information without requiring manual operation.

I have decided to change the Band / Frequency of the WSPR Beacon currently in operation from Mossel Bay in the Southern Cape.  It was running on the 40 Meter band from  7 October 2025 @ 10h00 SAST to the 15 April 2026 @ 08h00 SAST.  From the 15 April 2026 09h00 SAST it will be transmitting on the 10 Meter band until further notice.

Particulars of the ZS1I Ultimate 3S Beacon active on 10 Meters:

• Call: ZS1I
• Freq. Band: 28.126 000 Mhz
• Dial Freq. :  28.124.600
  
• Band:  10 Meters (28 Mhz)
• Grid:  KF15BT
• Power:  250 mW
• Mode: W-2  (WSPR2)
• Antenna:  EFHW (49:1 Balun)
• TX Period:  Every 10 Minutes
•  Beacon on the air from:  15 April 2026 @ 09h00 SAST
  
•  First Spotter:??????  (Who will it be?)
  

Spotting reports are welcome for 10-meter WSPR beacons, as this band is frequently active and highly dependent on daily propagation changes. WSPR (Weak Signal Propagation Reporter) is frequently used to test HF antenna performance at low power (e.g., 200mW to 5W), with reports uploaded globally. 

How to Spot and Report 10m WSPR

• WSPRnet.org: The primary database for all WSPR spots. Data can be analyzed in real-time.
• WSPR.rocks: A fast, interactive site for searching WSPR data.
• WSPR Watch (iOS App): Useful for monitoring where 10m beacons are being heard in real-time.
• PSK Reporter: An excellent tool to visualize real-time propagation maps and see who is hearing your beacon.
• 10m Frequency: WSPR 10m activity is usually found around 28.1246 MHz (USB dial frequency).

Key Considerations for 10m WSPR

• Propagation: Even when the 10m band seems quiet for voice (SSB), WSPR can show open paths, particularly as the sun moves toward solar maximum.
• Timing: An accurate clock (GPS-synced) is essential, as transmissions start 1 second into an even UTC minute.
• Reporting Frequency: Even very low power (10mW - 20mW) can yield significant DX on 10m.

Finally:  I am looking forward to receive spotting reports of the ZS1I 10m WSPR Beacon active from Mossel Bay, South Africa. 

 

BREAKING: New additions / extensions to the ZS Link Network in the Southern Cape! (Part 3)

ZS1I MMDVM / DMR Repeater issues and how to fixed them.

In the last week or two I ran into some issues regarding the DMR Repeater we are using in the Southern Cape Area.  Now some might one day run into the same issues and I therefor decided to write this article on how to fix the issues.

Here is the issues I experienced:

• DMR Repeater does not except any "calls" from my trusted TYT MD380 and Hytera MD785G radios.
• The Huawei B525 Router used with the DMR Repeater all of a sudden could not access the Internet.
• I used my Windows computer to program the TYT MD380 HT radio in the past.  This time around I could only read the radio but the CPS Firmware refused any other command and would crash as soon as I enter any information.

The above "errors" apart from being frustrating kept me busy for a few days while fault finding.  Now let's look at each "error" individually.

DMR Repeater does not except any "calls" from my trusted TYT MD380 and Hytera MD785G radios.

Background:  The repeater and the two radios worked flawlessly until one morning when I started / rebooted all three items.  Please not all three items was shut down properly the night before.  Never ever hotplug any cables to any of the above radios, hotspot or raspberry pi!!  Well I did not.   I hear some of you say but it must be a problem with the DMR Repeater.  I also thought so and worked  through all the settings of the repeater firmware, calibration and hardware setup.  This took at least two days, working on and off as I find the time.  No luck at all.  It seems if all three radios just decided to be like a stubborn donkey.  Well the next possible fix was to replace the WSPD firmware which I used a the time with Pi-Star firmware.  It might have been a firmware "glitch" as my grandson named software issues.  I took out the WSPD card and re-write a new SD card with the Pi-Star firmware and slotted it into the Raspberry Pi.  No change so I made the assumption that there was nothing wrong with both firmware's.  Just as I side-note using DroidStar was working fine on the DMR Repeater, DMR Bridge and ZS Link Hub.  I looked at Brandmeister under My Devices and every device in used reflected that it was active and working.  ID's matched the devices and Static Talk Groups were set.  All that was left was to go through the CPS files of the 2 RF Radios.  I thoroughly scrutinized the CPS files but could not find any issues.  I started running out of options but somewhere there is a problem and that needs to be fixed.

The error / errors:  If I could get one radio to work the other one would be fixed instantly.   I needed to look deeply into the error issue.  I used the TYT MD380  Radio to label the error.  Error = The radio would TX for a short period and then a error beep would sound.  The LED on the radio goes red when TX'ing but then alternate between red and green.  The DMR Repeater screen stays in the default display while the RX and TX radio LED's will light up as it should.  Nothing else happens and this indicate that the MD380 radio does not open the repeater.  I hear you shout Talk Group, Color Code, Time Slot, Calibration, TX and RX Frequency, RX Group List and Zone.  Well checked all of that with no joy!

To solve the issue:  The solution to the problem was quite easy and mainly overlooked.  It was a DMR ID issue that was solved by just deleting two numbers.  Let's look at the solution.  I use a 7 number DMR ID and for the purpose of this article I will use 655xxxx.  Let's to to Configuration in Pi-Star.  Move down to General Configuration and find CCS7/DMR ID. The ID must be 655xxxx (7 Digits).  At the same time make sure that your Hotspot Security Password in DMR Configuration is correct.  Also ensure that in DMR ESSID there is no ESSID.  It should look like this 655xxxxNone.  Now click on Apply Changes and wait for the screen to return.  Once the changes were set go to the top of the page and look for Expert.  Click on Expert.and then on MMDVMHost.  Under the General Tab ensure that the Id is the seven number 655xxxx.  Now go down to the DMR Tab and this is where my error originated.  Go to Id en  make sure that you enter the 655xxxx number.  For some rime or reason my Id looked like 655xxxx05.  Do not ask me where the two last digits came from. These two numbers created the following number in BrandMeister under My Devices  = 655xxxx05 which displayed a green hart as well as 655xxxx which also displayed a green hart.  In other words this caused all sorts of mayhem albeit the DMR Repeater not working as it should.

 

I removed the 05 and rebooted the repeater and wallah the repeater came to life and work as it should. As mentioned before "The solution to the problem was quite easy and mainly overlooked.". The error hiding away until I found it. I am now able to use both DMR Radio to talk to the repeater without any hassles.  The repeater can also be linked to the ZS Link Hub providing a further extension of the ZS Link Network.  With this problem sorted let's move on to the next "glitch".

(Click on image for larger view.)

The Huawei B525 Router used with the DMR Repeater all of a sudden could not access the Internet.

Okay I must admit that on of the computer I  use in the Shack is rather ancient.  It runs Window 7.  Now I mainly use this computer to monitor nodes, repeaters, bridges etc.  I have 3 routers in my shack running different equipment on them. The Huawei B525 Router is used with the DMR Repeater.  The router is setup correctly and was working correctly when all of a sudden I would receive the following error message after a reboot of the machine.  

"no internet access DNS server isn't responding"

Now I did not have any time to go into a detail setup / search through the firmware of the computer.  I found the following solution to the issue.

To fix "DNS server isn't responding," restart your router and modem, clear your browser/system cache, and try flushing DNS via Command Prompt (ipconfig /flushdns). If issues persist, switch to a public DNS server (like Google’s 8.8.8.8 and 8.8.4.4), update network adapter drivers, or temporarily disable firewalls/VPNs. 

Quick Fixes for DNS Errors

• Restart Hardware: Power-cycle your router and modem (unplug for 30 seconds).
• Flush DNS Cache: Open Command Prompt as administrator and type ipconfig /flushdns.
• Switch DNS Servers: In network settings, change IPv4 DNS to 8.8.8.8 (Preferred) and 8.8.4.4 (Alternate).
• Disable Third-Party Antivirus/VPN: These can often block DNS requests.
• Check Physical Connections: Ensure Ethernet cables are secure, or try a different cable.
• Update/Reinstall Network Adapters: Open Device Manager, find your network adapter, and check for driver updates.
• Disable IPv6: Sometimes switching to IPv4-only fixes connectivity.

(Click on image for larger view.)

Needless to say the only solution that worked for me was the following: (See image above) 

Go to Control Panel and select Network and Internet - Network and Sharing Center.

Click on Local Area Connection

Window will open - Local Area Connection Status  Window will open - Local Area Connection Properties

Click on Properties - Double click on - Internet Protocol Version 4 (TCP - IP4)

Internet Protocol Version 4 (TCP - IP4) Properties window will open.  

IP Address obtain Automatically must be selected

Select:  Use the followng DNS Sever Addresses

Enter the following addresses:

Preferred DNS Server:  8.8.8.8.

Alternative DNS Server:  8.8.4.4.

Click OK and OK and Close

Reboot the computer and after restarting your Internet will be back up and working!!

Note:  Yes there is other solutions to this problem but I used the above that was easy to setup and implement. 

(Click on image for larger view.)

I used my Windows computer to program the TYT MD380 HT radio in the past.  This time around I could only read the radio but the CPS Firmware refused any other command and would crash as soon as I enter any information.

Onto the final "glitch".  I use stock standard firmware and cable to program my TYR MD380 HT Radio.  This time around I received an error in Chinese stating that Microsoft will be looking for a solution.  Now we all know running a Window 7 machine will result in no feedback, response or support.  I expected the problem to be driver related and removed the old drive and install the latest version.  Well still no joy.  Scratching around the Shack I found my old Windows XP laptop which already had the CPS and driver installed.  Success on the first try.  The radio was read and write with the necessary changes without any issues.

Moral of the story -  Never get rid of your old computers.  They can help you out when the newer one's are stubborn and "glitchy".

With the three issues solved the DMR Repeater is now operational in the Mossel Bay Area.  Unfortunately the cooling fans are making quite a bit of noise and will have to be replaced.  I ordered two fan speed controller and as soon as they arrive I will fit the new fans on the repeater.

Finally: I trust that this article would be of some benefit to those who might experience the same issues.  For many this might be general knowledge but for others it might be helpful.  I have quite a few "tricks up my sleeve" in the future regarding this repeater.  If you interested in how one can use this repeater to it's full potential then do not miss Part 4 and Part 5.  Even better come and join in the fun!

Down Memory Lane: Koffie Drink - Reboot Amateur Radio WhatsApp Groep – 22 Junie 2019 – Root Koffie op George.

Die afgelope Saterdag, 22 Junie 2019 om 9vm was weer ‘n genotvolle en suksesvolle byeenkoms vir radio amateurs in George by Root-Koffie.

Die “venue” was uiters geskik, aangenaam en ideaal vir gewone asook koue dae met ‘n swart gietyster stofie wat die lokaal net op die regte hittevlak gehou het. Baie dankie aan Francois ZS1Q en Danie ZS1DBJ wat die nodig aanvoerwerk en reelings getref het om by Root te kon koffie drink.

Die byeenkoms was bygewoon deur 12 radio amateurs die meeste nog sedert die totstandkoming van die Reboot Koffie Drink. Die Reboot Amateur Radio WhatsApp groep en sy aktiwiteite is beskikbaar vir alle- en voornemende radio amateurs in Suid Afrika. Sluit gerus by ons aan op die groep en wees deel van hierdie dinamiese groep radio amateurs.

Ek het besluit om slegs ‘n kriptiese oorsig te lewer van die geleentheid. So as jy nie die geleentheid kon bywoon nie gaan jy ongelukkig nie die fynere detail kry oor die samekoms nie. Die rede vir die besluit is heel eenvoudig. Ons soek almal in lewende lywe by die Reboot Koffie Drink. Woon die geleenthede by en kry al die fynere detail tydens die samekoms. Ek praat nie eers van die goeie gesindheid en kameraderie by die byeenkomste nie. Die samekoste het hulself nou al bewys as nie amateur radio polities van aard nie en met geen persoonlike menings verskille of onaangenaamhede nie!! 

Hier volg ‘n kort opsomming van Saterdag se gebeure:

Nadat almal die nodige verslaafde koppie koffie aangekoop het en hulle plekke ingeneem het, het ons sonder enige seremonie of formaliteite die byeenkoms afgeskop, maar meer hieroor later.

Die volgende persone was teenwoordig: Dave ZR1OAC, Hennie ZS1IK, Willie ZS2CC, Llewellyn ZS003, Saney ZR1S, Johann ZS2BVD, Andre ZS1AFB, Johan ZS1WD, Conrad ZS1KG, Francois ZS1Q, John ZS1ZR en Johan ZS1I.  Die volgende persone het verskoning aangebied: Thys ZS1TBP, Kobus ZS2BBB, Nick ZS1N, Jimmy ZS1RB, Danie ZS1DBJ, Abe ZS1ZS en Mari ZS1MEH.

Na verwelkoming is almal teenwoordig bedank vir die moeite wat hul gedoen het om die byeenkoms by te woon in die gure weersomstandighede wat toe nou ook nie so onaangenaam was nie. Ek het besluit dat daar geen Reboot Amateur Radio aangeleenthede bespreek gaan word nie. Die Reboot Koffie Drink is immers ‘n informele geleentheid en nie ‘n formele vergadering van een of ander aard nie. Daar is dan ook sommer dadelik weggespring met die gewilde “Rondomtalie/Round Robin” mini lesings/demonstrasies en lekker gesels. Net soos in die verlede het elkeen wat kom koffie drink het gretig deelgeneem aan die Rondomtalie self die nuwe en ou gesigte wat die eerste keer teenwoordig was.

Hier volg ‘n kriptiese samevatting tov van die “Rondomtalie/Round Robin”:

•  Francois ZS1Q George – Amateur radio almanak van vroeer jare - PEARS VHF/UHF Analoog Kompetisie deelname vanuit die Suid Kaap. 
•  John ZS1ZR George – John was verantwoordelik dat die manne se lagspiere oefening gekry het. Dankie daarvoor John dit het die manne sommer lekker laat lag en ons kort van meer lag – VHF Radio in die Suid Kaap. 
• Johan ZS1I Mosselbaai – Saambring van 2m/70cm Draagbare Radios -Analoog UHF 70cm Eksperimentele 10mW baken – Propogasie 2m/70cm. 
• Hennie ZS1IK George – Oorsig van Amateur Radio Aktiwitiete – 2m Mobiele Werking – Luister vir Hennie op die 145.700 Herhaler. - Toevoeging tot die Reboot Amateur Radio WhatsApp groep. 
• Willie ZS2CC George - Aktiwiteite op die HF bande – 80m Band is huidiglik “kookwater” dag en nag – 6m Band openinge – 11m Band openinge - HF Verslag. 
• Llewellyn ZS003 – Reboot se IT Spesialis – Fibre Internet – Topografie van Internet Torings – Reikafstande van WiFi – WiFi tussen George en Mosselbaai – All things Internet -80dB Seine – Vrae oor WiFi. 
• Johann ZS2BVD George - Raspberry PI T-Hemp logo en Park-Run - Andre ZS1AFB ontmoet Johann en vandag sit hulle altwee aan die Reboot Koffie Drink Tafel - Sterrekunde, Teleskope, Elektronika, Mikrogolf Tegnologie, Raspberry Pi en Arduino Projekte en sommer vele meer. Johan bespreek 3 projekte nl: Raspberry Pi 3+ Mini Rekenaar en 3D drukker kassie; 4 “poort” 24v na lae spanning omsetters ook gemonteer in 3D drukker kassie en die Radio Amateur se beheerde kookpan stelsel - Sien fotos in die verband. 
• Saney ZR1S Wilderness - 40m Beacon Engineer and Care Taker - Willie ZS2CC Beacon Controller (Good laugh) – Summary of the 40m Beacon characteristics – The beacon is truly a “Green” Beacon – running of solar panel power – Unfortunately the beacon causes RF Pollution, HiHi. - which is fortunately a very good thing!! 
• Andre ZS1AFB George – Amateur Radio in Australia – Toekomstige amateur radio planne vir die Suid Kaap – Herhalers en herhalernetwerke – Mikrogolf skottels en die Ghz bande – Toekomstige onbeperkte perseel beskikbaar vir Reboot Koffie Drink aktiwiteite – Andre die PR van die dag toe hy lid van die publiek inlig oor amateur radio na die byeenkoms. Dankie Andre!! Sien die draagbare radio ding het toe tog gewerk!! 
• Johan ZS1WD Blanco – Johan (ZS1Wasgoed Draad) is terug na ‘n tydsverloop van meer as 20 jaar!! Nog besig om weer sy stasie aan die gang te kry – Afgetree – Johan bied gratis koffie aan vir alle rebooters by sy huis. Al voorwaarde is dat hulle sy gras moet sny en tuin bewerk - Dis nou ‘n bargain – HF Radio asook 2m simplex en herhalers – Johan reeds aktief op die 145.700 George herhaler. Kyk gerus uit vir Johan. 
• Conrad ZS1KG Blanco - Werksverpligtinge – Weersatelliet prente en ontvangs – weersatelliet grond stasie - Conrad dankie dat jy gekom het al was dit tydens die Rondomtalie. Die feit is jy was daar en dit is wat saak maak. Jammer jy is nie in die groeps foto nie maar ek het dit eers later agter gekom. 
• Dave ZR1AOC Mosselbaai – Digitale Radio - Peanut Dstar – Verstelling en toets handstel van Andre ZS1AFB tydens byeenkoms – Sukses die radio is nou ten volle operasioneel – Nou dit is wat Reboot Koffie Drink lekker maak. Sommer gou gou help die manne mekaar. Dankie, Dave!  

Soos gesien kan word is daar vele aspekte van amateur radio bespreek en gedemonstreer. Waar kry jy nog soveel inligting en kennis in twee ure se tyd? 

‘n Groot dank ook aan Thys ZS1TBP wat bereid was om die 145.700 George Herhaler te beman en te monitor voor en tydens die koffie drink sessie. Thys ek weet jy sou graag teenwoordig wou wees maar het jy ‘n groter rol verfil op die herhaler. Verskeie kontakte is met Thys gemaak voor en tydens die geleentheid. Dankie Thys!! 

Iets wat ek opgemerk het tydens die Koffie Drink wat ander dalk nie van weet nie. Ons het die voorreg gehad en dit is ook ‘n eerste in die Suid Kaap om twee pa’s en twee seuns by ‘n Koffie Drink saam op dieselfde tyd en plek teenwoordig te gehad het. Wat ‘n voorreg!! Willie- ZS2CC en Llewellyn Hewitt ZS003 (pa en seun). Johan- ZS1WD en Conrad Scheepers ZS1KG (pa en seun) 

Teen 11 uur se kant was dit huistoe gaan tyd gewees. Weereens ‘n baie en genotvolle koffie drink sessie gewees. Weereens ‘n groot en hartlike dank aan ‘n ieder en elk wat die byeenkoms bygewoon en aan die Rondomtalie deelgeneem het. Een persoon maak nie die byeenkoms nie maar dit is julle wat die moeite doen on dit by te woon wat die geleentheid ‘n groot sukses maak. Sonder julle deelname sou die koffie drink nie suksesvol gewees het nie. 

Die volgende Reboot Koffie Drink sal gehou word te Mosselbaai op die 20 Julie 2019 om 9vm. Die plek van byeenkoms sal mettertyd aangekondig word. Teken asb nou al die datum aan in julle dagboeke dat daar nie botsende belange is nie en dat jy die geleentheid kan bywoon. 



73 

Johan ZS1I, Mosselbaai 
24 Junie 2019

Fotos:  (Klik op fotos om te vergroot.)

Hennie ZS1IK, Willie ZS2CC en Llewellyn ZS003

                                        Hennie ZS1IK, Willie ZS2CC en Llewellyn ZS003

Johann ZS2BVD, Saney ZR1S, Andre ZS1AFB en Johan ZS1WD

So kuier die manne

  Francois ZS1Q en John ZS1ZR

Saney ZR1S, Andre ZS1AFB, Johan ZS1WD, Francois ZS1Q en John ZS1ZR

  Middel:  Dave ZR1OAC

Die Raspberry Pi Rekenaar in 3D kassie

So lyk die Raspberry Pi uit sy kassie

Die 24 volt na laer spanning omsetters in 3D kassie

Die 24 volt omsetter verwyder uit sy 3D kassie

Die Amateur Radio beheerde braaipan stelsel.  Arduino Nano ens.

Kontrole kas van die braaipan beheerde stelsel

Ai dis darm maar lekker!!

Analoog UHF 70cm Eksperimentele 10 mW baken

   

Zayn ZR3VO - AllStar Portable / Mobile Node Project

Image: ZR3VO Portable / Mobile AllStar  Node.  (Click on image for larger view.)

Zayn informed me that he is busy building an AllStar Portable / Mobile Node and a DMR Mobile Hotspot which he will be using whenever the need arises.  In the first article we will be looking at the AllStar Portable / Mobile Node and in the second article we will be looking at his DMR Mobile  / Portable Hotspot.

Now what on earth is a Portable / Mobile AllStar Node?

A

DIY mobile AllStar node is a custom-built, portable device that uses a low-power computer, a radio interface, and amateur radio equipment to connect to the global AllStarLink network via the internet  (often a mobile hotspot). This setup allows amateur radio operators to communicate with thousands of other nodes and repeaters worldwide using their handheld or mobile radios, essentially acting as a personal gateway or "hotspot". 

The "DIY" aspect means the operator assembles the components themselves, which is a common and cost-effective approach within the ham radio community, as opposed to buying a pre-built commercial unit. 

 

Key Components:

 

A typical DIY mobile AllStar node requires the following main components: 

• A Computing Device: A small, low-power computer, most commonly a Raspberry Pi (Pi 3 or Pi 4 are popular choices). It runs a Linux-based operating system with the AllStarLink software, often a pre-configured image like HamVoIP.
• A Radio/Audio Interface: A small circuit board or device that connects the computer's USB port (via a C-Media CM108/CM119 sound IC) to the radio's audio input/output and Push-to-Talk (PTT) lines. Pre-made interfaces like the DMK URIx or Masters Communications DRA boards are available, or advanced users can build their own from scratch.
• A Node Radio: A simple, often inexpensive, UHF or VHF radio (e.g., a Baofeng UV-5R or similar) dedicated to the node. This radio receives signals from your personal handheld radio and transmits audio back from the network.
• Power Source: For a mobile setup, a portable battery bank or a buck converter for a vehicle's power system is used.
• Internet Connection: The node needs internet access, which can be provided by Wi-Fi or by tethering to a mobile phone hotspot.

Functionality:

 

The setup works by:

1. Receiving an FM signal from your handheld radio on a specific frequency.
2. Converting the audio to digital data via the sound interface and the Raspberry Pi.
3. Transmitting that digital data over the internet to other AllStar nodes.
4. Receiving internet audio from other nodes.
5. Converting the digital audio back to an FM signal for transmission to your handheld radio.

This allows for seamless communication over vast distances, bridging the gap between local RF (Radio Frequency) coverage and the global internet network. 

 

Building Your Own:

 

To build a DIY node, you would typically follow these general steps:

1. Register for an AllStar node number on the AllStarLink website.
2. Gather the necessary hardware components.
3. Install the AllStar software (like HamVoIP) onto the Raspberry Pi's SD card.
4. Wire the radio to the interface board (if necessary).
5. Configure the software settings, including audio levels and network parameters, often using a program like PuTTY for remote access.
6. Test the node using the "Parrot mode" feature.

There are many online guides and YouTube tutorials available to walk users through the process.

 

Information regarding the ZR3VO AllStar Portable / Mobile Node:

 

Call Sign:  ZR3VO

Frequency:  145.350 Mhz

CTCSS:  88.5 Hz

Node Number: 46615

Location: Orania

Site: Orania Township

Affiliation: ZS Link Network Group

 

The "inauguration"   of the node took place recently He use the node regularly while mobile and even portable. The node is functioning well and is definitely a great asset when going mobile or portable.  Congratulations on constructing a useful and effective node, Zayn. 

Images:  Click on images for larger view.

 

 

How do I save TalkGroups (TG) in DroidStar?

The articles relating to Droidstar resulted in the following question being asked:  " How do I save TalkGroups (TG) in DroidStar?"

Saving talkgroups in DroidStar involves entering them in the TGID field on the main screen, which generally saves them as part of your application settings when you close the app. To ensure they are permanently associated with your DMR ID, you should configure static talkgroups in your BrandMeister SelfCare profile, as DroidStar functions as a hotspot. 

How to Save/Set Talkgroups in DroidStar

• Enter the TGID: On the main screen, locate the TGID box, enter the talkgroup ID number, and ensure you transmit (PTT) while that ID is entered to link it.
• Save Settings: Once all your settings (Callsign, DMR ID, Password, TGID) are entered, exiting the program properly should save these in the app's configuration, according to user experiences.
• Static Talkgroups (Best Method): To prevent losing your talkgroup, log in to the BrandMeister SelfCare website and add the desired talkgroups to your hotspot configuration. This ensures that DroidStar stays connected to them, similar to a physical DMR radio.
• Unlinking: To disconnect from a talkgroup, you can "Key 4000" (Group Call) for one second, which is a common practice to unhook from a previous TG.

Key Tips

• Initial Setup: Ensure you have your BrandMeister security password entered in the settings, not your login password.
• Testing: Use Talkgroup 91 (Brandmeister Worldwide) for testing functionality.
• Host Selection: Select a valid DMR host (e.g., BM_6551_South_Africa) in the host field.

Give the above a try!!

Enjoy!!