If you’ve spent any time in the amateur radio packet world, you know the landscape. Most of the software was written in the early 2000s, configured via INI files, and runs best when you squint at it the right way. Direwolf came along and meaningfully improved the software TNC situation. But the broader stack (decoding, digipeating, iGating, monitoring) still required cobbling together multiple tools, and none of them came with anything resembling a modern user interface.

Graywolf changes that. It’s a complete APRS station in a single binary: software modem, digipeater, iGate, and a browser-based web UI, all bundled and working together out of the box. It’s written by Chris Snell, NW5W, and it’s open source under GPL-2.0. As of June 2026, it’s at version 0.13.15 with 100 releases published and an active development pace.

What It Actually Is

Graywolf isn’t a front-end wrapper around Direwolf. It has its own modem, written from scratch in Rust. The AX.25 decoding, APRS operations (beacons, digipeating, iGating), and the REST web API are handled by a service written in Go. The web frontend is built in Svelte.

The Rust modem is a port of the AFSK demodulator from Direwolf, originally written by WB2OSZ. It incorporates decision-feedback AGC and hard-limiter correlator techniques credited to Ion Todirel (W7ION) from his libmodem project. These aren’t just software engineering choices. They’re the reason the modem performs the way it does, and they represent real signal processing expertise applied to a practical problem.

The Benchmark Numbers

This is where Graywolf makes its case plainly. The WA8LMF TNC test CD is the standard benchmark for software TNCs. Here’s how Graywolf compares to Direwolf running in its best mode, which is -P AD+:

Graywolf beats or matches Direwolf on every single track. Not by massive margins, but those aren’t the point. It achieves this performance at roughly 5% of a Raspberry Pi 5’s CPU, while Direwolf in its most effective mode is considerably heavier. On an actual Raspberry Pi 5, Graywolf’s modem runs at about 19% of a single CPU core. For a station that’s meant to run 24/7 on low-power hardware, that’s a meaningful difference.

The benchmarks are reproducible. The repo includes a bench.sh script so you can verify this yourself.

Installation

Graywolf ships as a single binary. There are no external dependencies to manage, no daemon prerequisites, and no separate modem process to configure.

Packages are available for:

• Debian/Ubuntu via APT
• Fedora/RHEL via RPM
• Arch Linux via AUR
• Windows with an installer
• macOS as binaries

Architecture support includes x86-64 and ARM, including Raspberry Pi. As of version 0.13.15, the build process also restores support for armv6 and 32-bit Pi targets, which had been broken. The SQLite database stores all configuration, so there’s no flat config file to maintain. Setup is handled entirely through the web UI.

The Web Interface

Graywolf is managed through a browser. The interface is responsive and works on both desktop and smartphones, which matters when you’re managing a station remotely from a phone.

The interface includes a live packet stream, a full map view, and a messaging interface. Configuration of all station parameters (modem settings, PTT method, beacon intervals, digipeater paths, iGate filters, and more) is done through the browser, not a text editor.

The Live Map

The map deserves its own mention because it’s not just a stripped-down APRS viewer. Graywolf describes it as “a private aprs.fi for your station,” and that’s accurate in scope. It supports:

• Real-time packet display with station trails
• Digipeater path visualization
• Weather overlays
• A private vector basemap
• Offline map downloads by state, province, or country

The offline map capability is practically useful. If you’re operating at a remote site, during an emergency activation, or in an area with unreliable internet, being able to pre-download map tiles for your region means the map still works.

Messaging

APRS messaging in Graywolf works as an SMS-style interface with delivery status and unread badges. Under the hood it supports:

• Auto-ACK and retry on direct messages
• Tactical callsigns: you can message groups using callsigns like GRAYWOLF or AMIGOS for net operations
• RF-first delivery with APRS-IS fallback: it tries the radio path first and falls back to internet gating if the RF path fails
• Long messages up to 200 characters: the standard APRS message limit is 67 characters, so this is a significant extension for stations that support it

PTT Methods

One of the more practical aspects of Graywolf is how many PTT methods it supports out of the box, covering virtually every common way to key up a radio from a computer:

• Serial RTS/DTR: works with Digirig and standard USB-serial adapters
• CM108 USB HID GPIO: works with AIOC and homebrew sound card adapters
• Linux GPIO: direct GPIO control on Raspberry Pi, BeagleBone, and similar boards
• Hamlib rigctld: CAT control for radios that support it

Most APRS software supports one or two of these. Supporting all four in the same package means Graywolf works with the hardware you already have.

Digipeater

The digipeater implementation is full-featured:

• WIDEn-N path handling: the standard APRS digipeating path format
• Preset-driven configuration: presets for common roles like fill-in digi or wide-area digi
• Duplicate suppression: prevents re-transmitting packets already heard from other digipeaters
• Per-path filtering: control which packets get digipeated based on path

This is the kind of configuration that matters for anyone setting up a serious digipeater node rather than just a home station.

iGate

The iGate handles both directions:

• RF to APRS-IS: packets heard on RF are uploaded to the APRS-IS network
• APRS-IS to RF: packets from the internet are gated down to RF for local delivery

Configurable filters let you control what gets gated in each direction. The logs include packet origin tracking so you can see where each packet came from and whether it was gated. As of v0.13.15 (PR #202), the iGate exposes RF-to-IS gate reasons for KISS client TX, meaning you can see exactly why a packet was or wasn’t gated.

TNC Interfaces

Graywolf speaks the protocols that other packet software expects:

• KISS TNC: TCP built in, serial via tnc-server
• AGWPE TCP: the Packet Engine interface used by Winlink, UI-View, and many others

This means you can use Graywolf as the TNC back-end for other software while still using Graywolf’s own interface for monitoring and configuration.

Actions

Actions are a less-common feature that’s worth understanding. They let you trigger scripts or webhooks remotely by sending specially-crafted APRS messages to your station. Supported trigger types include:

• Shell scripts
• PowerShell scripts
• Webhooks

Actions can be secured with one-time passwords using the same TOTP standard as Google Authenticator and 1Password. A recent commit adds a TOTP verifier with a replay ring, meaning the same OTP can’t be reused, which closes a basic replay attack vector.

The practical uses here are real. Triggering a generator start, alerting monitoring systems, or running a check-in script via an APRS message from a mobile radio is the kind of capability that makes sense in emergency communications contexts.

Observability

For a station that runs unattended, knowing what it’s doing matters:

• Prometheus metrics: scrape Graywolf’s metrics into whatever monitoring stack you’re using
• SQLite packet logging with search: all heard packets are logged and searchable
• Live packet stream in the web UI: real-time view of everything the station is hearing

The Prometheus integration is unusual for amateur radio software. It means Graywolf fits into professional monitoring setups (Grafana dashboards, alerting rules, the whole ecosystem) without any custom work.

Android

There’s an Android application in active development. Recent commits show USB KISS TNC support added, a watchParentDeath mechanism to properly cancel the app context when the parent process exits, and a CI pipeline using Fastlane for track promotion and Play Store listing uploads. This is real software engineering work, not a proof-of-concept port.

The Project in Context

Graywolf sits at version 0.13.x with 100 public releases and four contributors. It has 123 stars and 11 forks on GitHub. The commit history shows consistent, regular work across multiple releases per month, and the changelog reflects real user-reported issues being fixed. The armv6 build regression, for example, was reported as issue #199 and fixed in five days.

The project has a Discord community, a published handbook, a Known-Working Configurations list with community-submitted hardware setups, and a public map of currently active stations.

This is software built to be used, not just released.

Who It’s For

Graywolf makes sense for:

• Home stations that want a complete APRS setup without managing multiple tools
• Digipeater and iGate operators who want modern configuration and monitoring
• Emergency communications groups that need reliable, maintainable software on Raspberry Pi hardware
• Experimenters who want to run their own private APRS network with a real-time map

If you’re currently running Direwolf with a collection of scripts, config files, and manual log inspection, Graywolf is a direct upgrade. The modem performance is better, the CPU footprint is lower, and everything is accessible through a browser instead of a terminal.

The latest release is available at the Graywolf GitHub repository. The handbook covers installation, configuration, and the REST API reference in full.

The post Graywolf: A Modern APRS Station That Actually Keeps Up With the Hardware It Runs On appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

For years, APRSdroid has been one of the most widely used APRS applications available for Android. It provides a practical way for amateur radio operators to access the Automatic Packet Reporting System (APRS) from smartphones and tablets, whether through RF, APRS-IS, Bluetooth TNCs, or various radio interfaces.

While the official APRSdroid project remains a popular choice, the NA7Q Edition takes the application significantly further. Developed and maintained by NA7Q, this customized build introduces features that many APRS operators have requested for years, including full digipeating, two-way IGating, Mic-E support, advanced offline mapping capabilities, Bluetooth Low Energy support, DigiRig compatibility, and enhanced radio control functions.

The project is actively developed, and new functionality is continuously added. As a result, some features may still be under development or subject to change between releases.

Official project page:

https://www.na7q.com/aprsdroid

Downloading APRSdroid NA7Q Edition

Before installing the NA7Q version, it is recommended to remove any previously installed official APRSdroid version to avoid conflicts.

APRSdroid APK

Download the latest APRSdroid NA7Q build:

https://www.na7q.com/aprsdroid

Mobile HUD APK

The Mobile HUD companion application is available separately:

https://www.na7q.com/aprsdroid

The Mobile HUD application remains experimental and results may vary depending on device hardware and Android version. Current testing indicates that landscape orientation provides the best user experience.

Source Code

The project source code is available through GitHub:

https://github.com/na7q

One important note is that the APK does not include the Google Maps API. Users who require Google Maps functionality can build the application themselves and add their own Google Maps API key.

Android Storage Permissions and Offline Maps

Beginning with Android 11, Google introduced significant changes to storage access permissions. These changes impact applications that need direct access to map files stored on internal or external storage.

To enable offline maps in APRSdroid NA7Q Edition:

1. Open APRSdroid Settings.
2. Navigate to the OSM Maps section.
3. Select Grant Storage Permissions.
4. Approve the request for full file access.

Without this permission, APRSdroid cannot access locally stored mapping databases.

This step is required for Android 11 and newer devices.

Offline Mapping Support

One of the largest improvements in the NA7Q build is its extensive offline mapping support.

The official APRSdroid implementation relies heavily on online map services. While suitable for urban environments with reliable cellular coverage, online maps become problematic during emergency communications, backcountry travel, search-and-rescue operations, and disaster response.

The NA7Q version addresses this limitation by supporting:

• MBTiles maps
• Mapsforge V3 maps
• OpenStreetMap offline databases

Users can operate entirely without an internet connection once maps are downloaded.

To use offline maps:

1. Open Settings.
2. Navigate to OSM Maps.
3. Select OpenStreetMap.org as the map viewer.
4. Enable Offline Mode.
5. Choose your downloaded map file.

When Offline Mode is disabled, APRSdroid will continue using online OpenStreetMap servers.

Supported Map Formats

MBTiles

APRSdroid supports MBTiles databases that contain standard raster tiles stored as:

• PNG
• JPG

Vector MBTiles and PBF files are not currently supported.

This makes the application compatible with map sets generated for platforms such as:

• Gaia GPS
• OpenStreetMap tile downloads
• Custom mapping projects

Mapsforge V3

A newer addition to the project is Mapsforge V3 support.

Mapsforge maps provide vector-based rendering, resulting in:

• Smaller file sizes
• Faster rendering
• Improved zoom performance
• Better offline usability

This is particularly useful for operators carrying large regional maps on mobile devices with limited storage.

Downloading Maps

Obtaining suitable offline maps can often be the most challenging part of configuring APRS software.

To simplify this process, NA7Q provides several mapping tools.

OSM Map Maker for Windows

A Windows-based application that downloads OpenStreetMap data and generates APRSdroid-compatible map databases.

Download:

https://www.na7q.com/aprsdroid

Recommended usage:

• Enter a specific location.
• Examples:
  • Portland, Oregon
  • Oregon, USA
  • Texas, USA

The more precise the location, the better the resulting map selection.

Python OSM Map Maker

A cross-platform alternative written in Python.

Compatible with:

• Windows
• Linux
• macOS
• Android

Download:

https://www.na7q.com/aprsdroid

This version provides greater flexibility and is useful for operators who prefer scripting or automation.

Multi-Map Maker

The Multi-Map Maker expands map generation by supporting additional map providers.

Available map sources include:

• Google Maps
• Google Satellite
• Google Terrain
• OpenStreetMap
• USGS
• USFS
• Canada Topographic Maps
• Thunderforest
• MapBuilder Light
• MapBuilder Dark

This allows operators to choose the most appropriate cartography for their operating environment.

Examples:

• Backcountry navigation may benefit from USFS maps.
• Search-and-rescue teams may prefer topographic layers.
• Mobile operators may prefer simplified road maps.

Download:

https://www.na7q.com/aprsdroid

Map Viewer

The Map Viewer utility allows users to preview available map styles before downloading large datasets.

This is particularly useful because:

• Not every map provider covers every region.
• Some providers restrict maximum zoom levels.
• Different styles emphasize different geographic features.

Download:

BBBike Mapsforge Generator

For operators who prefer Mapsforge vector maps, BBBike provides custom map generation.

Website:

https://download.bbbike.org/osm

Users can create custom vector map regions tailored to their operational area.

Understanding Zoom Levels

Map size increases dramatically as zoom levels increase.

NA7Q recommends:

• Zoom 13–14 for large states or regions.
• Higher zoom levels only when necessary.

Example:

A Washington State map generated at Zoom 15 can range between approximately 2 GB and 5 GB depending on the selected map source.

This is an important consideration for operators using limited storage devices.

Included World Map

For users who simply want to begin testing immediately, NA7Q provides a starter world map.

Coverage extends to approximately Zoom Level 6 and serves as a useful global reference layer.

World Map:

https://www.na7q.com/aprsdroid

Features Added Beyond Official APRSdroid

The biggest reason many operators switch to the NA7Q Edition is the extensive feature set.

These additions transform APRSdroid from a simple APRS client into a more complete mobile APRS platform.

Full Digipeater Support

One of the most requested capabilities is digipeating.

The NA7Q build supports:

• Direct digipeating
• Full digipeating

This enables Android devices to participate more actively in APRS RF networks.

Two-Way IGating

Most APRS applications provide limited APRS-IS connectivity.

NA7Q Edition supports:

• Receive from APRS-IS
• Transmit to APRS-IS
• Two-way IGating

This allows traffic to flow between RF and internet networks.

For operators building portable APRS infrastructure, this is a significant enhancement.

Flexible RF and APRS-IS Routing

Users can choose:

• RF only
• RF plus APRS-IS
• RF with IGating

This flexibility allows the station to be tailored for:

• Mobile operation
• Fixed stations
• Emergency deployments
• Field events

Mic-E Compression

Mic-E remains popular because of its compact packet format.

The NA7Q build includes:

• Mic-E encoding
• Mic-E status support
• Mic-E emergency status

This improves efficiency while maintaining compatibility with APRS infrastructure.

Standard APRS Compression

In addition to Mic-E, compressed position formats are supported.

Benefits include:

• Smaller packet sizes
• Reduced channel usage
• Improved network efficiency

Bluetooth Low Energy Support

Bluetooth Low Energy (BLE) support is nearing completion and has reached a stable stage of development.

Advantages include:

• Lower power consumption
• Improved battery life
• Better compatibility with modern hardware

This is particularly important for portable and mobile APRS operations.

DigiRig Support

DigiRig has become one of the most popular interfaces for digital amateur radio communications.

The NA7Q build includes native DigiRig compatibility, simplifying setup for operators using:

• HTs
• Mobile radios
• Base stations

Radio Control Features

Expanded radio control support is included for various manufacturers.

Compatible systems include:

• Vero
• BTech
• Radioddity

Additional radio models may be supported depending on firmware and interface configuration.

Enhanced Station Information

Several usability improvements have been added.

The Station Viewer now displays:

• Speed
• Course

These fields provide immediate situational awareness when tracking mobile stations.

Hub Log Improvements

The Hub Log can sort stations by:

• Distance
• Most recently heard

This makes it easier to identify nearby activity and monitor local APRS traffic.

Metric and Imperial Units

Users may select their preferred measurement system.

Supported options include:

• Metric
• Imperial

This improves usability for international operators.

Hardware Acceleration Control

A toggle has been added to disable hardware acceleration.

This can help resolve compatibility issues on devices experiencing graphical rendering problems.

Mobile HUD

The Mobile HUD companion application aims to provide a heads-up display style interface for APRS operations.

Current status:

• Experimental
• Under active development
• Best used in landscape orientation

The concept is promising for:

• Mobile APRS tracking
• Navigation support
• Vehicle installations

As development continues, additional functionality is expected.

Development Roadmap

NA7Q continues to actively develop the project.

Planned enhancements include:

APRS Parser Improvements

More accurate packet decoding and interpretation.

Weather Readability

Improved display of APRS weather data.

Altitude Display

Altitude information added to the Hub Log.

Full Screen Mode

Better utilization of modern smartphone displays.

Integrated Mobile HUD Access

Direct access from the APRSdroid menu.

BLE Stability Improvements

Fixes related to startup crashes when no Bluetooth Low Energy device is selected.

APRS Query Commands

Support for commands such as:

?APRSM

and related APRS messaging queries.

Mic-E Cleanup

Additional refinements to Mic-E processing and status handling.

Beacon Type Selection

A simplified list-based interface for choosing:

• Mic-E
• Compressed
• Uncompressed

beacon formats.

Mic-E Emergency Alerts

Visual alerts for emergency status packets.

Path Tracking

Display whether stations were:

• Directly heard
• Digipeated
• Relayed

This will improve network visibility and troubleshooting.

Final Thoughts

APRSdroid NA7Q Edition represents one of the most ambitious APRS Android projects currently available. Rather than focusing solely on APRS messaging and tracking, the project expands the application into a comprehensive field communications platform.

The standout features are unquestionably:

• Full digipeating support
• Two-way IGating
• Offline MBTiles maps
• Mapsforge V3 support
• Mic-E functionality
• Bluetooth Low Energy compatibility
• DigiRig integration
• Advanced radio control

For operators who rely on APRS in remote areas, emergency communications, off-grid environments, search-and-rescue activities, or mobile deployments, these additions solve many of the limitations found in traditional APRSdroid installations.

Because development remains active, users should expect occasional bugs and unfinished functionality. However, the pace of development and the growing feature set make APRSdroid NA7Q Edition one of the most capable APRS applications available for Android today.

Resources:

Project Page:
https://www.na7q.com/aprsdroid/

Patreon:
https://www.patreon.com/na7q

GitHub:
https://github.com/na7q

BBBike Maps:
https://download.bbbike.org/osm/

The post APRSdroid NA7Q Edition: The Most Feature-Rich APRS Client for Android appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

If you open https://status.aprs2.net/ right now, you see a live dashboard for the APRS-IS Tier 2 network. APRS-IS is the internet backbone for the Automatic Packet Reporting System. It takes position reports, weather data, text messages, and telemetry from amateur radio stations worldwide and routes them across the internet in real time.

Tier 2 is a volunteer network of servers that filter and distribute APRS traffic so the Core servers do not get overloaded. There are hundreds of T2 Leaf servers in every country. They connect to T2 Hubs, and the hubs feed the Core.

Why should you care about the operating system these servers run? Because APRS is used for real emergencies. Search and rescue teams track assets with it. Weather stations from the Citizen Weather Observer Program feed data to the US National Weather Service through it. Satellites digipeat through it. If a server goes down, packets get lost. Uptime of 99.9 percent is not a marketing number. It is an operational requirement.

Japan’s T2 servers run FreeBSD. Most other countries run Linux. This article explains why, using real data from status.aprs2.net, the history of BSD in Japan, and the technical strengths of FreeBSD’s network stack.

1. Look At The Data First: What Does status.aprs2.net Actually Show?

T2 Hubs:

Out of four hubs, only T2HUB1 runs FreeBSD. It also has the best score. Lower is better. T2HUB3 is down.

T2 Leafs in Japan:

Three of the four main Japanese T2 servers run FreeBSD. T2HAKATA has an http problem, but T2OSAKA and T2FUKUOKA are perfect. Score in the 800 range. Availability 100.00 percent.

Now compare with other countries. Germany T2ERFURT runs Linux. UK T2UK runs Linux. USA T2CAWEST runs Linux. Brazil T2BRAZIL runs Linux. FreeBSD only shows up in Japan, T2GB in the UK, T2HUB1, and a few small servers.

So the question is valid. Why is Japan different?

2. The Software Is The Same: aprsc Runs On Both

Every T2 server in that list runs aprsc. This is a daemon written by Hessu Lahtinen, OH7LZB, from Finland. It was developed on both FreeBSD and Linux from the start. It compiles cleanly on either one.

aprsc has a simple but critical job. Accept connections from APRS clients and IGates. Filter duplicate packets. Forward traffic to upstream hubs. It needs to handle thousands of concurrent sockets. Each packet is only 100 to 300 bytes.

The bottleneck is not CPU gigahertz. The bottleneck is the kernel network stack, context switching, and interrupt handling. The OS that handles sockets most efficiently wins.

FreeBSD’s TCP/IP stack is a direct descendant of 4.4BSD. That is the reference implementation of TCP/IP. Linux’s network stack evolved fast and added new features like eBPF, XDP, and BBR. Both are good. The philosophy is different.

3. Philosophy: Why FreeBSD Fits Japanese Engineering Culture

To understand the OS choice, you need to understand three things about Japan. The concept of monozukuri, the requirement for uptime, and the history of BSD in Japan.

3.1 Monozukuri: Build It Once, Build It Right, Let It Run For 10 Years

Monozukuri is the Japanese ethic of craftsmanship. It means build something with care so you do not need to touch it again. The Shinkansen runs on time because of monozukuri. Toyota factories have near zero defects because of monozukuri.

FreeBSD has the same approach. Release cycles are slow. FreeBSD 13 came out in 2021. FreeBSD 14 came out in 2023. Each release goes through heavy QA. APIs do not break often. A driver that is merged gets maintained for ten years.

Look at the Changed column in the status. T2OSAKA last changed 2025-07-05. Over a year with no updates, yet availability is 100 percent. T2FUKUOKA last changed 2026-04-21. Japanese sysadmins do not like to update every week. They want to set up, tune, and then leave it. FreeBSD gives them that peace of mind.

Linux is different. Kernel 6.1, 6.2, 6.3 ship fast. New features land fast. That is great for cloud. But for an APRS server where you want 99.99 percent uptime, fast can be a risk.

3.2 Uptime Is Everything

APRS-IS Tier 2 is not a toy. If T2OSAKA goes down, the whole Kansai region can go blind. IGates cannot upload positions to the internet. In Japan, where earthquakes and tsunamis are real threats, APRS is part of the emergency backup plan. During the 2011 Tohoku earthquake, APRS was used to track aid.

That is why the Avail column matters. T2OSAKA 100.00 percent. T2FUKUOKA 100.00 percent. T2UK 99.90 percent. A difference of 0.1 percent over 30 days is 43 minutes of downtime. In an emergency, 43 minutes is a long time.

FreeBSD is famous for uptime. There are FreeBSD servers with five years of uptime without a reboot. Kernel panics are rare. Memory leaks are uncommon. Upgrades do not force a reboot unless the kernel changes. For a Japanese sysadmin running a server as a volunteer, uptime without drama is gold.

3.3 The History of BSD in Japan: From Universities To Commercial Use

Japan was one of the earliest adopters of BSD outside the United States. In the 1980s, universities like Keio and Tokyo University used 4.2BSD for networking research. From there, a generation of Japanese developers started contributing to FreeBSD, NetBSD, and OpenBSD.

Big examples. Juniper Networks uses FreeBSD for JunOS. Nintendo Switch OS is based on FreeBSD. Panasonic and Sony have shipped products with it. So when a Japanese engineer needs to build a server, FreeBSD is not foreign. It is like Ubuntu in other countries. Everyone knows it.

The ham radio community in Japan also has many professional engineers. JARL, the Japan Amateur Radio League, had 1.2 million members at its peak. Many members work at NEC, Fujitsu, Hitachi. These people use FreeBSD at work. When they set up a T2 server at home, they install what they know.

4. Technical Analysis: Why FreeBSD’s Network Stack Fits APRS

Philosophy is not enough. Let us look at technical reasons. APRS-IS has weird traffic patterns.

4.1 Many Connections, Small Packets, Kernel Bound

T2CHILE handles 1,260 clients with 897,504 bytes per second out. That is 712 bytes per second per client on average. Very small. But the socket count is high. The kernel has to do a lot of select, poll, or epoll.

FreeBSD uses kqueue. kqueue was created for exactly this case. It scales to tens of thousands of file descriptors without slowing down. Linux has epoll which is similar. But kqueue has been mature since FreeBSD 4.1 in 2000.

For aprsc, kqueue gives an advantage when clients connect and disconnect often. APRS clients on mobile radios do that. A satellite passes, the client connects for five minutes, then drops. kqueue handles that churn efficiently.

4.2 Zero Copy and Sendfile

APRS servers do a lot of forwarding. A packet comes in from client A, then goes out to client B, C, and D. No need to change the data. FreeBSD has sendfile and zero-copy sockets that optimize this path. Data goes from kernel buffer straight to the NIC. No copy to userspace.

Look at T2FUKUOKA. 269 clients, C load 79.5, B out/s 36,285.
Compare T2TOKYO Linux. 256 clients, C load 79.7, B out/s 15,170.

Clients and CPU load are almost the same. But FreeBSD pushes 2.3 times more data. That means per CPU cycle, FreeBSD sends more packets.

In a data center, that difference is electricity cost. For a ham who pays the power bill himself, that difference matters.

4.3 PF: A Packet Filter That Is Sane

All APRS servers face the internet. They need a firewall. Linux uses iptables, nftables, or ufw. FreeBSD uses PF from OpenBSD.

PF config example looks like this:

pass in on em0 proto tcp to port 14580
block in all

Simple. Stateful. Rules are read top to bottom. Japanese sysadmins like it because it is easy to audit. In security, easy to audit means safe.

PF is also fast with large state tables. An APRS server has thousands of states because of thousands of clients. PF handles it without eating CPU. That is why T2OSAKA has a score of 815 with 304 clients.

4.4 Jails and VNET: Full Isolation

Some Japanese sysadmins run aprsc in a jail with VNET. That means the jail has its own network stack. If aprsc gets exploited, the attacker only gets the jail. He cannot see the main host.

Linux has Docker and network namespaces. But VNET in FreeBSD is a full stack. It has its own routing table, its own PF, its own lo0. It is like a VM but without the overhead of a VM. For critical infrastructure, that isolation helps you sleep at night.

5. The Score Column: Why FreeBSD Scores Are Low

In the status monitor, there is a Score column. Lower is better. The score is calculated from aprsis_rtt plus http_rtt plus user_load.

T2UK FreeBSD has score 709.2. That comes from aprsis_rtt 0.0 plus http_rtt 0.0 plus user_load 291.0 plus other penalties.

T2FUKUOKA score 807. T2OSAKA 815. T2TOKYO Linux 806. About the same.

But T2HUB1 FreeBSD score 71. That is the lowest among hubs. T2HUB2 Linux score 95.

Low score means low latency and low load. FreeBSD gets low scores for two reasons. First, network latency is consistent. Second, aprsc on FreeBSD uses CPU more efficiently when load is low. When clients are few, like T2HUB1 with 18 clients, FreeBSD is very thrifty.

6. The Human Factor: Who Runs The Server?

Technology does not run itself. People set it up.

The callsigns that run T2 Japan are old timers. JF2IWL, JI1BQW, people who have been in APRS since the 1990s. They started with packet radio on MS-DOS and JNOS. JNOS was a TCP/IP stack on DOS. Then they moved to Linux, then many moved to FreeBSD for stability.

When you have used FreeBSD for 20 years, you do not switch to Ubuntu because of hype. You have scripts. You have monitoring. You have PF rules. All tuned. Switching OS means two weeks of work. It is easier to stay.

Also, the aprsc documentation is most complete for FreeBSD. Hessu OH7LZB uses FreeBSD himself. So if there is a bug, the fix lands on FreeBSD first. Sysadmins in Japan who care about reliability will follow upstream.

7. This Does Not Mean Linux Is Bad

We need to be fair. Look at the data. The biggest server T2CSNGRAD with 1,769 clients runs Linux. T2FINLAND with 1,762 clients runs Linux. T2UKRAINE with 1,771 clients runs Linux. All 100 percent availability.

That means Linux can handle it. BBR TCP on Linux is also great for international links with high latency. If your server is in Tokyo but the client is in Brazil, Linux BBR can give better throughput.

In Japan, the choice comes down to tradition, stability, and maintainer preference. It is not an OS war. It is like choosing Toyota versus Honda. Both get you there. The mechanic just knows Toyota better.

8. If You Want To Set Up an APRS IGate, Which Should You Pick?

Based on all this, the guide is simple.

1. You want uptime, you hate updates, the server sits at a site
   Use FreeBSD. Install aprsc from ports. Set up PF with three lines. Enable kqueue. Done. You can leave it for two years.
2. You want to use Raspberry Pi, weird WiFi dongles, Docker
   Use Linux. Drivers are more plentiful. Direwolf IGate is easier on Linux. Community tutorials are everywhere.
3. You want to learn the network stack properly
   Use FreeBSD. The source code /usr/src/sys/netinet/tcp_input.c is a textbook. Read the code, compile the kernel, and you will understand TCP from the inside.

9. Conclusion: The Real Answer Why Japan Picks FreeBSD

After going through status.aprs2.net and history, the answer has five layers.

Layer 1: Performance
FreeBSD’s network stack with kqueue, zero copy, and clean TCP/IP gives better throughput per watt for APRS traffic that has many small connections. The T2FUKUOKA versus T2TOKYO data proves it.

Layer 2: Stability
FreeBSD’s philosophy is do not break things that work. Uptime of T2OSAKA at 100 percent for years. For emergency infrastructure, that is the number one requirement.

Layer 3: Security
PF and jails give sysadmins tight control without complexity. In today’s world, an exposed server should be hardened.

Layer 4: Culture
The BSD community in Japan has existed since the 1980s. From universities to industry. Ham radio in Japan has many engineers who use FreeBSD daily. When they build a volunteer server, they use what they know.

Layer 5: People
The maintainers of T2 Japan are veterans who have used FreeBSD for 20 years. Tools, scripts, monitoring are all ready. Switching OS is not a technical issue. It is a time and energy issue.

So it is not because Linux is bad. It is not because FreeBSD is magic. It is because of the fit between APRS needs, FreeBSD strengths, and Japanese engineering culture.

If you look at status.aprs2.net five years from now, I bet T2OSAKA and T2FUKUOKA will still be FreeBSD. Because of monozukuri. Build it once, let it run until the end.

The post Why Do Japan’s APRS-IS Servers Run on FreeBSD? A Deep Dive Into status.aprs2.net appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Introduction: Why Talk About Ham Radio in 2026?

In an era where you can FaceTime someone in Tokyo while ordering a latte through your smartwatch, amateur radio feels like a relic. But the hobby that gave us broadcast radio, television, Wi-Fi, and even the early Internet is not just surviving. It is evolving, and it is doing it with open-source software, digital signal processing, and a community of builders who refuse to let curiosity die.

Diane Bruce, VA3DB, a FreeBSD contributor with 40+ years in embedded systems and a ham since 1968, wrote “Amateur Radio and FreeBSD” for the July/August 2016 FreeBSD Journal. Her article is not a nostalgic look backward. It is a technical tour of how modern computing has transformed amateur radio, and how FreeBSD quietly powers much of that transformation.

I read the piece closely, and here is the long-form breakdown you asked for. No fluff, no rambling. Just the substance, context, and why it still matters in 2026. This post is over 2,000 words.

1. The Core Premise: Ham Radio Is the Original “Maker” Movement

Bruce opens with a reality check: wireless communication and the global Internet still depend on radio. Cell towers, Starlink, Wi-Fi, Bluetooth. All radio. Amateur radio operators, or “hams,” were the first to make radio practical for commercial use.

Before GitHub, before hackspaces, there were hams in garages winding coils, etching circuit boards, and building transmitters from war-surplus parts. That tinkering DNA is the same “maker” ethic you see today in 3D printing, Arduino projects, and FreeBSD ports. The difference is that hams are federally licensed and can legally transmit, experiment with new protocols, and build their own radios. You cannot do that with your iPhone.

Licensing is easier now. Morse code is no longer required. If you have a technical background, the exam is straightforward. That low barrier is intentional. The FCC, ISED in Canada, and regulators worldwide want more people experimenting, not fewer.

2. Why Computers and Ham Radio Became Inseparable

Bruce asks, “But why use computers with ham radio in the first place?” The answer is that both fields changed radically.

Modern hams use computers for:

• Satellite prediction: Knowing when the ISS or an amateur satellite passes overhead
• Digitally encoded voice: D-STAR, DMR, System Fusion
• Logging: Tracking thousands of global contacts automatically
• Digital modes: WSJT-X, PSK31, RTTY, FT8
• Software-defined radio: Turning $30 USB dongles into wide-band receivers
• APRS tracking: Real-time GPS position reporting

The result is a flood of ham applications, many written for Linux. Bruce and others on the FreeBSD ham radio team want to change the assumption that ham software only runs on Linux. Most Linux ham apps port to FreeBSD easily.

3. From Teletype to fldigi: The Evolution of Digital Modes

Ham radio was digital before “digital” was cool. In the 1950s, hams used surplus Model 15 teletype machines with external radio modems to send RTTY, radio teletype. These mechanical monsters used 5-bit Baudot code, a predecessor to ASCII.

The machines were clunky, loud, and impractical. Early home computers like the Apple II changed that. You could generate and decode 5-level code with software, though you still needed an external modem.

Today, CPU power means you do not need the modem. Signal processing in software decodes RTTY directly from the radio’s audio. The “Swiss army knife” for this on FreeBSD is fldigi. It handles RTTY, Hellschreiber, and modern modes like PSK31.

Hellschreiber deserves a mention. Developed in WWII, it used tones to paint characters on a moving drum. Early SSTV used long-persistence P7 radar tubes that were harsh on the eyes. Now it is all done in software, in full color.

4. Weak Signal Revolution: WSJT, JT65, and Bouncing Signals Off the Moon

The most dramatic change in ham radio is weak-signal work. Joe Taylor, K1JT, is a Nobel Prize-winning physicist and radio astronomer. He wanted to do Earth-Moon-Earth, or EME, communication.

Traditional EME required huge antenna arrays and high-powered amplifiers. Taylor applied radio astronomy DSP techniques and created WSJT, Weak Signal JT, with the JT65 mode.

Result: EME with a modest station that is far less expensive. Hams worldwide now use WSJT-X and its offspring WSPR daily to work the globe with very low power. Not just via the moon. Traditional shortwave using the ionosphere works too.

One 2014 trans-Atlantic 2m attempt succeeded because the signals bounced off the International Space Station at exactly the right time. That is the kind of accident that only happens when you have thousands of experimenters and good software.

PSK31 is another low-bandwidth mode popular for low-power operators. It can be heard below the noise floor. Again, fldigi is the program of choice.

5. Packet Radio, APRS, and the Internet Before the Internet

Amateur radio operators were instrumental in early packet radio. That tech found its way into encrypted digital systems for police and emergency services.

Store-and-forward networks using AX.25, a modified X.25 protocol, are still used worldwide. AX.25 is the backbone of the Amateur Positioning Radio System, or APRS.

APRS is well supported on FreeBSD using Xastir and YAAC. Stations use GPS to broadcast positions over AX.25. Search and rescue groups like Civilian Air Patrol rely on it.

Those packets also get relayed to the Internet. Go to aprs.fi and you can watch hams move in real time. Bruce’s example: aprs.fi/#!addr=FN25 shows her area near Ottawa. The screenshot in the article shows dozens of stations around Ottawa.

6. Software-Defined Radio: The $30 Revolution

Software-defined radio, SDR, is one of the hottest techniques in ham radio. Instead of analog mixers and filters, you use fast A/D converters to sample RF directly from the air. The data becomes I/Q signals: two streams 90 degrees out of phase. Decode them with a computer.

You can also generate signals with D/A converters and transmit.

Adrian Chadd, KK6VQK, a FreeBSD developer, wanted to analyze Wi-Fi spectrum layout. He needed SDR software that was well supported. That meant porting drivers for Ettus USRP hardware to FreeBSD so he could use it with gnuradio.

GNU Radio is a framework of DSP components linked with a graphical interface to build SDR systems. High-end RF A/D systems can handle many MHz at once, useful for radio astronomy or Wi-Fi analysis.

But you do not need expensive gear. Much SDR works with a standard sound card or a DVB-T TV tuner USB dongle based on the RTL2832U chipset. The dongle can directly sample RF up into UHF. Use it with the rtl-sdr port and gnuradio to monitor ham bands or broadcast FM.

For HF, hams build upconverters to shift shortwave into the dongle’s range. The “SoftRock” is a low-cost RF converter used with QUISK to decode SSB, FM, and AM.

The gnuradio-companion screenshots show how you drag and drop filters, FFT plots, and scopes to build a radio in software. That is the maker ethic in pure form.

7. Satellites, the ISS, and Tracking Software

Hams have built their own satellites since 1974. AO-7 is still operating, though its batteries are dead. Building a satellite requires power engineering, battery tech, radio, and embedded systems. These are NASA-level skills.

For the rest of us, the challenge is pointing the antenna. That is where predict and gpredict come in.

The International Space Station has licensed hams on board. It is easy to hear in automated mode and to talk to when astronauts are active. They do not have much time, but they schedule school contacts. Gpredict shows the ISS and other satellites with coverage circles.

The ISS also broadcasts SSTV, slow scan TV. Hams decode it with QSSTV. What used to require P7 radar tubes now takes a laptop.

8. Repeaters and the Internet: Linking the World

Repeaters extend mobile range by receiving on a hilltop and retransmitting. Linking city repeaters worldwide via the Internet is trivial. Software like thebridge or svxlink does it.

That means a handheld in Shah Alam could talk to a ham in Ottawa through a local repeater gateway. The RF part is local. The Internet handles the distance. This hybrid model is why ham radio stays relevant. It is not competing with the Internet. It is integrating with it.

9. FreeBSD’s Role and the Culture of Porting

Bruce’s subtext throughout is that FreeBSD is a first-class ham radio OS, even if most guides assume Linux. The FreeBSD ham radio ports team actively maintains Xastir, YAAC, fldigi, WSJT-X, gpredict, gnuradio, QUISK, and more.

Porting is not just recompiling. Adrian Chadd had to port USRP driver support. That kind of low-level work keeps FreeBSD relevant for SDR.

The ports model fits ham radio culture. You build what you need. You share it. You document it. Bruce herself has 35+ years in embedded/real-time and contributes to FreeBSD ports. She was first licensed in 1968.

10. So, Should You Get Licensed in 2026?

Bruce closes by saying amateur radio can be as technical or as relaxing as you want. The era of inexpensive computing has made it more interesting.

Here is why that still holds:

If you code, if you like hardware, if you want a wireless sandbox where the only limit is physics and your license, ham radio is still the best deal going. No, Morse code is not needed. Yes, your FreeBSD laptop is enough to start.

11. Getting Started: Resources and Next Steps

Bruce recommends two starting points:

• ARRL, American Radio Relay League: http://www.arrl.org
• RAC, Radio Amateurs of Canada: http://www.rac.ca

For FreeBSD-specific info: https://wiki.freebsd.org/Hamradio On FreeBSD

A modern starter kit in 2026 might look like:

1. License: Study for Technician in US, Basic in Canada. Free PDFs and apps exist.
2. Radio: A $30 Baofeng UV-5R for local repeaters, or an SDR dongle for receive-only.
3. Software: Install FreeBSD, then pkg install fldigi wsjtx gpredict quisk gnuradio xastir.
4. Antenna: Build a dipole for HF or a tape-measure Yagi for satellites. Plans are free.
5. Elmer: Find a local club. Hams love to mentor.

Conclusion: The Quiet Engine of Innovation

Bruce’s article is not about nostalgia. It is a status report. Ham radio pioneered wireless, and it never stopped. The tools changed. Spark gaps became SDR. Paper logbooks became FreeBSD servers running fldigi. But the ethos is identical: understand the system, then improve it.

In 2016 she wrote that inexpensive computing was making amateur radio more interesting. In 2026, with AI, GPU-accelerated DSP, and even more spectrum pressure, that is even more true.

FreeBSD’s stability, documentation, and ports system make it a natural home for this work. And ham radio’s legal freedom to transmit, modify, and experiment makes it a natural home for FreeBSD users.

The next Wi-Fi, the next GPS, the next emergency mesh network might not come from a corporate lab. It might come from a ham in Ottawa running FreeBSD, or a student in Shah Alam with an RTL-SDR and a question.

That is why this 2016 article still matters. It is a map. The territory is still open.

https://www.freebsdfoundation.org/wp-content/uploads/2016/10/HAMradioBruce.pdf

The post How FreeBSD and Ham Radio Still Shape the Future of Wireless Communication appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

If you use a Mac for amateur radio, you know the problem. Most software is designed for Windows. The stuff we get on macOS is usually ported over and looks terrible, or it is just too hard to set up.

QTH.app is different because it is actually built for the Mac. It feels like a native app. You can zoom in on the map with the trackpad, it scrolls smoothly, and it doesn’t look like Windows 95.

What it does It is a full APRS client:

• Mapping: It uses Apple Maps, so it’s clean. Supports USNG/MGRS and Maidenhead grids.
• Hardware Support: This is the important part. It works with APRS-IS (internet) but also connects to hardware TNCs. It has specific support for the Mobilinkd Bluetooth TNC, which is great for a portable setup. You can also just use the Mac’s internal sound card as a modem.
• Timeline: You can scroll back in time to see where stations were earlier. Good for checking movement history.

The Cost The developer (W8WJB) uses a “Freemium” model.

• RX is Free: You can download it and use all the receiving features for free. You can see stations, weather, and telemetry.
• TX is Paid: If you want to transmit (beacon your position), you have to pay a one-time fee inside the app.

My thoughts It’s good to finally see a developer focusing on the Mac interface. Since the RX part is free, it is worth downloading just to use as a monitoring tool in the shack. If you need to transmit, you can decide if the upgrade is worth it.

Check it out on the Mac App Store or visit https://qth.app/

The post QTH.app – Finally a proper APRS client for macOS? appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

For Amateur Radio operators, the answer often lies in a series of digital “chirps” known as APRS (Automatic Packet Reporting System). While often mistaken as just a “vehicle tracker,” APRS is actually one of the most resilient, tactical, and vital tools in the emergency communications (EmComm) arsenal.

In this post, we’ll dive deep into the history of APRS, how it saves lives during crises, and why its continuous usage today is critical for future readiness.

What is APRS? (It’s More Than Just GPS)

Before we discuss disaster scenarios, we must understand the tool. APRS is a digital communications protocol used by amateur radio operators to exchange real-time tactical information.

Unlike voice communications, which are fleeting and require you to be listening at the exact right moment, APRS is visual and persistent. It uses packet radio to transmit data—coordinates, weather telemetry, text messages, and status objects—over radio waves (usually on the 2 meter band)

A Legacy of Innovation: The History of APRS

To understand the philosophy of APRS, we have to look at its creator, the late Bob Bruninga (WB4APR).

In the early 1980s and 90s, Bob didn’t set out to build a vehicle tracking system. He wanted to solve a “local tactical” problem. In an emergency operations center, voice channels were cluttered with people asking, “What is your location?” and “What is the status of the shelter?”

Bob developed APRS to move that data off the voice channel. His vision was a real-time dashboard for local information. He famously insisted that APRS stands for Automatic Packet Reporting System, emphasizing that it is not just for Position reporting, but for Packet reporting of all kinds of tactical data.

From its humble beginnings on Commodore 64s and TNCs (Terminal Node Controllers), APRS has evolved into a global network supported by satellites, internet gateways (IGates), and handheld radios.

3 Critical Usages of APRS During Emergencies

When disaster strikes, confusion is the enemy. APRS cuts through the fog of war in three distinct ways.

1. Tactical Situational Awareness (Asset Tracking)

In a search and rescue (SAR) operation or wildfire response, the Incident Commander needs to know exactly where their teams are.

• The Problem: Relying on voice reports (“Command, I am at the corner of 5th and Main”) takes up valuable airtime and is prone to error.
• The APRS Solution: Responders carrying handhelds or driving trucks equipped with APRS trackers automatically beacon their position every few minutes. The Incident Commander can look at a map screen and see the real-time movement of every unit.
• Why it matters: This creates a “God’s eye view” of the battlefield without a single word being spoken, leaving voice frequencies open for urgent traffic.

2. The “Last Mile” Messaging Service

What happens when you need to send a supply list or a welfare check, but the internet is down? APRS has a built-in text messaging capability.

• Station-to-Station: You can send short text messages directly from radio to radio, completely independent of the internet.
• The SMS/Email Gateway: Even if the local internet is down, if your radio packet can reach a high-altitude repeater or an IGate 50 miles away that does have power, that IGate can route your message to the global internet. This allows a ham radio operator in a disaster zone to send an SMS to a family member’s cell phone or an email to a relief agency.

3. Hyper-Local Weather Intelligence

Natural disasters are often weather-dependent. National radar gives a broad picture, but micro-climates matter during floods and fires.

• Weather Telemetry: Many hams connect their home weather stations to APRS. These stations autonomously beacon wind speed, rainfall, and barometric pressure.
• Crisis Application: During a flash flood, an emergency coordinator can monitor APRS weather packets from the specific valley where the water is rising, getting ground-truth data that might differ from the news report. This data often feeds directly into the National Weather Service via the CWOP (Citizen Weather Observer Program).

Continuous Usage: Keeping the Network Alive

One of the unique aspects of APRS is that it relies on a “mesh” of volunteer digipeaters (digital repeaters) and IGates. If hams stopped using APRS, the network would decay. Therefore, everyday usage is actually a form of preparedness.

• The “Always-On” Global Net: By tracking their daily commutes or hiking trips (SOTA – Summits on the Air), hams ensure that digipeaters are functional and coverage maps are accurate.
• Space Communications: APRS is a primary mode of communication through the International Space Station (ISS) and various CubeSats. Hams practice bouncing packets off satellites, a skill that becomes crucial if terrestrial repeaters fail.
• Public Service Events: Hams use APRS to track runners in marathons or support vehicles in bike races. These “planned disasters” are the perfect training ground for the real thing.

Conclusion: The Visual Language of Survival

In an age of 5G and Starlink, it is easy to dismiss a 1200-baud packet radio protocol as obsolete. But fragility is the price of complexity. Cellular networks are fragile; the internet is fragile.

APRS is robust. It is decentralized, operates on simple hardware, and provides the one thing most critical in a crisis: Truth. The truth of where people are, what the weather is doing, and who needs help.

For the amateur radio operator, equipping your station with APRS isn’t just a fun hobby project—it is a commitment to being the eyes and ears of your community when the screen goes dark.

Ready to get started?

• Hardware: Look into easy-to-use trackers like the Mobilinkd TNC or radios with built-in APRS like the Yaesu FT-5D or Kenwood TH-D74.
• Software: Download APRSdroid (Android) or aprs.fi (iOS) to see the network in action right now.

https://www.aprs.org

The post The Silent Sentinel: Why APRS is the Ultimate Digital Lifeline When the Grid Fails appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

For years, if you wanted to set up a serious APRS (Automatic Packet Reporting System) node—be it an iGate, a Digipeater, or a Tracker—you usually had two choices. You could buy an expensive, proprietary TNC (Terminal Node Controller), or you could wrestle with a soundcard modem and a dedicated PC.

But the game has changed.

Today, we are diving deep into a project that is making waves in the community, developed by Thai amateur radio operator Somkiat Nakhonthai (HS5TQA). It is called ESP32APRS_Audio, and it might just be the most versatile, cost-effective APRS solution available today.

What is ESP32APRS_Audio?

At its core, ESP32APRS_Audio is a firmware that turns a standard ESP32 microcontroller into a fully functional Software TNC.

Unlike other ESP32 projects that require specific LoRa modules or complex digital interfaces, this project utilizes the ESP32’s internal DAC (Digital to Analog Converter) and ADC (Analog to Digital Converter) to generate AFSK (Audio Frequency Shift Keying) tones directly.

In plain English: You can plug this $5 chip directly into the microphone and speaker jack of any analog radio—from a Baofeng UV-5R to a 25-year-old Yaesu mobile—and turn it into a modern, internet-connected APRS station.

Why This Project is a Game Changer

1. It’s a True “Soft-Modem”

Most modern APRS projects rely on external hardware modems. HS5TQA’s code implements the modem entirely in software.

• VHF: Standard 1200bps AFSK (Bell 202) for 2m operations.
• HF: 300bps AFSK (Bell 103) for long-range HF packet.
• UHF High Speed: 9600bps GFSK (supported on ESP32-S3).

2. The “Swiss Army Knife” of Modes

One firmware flash gives you every mode you could possibly need. You don’t need different code for different jobs; you just change the settings in the web interface.

• iGate (Internet Gateway): Listens to RF traffic and pipes it to the APRS-IS internet servers via WiFi.
• Digipeater: Listens for packets and re-transmits them to extend network range.
• Tracker: Connects to a GPS and beacons your location.
• Weather Station: Interfaces with weather sensors to report telemetry.

3. FX.25 Support

This is a huge technical win. The firmware supports FX.25, which is an upgrade to the standard AX.25 protocol. It wraps the standard packet in “Forward Error Correction” (FEC) data.

• The Benefit: If a packet gets slightly corrupted by static, FX.25 can mathematically repair it.
• Compatibility: It is fully backward compatible. Standard TNCs will just see a normal packet, but FX.25-enabled stations (like Direwolf or this ESP32) will enjoy much better decoding in noisy environments.

The Hardware: Simplicity Itself

You don’t need a degree in electrical engineering to build the interface. The repository provides the schematic for the ESP32DR Simple Circuit.

To connect the ESP32 to a radio, you essentially need three things:

1. Isolation: A simple 600:600 Ohm audio transformer prevents ground loops (hum) between your radio power and ESP32 power.
2. Level Adjustment: A voltage divider (potentiometer) to drop the radio’s loud speaker audio down to the 3.3V range the ESP32 can handle.
3. PTT Control: A simple NPN transistor (like a 2N3904) to trigger the Push-To-Talk on the radio.

Supported Boards:

• Standard ESP32 (DevKit V1)
• ESP32-C3
• ESP32-S3

The Software Experience: No Coding Required

One of the biggest barriers to entry for Ham projects is the “Compile Error.” You download a project, try to upload it, and spend 4 hours debugging library conflicts.

ESP32APRS_Audio solves this by focusing on a Web-Based User Interface.

1. Flash Once: You use the Espressif download tool to flash the binary files one time.
2. Config via WiFi: The ESP32 creates a WiFi Hotspot (ESP32APRS_Audio). You connect to it with your phone or laptop.
3. Browser Control: You navigate to 192.168.4.1 and are greeted with a full dashboard. You can set your Callsign, SSID, Latitude/Longitude, Digipeat paths, and Volume levels visually.

Advanced Features for the Power User

For those who want to push the envelope, HS5TQA has packed in enterprise-level features:

• VPN (WireGuard): Secure your connection if you are placing this on a remote mountain top.
• MQTT: Integrate your radio data into Home Assistant or other IoT dashboards.
• Bluetooth TNC: It enables the Bluetooth SPP (Serial Port Profile). You can pair your Android phone running APRSdroid to the ESP32, using it as a wireless TNC for your mobile operations.

How to Get Started

1. Visit the Repo: Go to GitHub – nakhonthai/ESP32APRS_Audio.
2. Order the BOM: An ESP32 DevKit, a few resistors, capacitors, and an RJ11 or TRRS jack for your radio.
3. Build the Cable: Follow the “ESP32DR Simple” schematic.
4. Flash & Deploy: Get your station on the air for under $20 USD.

Conclusion

The ESP32APRS_Audio project is a testament to the spirit of amateur radio. It takes accessible, inexpensive modern technology and bridges it with the legacy RF hardware we all love. Whether you are looking to fill a coverage gap in your area with a cheap Digipeater or build the ultimate mobile tracker, this project deserves a spot on your workbench.

https://github.com/nakhonthai/ESP32APRS_Audio

The post The Ultimate “DIY APRS TNC”: A Deep Dive into the ESP32APRS Audio Project appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

For decades, the Amateur Radio world has been somewhat bifurcated. On one side, you have the rugged, analog reliability of HF and VHF radios; on the other, the slick, user-friendly interface of modern smartphones. For a long time, connecting these two worlds required bulky, expensive external hardware—specifically Terminal Node Controllers (TNCs)—and a mess of cabling that made mobile operations a headache.

However, the landscape of the Automatic Packet Reporting System (APRS) is shifting. A software solution that has been gaining significant traction in the community is APRS pro. By leveraging the computing power already sitting in your pocket, this application attempts to modernize the packet radio experience without discarding the RF roots that hams love.

Here is an in-depth look at how APRS pro is attempting to redefine the “Shack-in-a-Box” concept.

The Death of the Hardware TNC?

The most significant technical achievement of APRS pro is its embedded “Soft TNC” (Terminal Node Controller). Historically, if you wanted to send digital data over an analog radio, you needed a physical modem box between your radio and your computer.

APRS pro eliminates this hardware barrier. By using the iPhone’s own audio processing capabilities, the app functions as a high-fidelity modem.

• VHF/UHF Operations: It handles the standard 1200 baud packets used for local 2-meter communications.
• HF Operations: It supports 300 baud modes for long-range High Frequency work.

For the end-user, this simplifies the setup dramatically. All that is required is a simple audio interface cable to connect the phone to the radio. The app handles the modulation and demodulation, effectively turning an iPhone into a fully functional command station.

Beyond RF: A Hybrid Connectivity Approach

While radio purity is important, APRS pro acknowledges the reality of modern infrastructure. The app is designed to be “transport agnostic.” It functions seamlessly over traditional RF, but it also integrates fully with cellular data (2G/3G/4G) and WiFi.

Perhaps most interestingly for off-grid adventurers, the app bridges the gap with commercial satellite trackers. It supports integration with Spot and deLorme satellite devices. This means a user can be completely off the grid—miles away from a cell tower or a digipeater—and still populate their location data onto the APRS pro map interface.

Intelligent UI: Dynamic Symbols and Mapping

One of the common complaints about legacy APRS software is the static nature of the user interface. APRS pro attempts to solve this with “Context-Aware” computing.

A standout feature is the Dynamic Symbol system. In traditional setups, if a user switches from driving a jeep to hiking on foot, they have to manually dive into menus to change their beacon icon from a “Car” to a “Hiker.” APRS pro automates this by detecting the device’s motion and speed, changing the symbol dynamically.

Furthermore, the mapping engine is robust. It allows for customizable layers, including real-time traffic data, building footprints, and specific Points of Interest (POI). This transforms the map from a simple location plotter into a tactical situational awareness tool.

The Communication Hub: Real-Time and Offline Messaging

APRS is not just about dots on a map; it is a messaging network. APRS pro includes a chat interface that mimics modern SMS or WhatsApp functionality, but over the APRS network.

It addresses a major pain point of RF communication: packet loss. If a user drives through a tunnel or loses connectivity, messages are often lost to the ether. APRS pro utilizes a server-side buffer that stores incoming messages while the user is offline and delivers them the moment connectivity is restored.

Contributing to the Network: Built-in iGate

The application encourages users to be active participants in the network infrastructure rather than just passive consumers. It features a built-in iGate (Internet Gateway).

When connected to a radio, the app can “listen” to local RF traffic from other hams and forward that data to the global APRS-IS (Internet Service) network. This allows a mobile user to act as a digital repeater, helping other nearby stations get their signal out to the world.

Safety Protocol

Finally, the developers have integrated a dedicated safety layer for emergency situations. The interface includes a prominent Emergency Button. When activated, this triggers a distress message sent directly to ALL nearby stations. For hikers, search and rescue volunteers, or remote workers, this creates an immediate digital lifeline to the surrounding amateur radio community.

The Verdict

APRS pro represents a maturity in the ham radio software market. By moving the complex processing from external hardware into software, it lowers the barrier to entry for new hams while providing the advanced features—like iGating and Satellite integration—that veterans require.

It is a compelling example of how amateur radio can evolve by embracing, rather than resisting, the smartphone revolution.

https://aprspro.com

The post Bridging the Analog-Digital Divide: A Deep Dive into ‘APRS pro’ for iOS appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Some of you may know me from the ham-radio-lora-aprs user group. While much of my recent work focuses on LoRa, I recently realized that a specific user interface problem applies to all APRS wireless methods—not just the new stuff.

We need to talk about the user experience (UX) of APRS, and why we are letting the “mesh” crowd eat our lunch when it comes to usability.

The Original Vision: More Than Just Dots on a Map

It is a common misconception that APRS is merely a vehicle tracking system. If we look back at the words of the late, great Bob Bruninga (WB4APR), the father of the protocol, the intent was always much deeper.

As Bob said years ago on aprs.org:

“APRS is not a vehicle tracking system. It is a two-way tactical real-time digital communications system between all assets in a network sharing information about everything going on in the local area. On ham radio, this means if something is happening now, or there is information that could be valuable to you, then it should show up on your APRS radio in your mobile.”

Furthermore, the documentation defines it as a multi-user data network that is distinct from conventional packet radio because of:

1. Map integration and data display.
2. One-to-many protocols for real-time updates.
3. Generic digipeating (no prior network knowledge required).
4. A worldwide transparent internet backbone.

The Current State: Where is the “Chat”?

Mike (KC8OWL) has done an incredibly successful job reinvigorating the concept of messaging with his popular APRSThursday. Each week, 600–800 hams send messages to ANSRVR essentially to say “I’m here!”

It is amazing to see that level of participation. However, it highlights a gap: APRS, as envisioned by WB4APR, should be facilitating this kind of interaction all the time.

So, why isn’t it?

I believe the answer lies in the interface. Sending a message via traditional APRS software often feels like a technical chore rather than a seamless communication flow. There isn’t an easy, modern interface that users have come to expect in the smartphone era.

The Mesh Comparison: A Lesson in Usability

In an informal survey, I looked closely at MeshCore and Meshtastic. Both have significant user communities that include hams and non-hams alike.

The key to their success? Solid, polished apps that run on iOS and Android. They transform a phone or tablet into a sophisticated, familiar interface for a wireless packet network.

I won’t debate the pros and cons of the protocols themselves (that is a complicated discussion!). Instead, I want to highlight the User Experience differences, using MeshCore as an example.

1. The Map Experience

Maps are critical. In the MeshCore app, the map is intuitive. It shows local objects and stations clearly.

• Click-to-Interact: Clicking an icon brings up relevant details without needing to fetch data from the internet.
• Direct Action: If it’s a node, you can click to send a one-to-one message immediately.
• Remote Control: If it’s your repeater, you can log in over the air (reminiscent of the old TNC RTEXT function) for rules-compliant local control.

Crucially, this can all happen offline (provided the base map is cached).

2. Modern “Chat” Messaging

Messaging in APRS allows for one-to-one and one-to-many communication. Today, the rest of the world calls this “Chat.”

In the mesh world, the chat interface looks like WhatsApp, iMessage, or Discord. It is transparent and fluid.

• The “Public” Channel: Any operator in range can contribute.
• Ease of Flow: It encourages conversation.

Compare this to current APRS apps (like Pinpoint, YAAC, etc.). While powerful, they often lack that “pick up and play” ease of flow—especially on a mobile phone.

3. Group Channels

Imagine a more focused chat room, for example, EOC-PHX.

• Use Case: Communications specific to the Phoenix Emergency Operations Center user community.
• Management: Managed by hams at the local Red Cross.
• Filtering: While amateur radio cannot be encrypted (nothing is “secret”), the interface can restrict the view of that specific chat group to members of the EOC team, filtering out the noise of the public channel.

This concept could extend to radio clubs for meeting announcements, hamfests, or even a dedicated APRSThursday group where the app reminds you to check in!

The Feasibility Question

Some might argue that channel capacity is a bottleneck. However, with informal guidelines, it is achievable. Our local Phoenix LoRa network runs at 4.6 kbps, which is roughly 4x the capacity of a typical 1200 baud AX.25 APRS channel. I do all my APRSThursday check-ins via this LoRa network without issue.

The Hurdle: Development

It seems the biggest impediment to having an APRS app like this is the substantial effort required to develop it and get it into the “walled gardens” of the iOS App Store and Google Play Store.

However, the roadmap is there. The “mesh” community has proven that if you give people a modern, slick interface, they will use the network for exactly what Bob Bruninga envisioned: Tactical, real-time digital communication.

Is there someone out there working on this? Is it time for APRS to get a UI facelift?

Cheers and 73, Jon N7UV

P/S: If you are interested on APRS, please join https://groups.io/g/APRS

The post Reimagining APRS: What Amateur Radio Can Learn from the Mesh Networking World appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Amateur radio enthusiasts have long been using APRS (Automatic Packet Reporting System) to track mobile stations, send messages, and share telemetry over RF and the internet. Traditionally, building an APRS tracker has required a fair bit of wiring, configuration, and standalone software installation. However, thanks to the work of the open source community—particularly the sdr-enthusiasts/docker-aprs-tracker project—it’s now possible to deploy a self-contained APRS tracker inside a Docker container.

This raises an interesting question: could we build a compact, mobile APRS tracker using a Raspberry Pi and this containerized setup? While I haven’t personally tested this combination yet, I believe the idea holds real promise and is worth exploring.

The Project: docker-aprs-tracker

The docker-aprs-tracker project packages Direwolf (a software TNC), GPSD (for GPS data input), and Chrony (for system time synchronization) into a Docker container. It’s designed to be run on a minimal Linux environment and supports ARM architectures, including Raspberry Pi models (such as the 3B+, 4B, and even some alternatives like LePotato). This makes it an ideal candidate for Raspberry Pi deployments.

Why Raspberry Pi?

The Raspberry Pi is a perfect fit for this kind of project due to its low power consumption, small size, and ARM64 compatibility. When paired with a USB GPS module, a USB sound card, and a Baofeng radio (or any HT that supports audio input/output), it has the potential to become a fully functional APRS tracker with digipeater capability.

Here’s the rough concept:

• Raspberry Pi (DietPi or Raspberry Pi OS Lite): Lightweight Linux OS, running headless.
• USB GPS module: Feeds GPS coordinates to the container via GPSD.
• USB sound card: Acts as the audio interface to the radio.
• Baofeng UV-5R: Transmits and receives APRS signals.
• Direwolf inside Docker: Handles AX.25 packet encoding/decoding and beaconing.

Key Advantages

• Portability: Everything runs on a Pi, powered by USB or battery.
• Simplicity: Containerized deployment reduces the mess of dependencies.
• Modularity: You can easily swap out hardware components.
• Maintainability: Configuration is stored in a version-controlled docker-compose.yml.

Points to Consider

This project is still under active development, and the container is described as “low maturity,” meaning bugs and frequent changes should be expected. For experimental or personal use, this isn’t a deal-breaker. In fact, it can be a great learning opportunity.

Also, tuning the audio interface can be tricky—especially if you’re using a VOX-based cable like the BTech APRS-K1. The creator of the project recommends a CM108-based USB sound card with built-in PTT support for more reliable transmission. There’s even mention of pre-built options from na6d.com that combine everything in a compact form.

Final Thoughts

While I haven’t built this setup yet, the combination of Docker, Direwolf, and Raspberry Pi opens the door for a lightweight, portable APRS tracker that could be deployed in a vehicle, on a hiking trip, or even at a public service event. It’s an idea I believe many radio amateurs will find interesting—especially those already comfortable working with Raspberry Pi and containerized applications.

If you’re looking for your next ham radio project, this might just be it. And if you do build it, I’d love to hear how it works out for you. Visit and learn more at https://github.com/sdr-enthusiasts/docker-aprs-tracker

The post Building an APRS Tracker with Raspberry Pi appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

In the ever-evolving world of amateur radio, having the right tools at your disposal can mean the difference between static silence and clear, effective communication. Among the most respected contributors to the amateur radio software community is the developer behind WD6CNF’s website, a trusted source of high-quality, purpose-built software for ham radio enthusiasts.

This remarkable collection of Windows-compatible programs was developed by a seasoned amateur radio operator known by his call sign, WD6CNF. With a genuine passion for radio communication and a deep understanding of signal processing, WD6CNF has dedicated countless hours to building reliable, user-friendly tools designed specifically to enhance station capabilities for fellow hams.

Whether you are a newcomer looking to explore digital modes or a veteran fine-tuning your signal chain, the WD6CNF software suite provides a rich variety of utilities to support and improve your station’s performance. Below is a closer look at each of the programs he has developed—each carefully crafted to serve a specific need in the amateur radio space.

CW Decoder (Replaced by CWTY Decoder)

While no longer updated, the original CW Decoder laid the groundwork for its successor. It provided basic Morse code decoding, helping operators monitor CW transmissions without relying solely on ear and experience. This program was a popular starting point for many in the hobby.

Audio Spectrum Analyzer

Designed for a range of Windows versions—from XP to Windows 10—this tool allows operators to visually analyze audio frequency spectrums. This is particularly useful for fine-tuning signal inputs and identifying interference sources. Its compatibility with modern systems makes it a must-have for any operator looking to improve audio clarity.

Audio Sweep Generator / Spectrum Analyzer

Combining the features of a signal generator and a spectrum analyzer, this versatile program enables users to test and observe frequency response across audio equipment and antennas. Perfect for calibration tasks and system diagnostics, it runs smoothly on systems as old as Windows XP up to Windows 10.

Digital Voice Keyer

A favorite among contesters and frequent operators, the Digital Voice Keyer automates the playback of pre-recorded messages. Compatible with Windows XP through Windows 10, it helps reduce operator fatigue during long sessions, ensuring clear and consistent audio transmission without the need for constant mic handling.

Voice Activated Recorder

This smart utility automatically begins recording when it detects voice input, saving only the most important parts of a QSO or monitoring session. It’s an ideal tool for logging activity or preserving key transmissions for later review. It runs on all Windows systems from XP to Windows 10.

Simple Windows Packet Controller

Supporting basic AX.25 packet communication, this controller simplifies digital packet radio for Windows users. Though targeted at XP, Vista, and Windows 7 systems, it remains a lightweight and effective entry point for digital operation.

DSP Filter

This program uses digital signal processing techniques to clean up audio signals—eliminating unwanted noise and enhancing clarity. Compatible from XP to Windows 10, it is particularly useful for weak-signal work or improving intelligibility in noisy conditions.

CWTY Decoder (Successor to CW Decoder)

This is the current Morse code decoding solution offered by WD6CNF. It supports newer Windows versions (Vista through 10) and provides improved accuracy, better interface design, and expanded functionality over its predecessor. A valuable tool for any CW enthusiast.

Dual Channel Oscilloscope

This digital oscilloscope turns your PC into a visual analyzer for real-time waveform inspection. Useful for audio diagnostics, transmitter checks, or educational purposes, the program supports all Windows versions up to 10 and is appreciated for its simplicity and effectiveness.

Dual Channel Function Generator

Completing the test suite is this function generator, capable of producing waveforms across two independent channels. Excellent for circuit testing, antenna experiments, and lab work, it serves as an invaluable addition to the shack of any technically-inclined operator.

A Community Contribution Worth Celebrating

The continued relevance and utility of WD6CNF’s software is a testament to his commitment to the amateur radio community. Despite the shift to modern platforms and SDR (software-defined radio), his tools remain dependable, efficient, and refreshingly straightforward.

Each program is available directly from the Downloads page of the official website, and all are free for radio amateurs to use. Whether you are just starting out or looking to expand your station’s capabilities, WD6CNF’s offerings are a valuable resource backed by years of experience and dedication.

We extend our sincere thanks to WD6CNF for his continued support of the ham radio community. His contributions serve not only as practical tools but also as an inspiration for amateur radio operators everywhere to share, build, and give back.

Visit http://www.hotamateurprograms.com/ and explore the tools that can take your amateur radio experience to the next level.

The post Unlocking the Airwaves: A Tribute to WD6CNF and His Software Suite for Amateur Radio Operators appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Amateur radio has always been about innovation, and Hamtastic is a fine example of that spirit. Built using Python, Flask, and Node-RED, this open-source project lets you send messages from low-power Meshtastic LoRa radios to HF bands using JS8Call and FLdigi. It’s a fun, flexible integration that combines modern mesh networking with traditional amateur radio communications.

If you’re looking for a way to extend the reach of your LoRa setup into HF frequencies—or just want to tinker with some cool ham tech—Hamtastic is worth exploring.

What Hamtastic Does

At its core, Hamtastic acts as a bridge between Meshtastic (a LoRa-based mesh radio platform) and JS8Call (a weak signal digital mode for HF bands). It uses:

• Python + Flask for a lightweight web server.
• Node-RED to manage message routing and flows.
• pyserial for talking to the Meshtastic device.
• JS8Net for communicating with JS8Call.

The result: a system that listens for Meshtastic messages, processes them, and transmits them on HF. You can also build a user interface using Node-RED Dashboard if desired.

Setup Overview

You’ll need to clone the Hamtastic GitHub repo, create a Python virtual environment, and install the required libraries. A few highlights:

git clone https://github.com/TheWatchMker/Hamtastic
cd Hamtastic
python -m venv .
. bin/activate
pip install flask pyserial requests json
pip install pip@git+https://github.com/jfrancis42/js8net

For the Node-RED side, you’ll want:

npm install node-red-node-serialport node-red-dashboard node-red-contrib-http-request node-red-contrib-json

Running the Services

Hamtastic comes with two core scripts:

• MeshtasticImport.py for handling incoming messages from your LoRa device.
• Node-red-Js8call.py for pushing those messages into JS8Call.

It’s a good idea to run these as systemd services on your Raspberry Pi. Here’s a quick template for that:

[Unit]
Description=Meshtastic Integration Service
After=network.target

[Service]
ExecStart=/usr/bin/python3 /path/to/MeshtasticImport.py
WorkingDirectory=/path/to
Restart=always
User=pi

[Install]
WantedBy=multi-user.target

Enable with:

sudo systemctl enable meshtastic.service
sudo systemctl start meshtastic.service

Node-RED Flow

The project also includes a sample flow file (Node-redFlow.json) that you can import into Node-RED for testing and routing logic. It includes components like inject nodes, function processors, HTTP handlers, and debugging output—everything needed to wire together your message pipeline.

Final Thoughts

Hamtastic is a brilliant DIY solution for hams who want to bridge mesh networks and HF. It’s not plug-and-play, but it’s not overly complex either—perfect for weekend experimentation. If you’re a Raspberry Pi user with an interest in packet radio, JS8Call, or digital comms, this project is definitely worth checking out.

Special thanks to @TheWatchMker and @yNosGR for building and maintaining the project. And also credit to JS8Net by jfrancis42 for the Python-JS8Call glue.

GitHub Repository: github.com/TheWatchMker/Hamtastic

The post Bridging Meshtastic and HF Radios with Hamtastic appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Important: WoAD is only for users with a valid amateur radio license. Do not download or use it unless you’re properly licensed. Ship station, marine, or general radiotelephone licenses are not accepted.

WoAD connects to the Winlink Global Radio Email® system and also supports peer-to-peer (P2P) messaging, either over the internet or via radio.

Supported Protocols and Interfaces

Telnet – Fastest option if you have internet access
Packet – Classic Winlink transport via KISS TNC
AFSK 1200 bps / 300 bps – Audio tones via soundcards like SignaLink or digirig
FSK 9600 bps – Higher-speed audio option
PTT control – Works via USB RTS, CM108 GPIO, or tone-activated
USB support – Radios like Kenwood TH-D72/74 and TM-D710 supported
Bluetooth – Connects to devices like Mobilinkd TNC
Bluetooth Low Energy (BLE) – For modern low-power devices
TCP/IP – Works with software TNCs like Dire Wolf
ARDOP – Modern, efficient digital mode
VARA HF and VARA FM – High-speed, robust modes for HF and VHF/UHF over TCP/IP

Whether you’re involved in emergency communications, portable operations, or just experimenting with radio email, WoAD is a lightweight, modern solution that puts digital comms in your pocket.

Developed by Sumus Technology Limited, WoAD continues to grow with the amateur radio community in mind.

Visit https://woad.sumusltd.com/

The post WoAD – Winlink Client on Your Android: Seamless Radio Email for Hams appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

John, WB2OSZ has quietly built something incredible: a community-curated APRS documentation repository that lives on GitHub — and it’s a goldmine.

What’s Inside?

The APRS Documentation Project isn’t just a document dump. It’s a thoughtfully collected and regularly updated library of the most relevant and practical APRS guides out there, including:

• What is APRS? – A straight-talking explanation from the creator himself, Bob Bruninga WB4APR (SK), that busts myths and reveals the real purpose of APRS: real-time tactical communication, not just vehicle tracking.
• Understanding APRS Packets – A great resource to help decode packet structure without drowning in the AX.25 spec.
• How to Get Started in APRS – No more buying vintage TNCs or spending big on radios you don’t need. This is beginner-friendly advice, perfect for LoRa APRS users too.
• The Best APRS Presentations – Planning to give a talk at a club or hamfest? This collection can help you prepare a solid presentation without starting from scratch.
• APRS Digipeater Algorithm – Finally, a modern explanation of how APRS digipeaters should work—essential reading if you’re running one or developing your own.
• APRS12b & APRS12c Draft Specs – These drafts aim to update the long-obsolete APRS101 spec with all the real-world tweaks and improvements made since 2000.

APRS Is Still Alive — and Evolving

APRS is more alive than ever. Radios and devices with built-in APRS features are becoming more common. And with events like APRS Thursday, the global community is actively encouraging more messaging and experimentation.

Even the International Space Station is on board—literally. There are documents here showing how you can use an HT to contact the ISS via APRS. No fancy gear needed.

Contribute or Just Read

This is an open-source, community-powered project. You don’t have to be a coder to help—just read the docs, share feedback, or contribute links to better resources. If you’re building tools, running IGates or digis, or just trying to get a LoRa tracker working, you’ll want to keep an eye on this repository.

GitHub link: https://github.com/wb2osz/aprsspec

Final Thoughts

Whether you’re using any available APRS software or hardware or experimenting with your own custom APRS software or hardware, this project is worth bookmarking. It’s clean, current, and community-driven — something APRS desperately needed.

The post Rediscover APRS with the APRS Documentation Project by WB2OSZ appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

I recently sat down at the shack with a Debian testing installed—more out of curiosity than anything—and decided to dig around to see what kind of amateur radio software is available directly from the APT repositories. No PPAs, no compiling from scratch. Just plain old apt.

And honestly? There’s a lot in there.

Getting Started

If you’re running Debian (or something based on it—like Ubuntu), pop open your terminal and try this:

apt-cache search amateur radio

The list is long. I figured I’d share some of the highlights that caught my eye, in case you’re thinking of setting up a ham radio workstation with Linux.

APRS & Packet Stuff

Want to run your own APRS iGate or digipeater? You’re covered.

• aprx: This one’s solid for setting up a receive-only or full iGate.
• aprsdigi: A simpler digipeater option.
• soundmodem: Emulates a TNC using just your sound card. Works well with 1200 baud packet.

Also stumbled on a2d—apparently it bridges APRS to DAPNET for DMR pagers.

Digital Modes

Of course, WSJT-X and friends are there:

• wsjtx, jtdx: Your go-to for FT8, FT4, WSPR, etc.
• js8call: A personal favorite for low-band chatting with more flexibility than FT8.
• flamp, flmsg, flwrap: For sending structured messages and files over HF.

If you’re into Winlink, there’s pat—a decent cross-platform client. Easy to run headless too.

Exams & Learning

Even tools to help study:

• hamexam: Practice tests for US licenses.
• canadian-ham-exam: Same idea, for our friends in Canada.

Rig Control

No need for proprietary tools here.

• hamlib: Core library for rig control (also has CLI tools).
• libhamlib-utils: Helpful for scripting or testing.
• There are bindings for Python, Perl, Lua, and even Tcl if you’re into that kind of thing.

You can even drive your transceiver from a Python script with python3-hamlib and pyhamtools.

Satellites & Propagation

Playing with propagation tools?

• gr-satellites: GNU Radio-based decoders for satellite telemetry.
• voacapl + pythonprop: Good ol’ HF propagation prediction, straight from the VOACAP engine.

EchoLink & Remote Ops

Some of us love working remote—or just can’t be at the shack all day.

• qtel: EchoLink client with a basic but functional GUI.
• svxlink-server: A full-featured voice-over-IP server for ham ops.
• remotetrx: For controlling radios remotely.

Also found svxreflector and GPIO tools for hardware control—perfect if you’re building a repeater or node.

Logging & Contesting

• xlog: A solid GTK+ logger. Lightweight, gets the job done.
• pyqso: Python-based, good for scripting or minimalist use.
• tlf: Console-based contest logger—perfect if you like living in the terminal.

One Command to Grab Everything

If you just want to explore, Debian offers a meta-package:

sudo apt install task-hamradio-blend

That’ll pull in a bunch of packages related to amateur radio, SDR, and digital comms. Saves a lot of time.

Final Thoughts

Running amateur radio on Linux used to feel like a hacky workaround. Today? It’s actually pretty smooth—at least on Debian. The tools are all right there in the official repos, and most are maintained well enough to be usable out of the box.

The post What Debian Offers for Amateur Radio in APT appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Amateur radio operators often use various software for digital modes, packet radio, SDR, logging, and hotspot management. Docker containers make installing and running these apps easier and more consistent, regardless of your OS or environment.

Below is a curated list of top amateur radio software that either has official or community Docker images available — plus example commands so you can start using them immediately.

1. Dire Wolf – Soundcard AX.25 Packet TNC & APRS

Purpose: Software TNC for packet radio and APRS with soundcard interface.

Docker image: w6rz/direwolf

Run command example:

docker pull w6rz/direwolf

docker run -it --rm \
  --device /dev/snd \
  --device /dev/ttyUSB0 \
  -v $HOME/direwolf:/root \
  w6rz/direwolf

• Mounts your local config directory.
• Accesses sound and radio devices.
• Configure direwolf.conf inside your $HOME/direwolf folder.

2. OpenWebRX – Web-Based SDR Receiver

Purpose: Run a remote software-defined radio (SDR) accessible via web browser.

Docker image: cyoung/openwebrx

Run command example:

docker pull cyoung/openwebrx

docker run -d -p 8073:8073 cyoung/openwebrx

• Access the SDR web interface at http://localhost:8073
• Connect and listen from anywhere on your network.

3. WSJT-X – FT8 and Other Weak Signal Digital Modes

Purpose: Decode weak digital signals like FT8, JT65.

Docker image: No official image, but community versions exist (e.g., jks-prv/wsjtx).

Run command example:

docker pull jks-prv/wsjtx

docker run -d -p 5900:5900 jks-prv/wsjtx

• Runs a VNC server on port 5900 to access the GUI.
• Connect using a VNC client to localhost:5900.

4. Fldigi – Multi-Mode Digital Modem

Purpose: Supports many digital modes: PSK31, RTTY, MFSK, Olivia, and more.

Docker image: Community-built images exist (e.g., ka6sox/fldigi).

Run command example with X11 forwarding (Linux):

xhost +local:docker

docker run -it --rm \
  -e DISPLAY=$DISPLAY \
  -v /tmp/.X11-unix:/tmp/.X11-unix \
  --device /dev/snd \
  ka6sox/fldigi

• Access GUI directly on your desktop.
• Use sound devices for digital mode decoding.

5. Pi-Star – Digital Voice Hotspot Software (DMR, YSF, P25)

Purpose: Popular for managing digital voice hotspots.

Docker image: Community image (e.g., wm5d/pi-star).

Run command example:

docker pull wm5d/pi-star

docker run -d -p 80:80 -p 22222:22222 wm5d/pi-star

• Access the Pi-Star dashboard via http://localhost
• Configure your digital voice hotspot remotely.

6. Chirp – Radio Programming Software

Purpose: Program handheld radios easily.

Docker image: Community images available.

Run command example with GUI (X11 forwarding):

xhost +local:docker

docker run -it --rm \
  -e DISPLAY=$DISPLAY \
  -v /tmp/.X11-unix:/tmp/.X11-unix \
  yourusername/chirp

Bonus: Managing Multiple Ham Radio Containers with Docker Compose

Create a docker-compose.yml file to run multiple services together (e.g., Dire Wolf and OpenWebRX):

version: '3'
services:
  direwolf:
    image: w6rz/direwolf
    devices:
      - /dev/snd
      - /dev/ttyUSB0
    volumes:
      - ./direwolf:/root
    stdin_open: true
    tty: true

  openwebrx:
    image: cyoung/openwebrx
    ports:
      - "8073:8073"

Run all at once:

docker-compose up

Summary Table of Top Ham Radio Docker Containers

Final Thoughts

Running amateur radio software inside Docker containers lets you:

• Avoid complicated installations.
• Run your apps anywhere without changes.
• Experiment with new software without risk.
• Easily manage dependencies and updates.

The post Top Amateur Radio Software You Can Run Using Docker: Practical Examples appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

In the world of amateur radio, we often become captivated by the latest transceivers, cutting-edge antenna designs, and sophisticated digital modes. While these technological marvels rightfully deserve our attention, there’s a humble yet indispensable tool that many operators overlook: the compass. This simple navigational instrument has been guiding explorers, soldiers, and adventurers for centuries, and it remains just as relevant for today’s amateur radio operator.

Whether you’re a casual weekend warrior setting up for a Parks on the Air activation, a dedicated DXer optimizing your beam antenna, or an emergency communicator preparing for disaster response, a quality compass can be the difference between successful communication and frustrating silence. In this comprehensive guide, we’ll explore everything you need to know about compasses in amateur radio, from basic principles to advanced applications.

Understanding How Compasses Work: The Science Behind the Magic

The Fundamentals of Magnetic Navigation

At its core, a traditional compass operates on one of nature’s most fundamental forces: magnetism. The Earth itself acts as a giant magnet, with magnetic field lines flowing from the magnetic south pole to the magnetic north pole. The magnetized needle in your compass aligns itself with these invisible field lines, creating a reliable reference point that has guided humanity for over a thousand years.

However, there’s an important distinction that every amateur radio operator should understand: magnetic north is not the same as true north. True north points to the geographic North Pole, while magnetic north points to the magnetic north pole, which is currently located in northern Canada and moves approximately 25 miles per year. This difference, called magnetic declination or variation, varies depending on your location and can range from 0° to over 20° in some areas.

Types of Compasses and Their Applications

Modern compasses come in several distinct varieties, each optimized for specific use cases:

Magnetic Compasses (Traditional Analog) These are the classic liquid-filled compasses with a floating needle. They’re simple, reliable, and require no power source. The liquid dampening prevents excessive needle oscillation and provides smooth, stable readings even in windy conditions.

Lensatic Compasses (Military-Style Precision) Originally developed for military use, these compasses feature a hinged cover with a sighting wire and a lens for precise bearing measurements. They’re built to withstand extreme conditions and often include tritium illumination for night use.

Baseplate Compasses (Orienteering Style) Popular among hikers and orienteers, these compasses are mounted on a clear plastic baseplate with rulers and scales. They’re designed for map work and route planning, making them excellent for antenna site surveys and field operations.

Digital Compasses and Electronic Solutions Modern smartphones, GPS units, and dedicated electronic compasses use magnetometers and sometimes gyroscopes to determine direction. While convenient, they require power and can be affected by electronic interference from radio equipment.

Mirror Sighting Compasses These combine the accuracy of lensatic compasses with the map-work capabilities of baseplate compasses. The mirror allows for precise bearing shots while also serving as an emergency signaling device.

Why Every Amateur Radio Operator Needs a Compass

1. Directional Antenna Optimization: Getting Every dB

For amateur radio operators using directional antennas, precise alignment isn’t just helpful—it’s absolutely critical. Whether you’re operating a simple 2-meter Yagi or a massive HF beam array, pointing your antenna in the right direction can mean the difference between successful communication and complete failure.

Consider this scenario: you’re trying to work a rare DX station in Japan from your location in the eastern United States. Your beam antenna has a 3dB beamwidth of about 60°, which might seem forgiving, but being off by just 10-15° could cost you 1-2 dB of signal strength. In weak signal conditions, this seemingly small error could make your signal unreadable at the receiving end.

Professional antenna installations often require pointing accuracy within 1-2°, and while amateur installations might not need to be quite that precise, even casual operators can benefit from improved accuracy. A good compass allows you to:

• Accurately determine the bearing to your target location
• Properly align rotatable beam antennas
• Optimize fixed antenna installations during the planning phase
• Troubleshoot propagation issues by verifying antenna pointing

2. Portable and Emergency Operations: Navigation in the Field

Amateur radio’s strength lies partly in its portability and usefulness during emergencies. When you’re operating away from your comfortable home station—whether for SOTA (Summits on the Air), POTA (Parks on the Air), Field Day, or emergency response—a compass becomes an essential tool for several reasons:

Site Selection and Setup When arriving at a new operating location, understanding the terrain’s orientation helps you make informed decisions about antenna placement. If you know that the nearest repeater or your target contact area lies to the northeast, you can position your antenna and operating position accordingly.

Navigation and Safety In remote locations, especially during SOTA activations on mountain peaks, weather can change rapidly and visibility can become severely limited. Your GPS might fail, or its battery might die. A compass provides a reliable backup navigation method that could literally save your life.

Coordination with Other Operators When working with multiple operators in the field, being able to communicate precise bearings helps coordinate activities. “The noise is coming from 135°” is much more useful than “the noise is coming from over there somewhere.”

3. Amateur Radio Direction Finding (ARDF): The Art of the Hunt

Amateur Radio Direction Finding, also known as “fox hunting” or “transmitter hunting,” is both a competitive sport and a practical skill. Participants use specialized equipment and techniques to locate hidden transmitters, and a compass is absolutely essential for this activity.

Competition Fox Hunting In ARDF competitions, participants must locate multiple hidden transmitters in a wooded area using only their radio equipment and navigation skills. Success requires the ability to take accurate bearings from multiple locations and triangulate the transmitter’s position. Even small bearing errors can lead you miles off course.

Practical RFI Hunting When tracking down interference sources in your neighborhood, the same principles apply. By taking bearings from multiple locations and plotting them on a map, you can narrow down the interference source’s location before beginning detailed investigation.

Search and Rescue Applications Emergency responders sometimes use ARDF techniques to locate emergency beacons or lost persons carrying radios. The ability to quickly and accurately determine bearing to a signal source can be crucial in life-or-death situations.

4. HF Propagation and DXing: Understanding the Path

For HF operators, especially those interested in DX (long-distance) communication, understanding signal paths and propagation is crucial. A compass helps you:

Great Circle Bearing Calculations The shortest path between two points on Earth’s surface follows a great circle route, which often differs significantly from what appears shortest on a flat map. Knowing the great circle bearing to your target helps optimize antenna pointing for maximum signal strength.

Propagation Prediction and Analysis Understanding where your signal is going helps interpret propagation predictions and band conditions. If propagation to Europe is good but you’re hearing nothing on 20 meters, checking your antenna bearing might reveal that it’s pointed toward the Pacific instead.

Multi-Path Analysis Some HF signals can arrive via multiple propagation paths simultaneously. Understanding the geometry involved helps explain why signals sometimes sound distorted or have flutter.

Advanced Compass Applications in Amateur Radio

Magnetic Declination: The Critical Adjustment

One of the most important concepts for amateur radio operators to understand is magnetic declination. This is the angular difference between magnetic north (where your compass points) and true north (the actual direction to the North Pole). Declination varies significantly based on your location and changes slowly over time.

For example, if you’re operating from New York City, your magnetic declination is approximately 13° West, meaning your compass points 13° west of true north. If you’re trying to point your antenna toward Europe using a bearing calculated from true north, you’ll need to add 13° to that bearing when using your compass.

Most quality compasses include adjustable declination correction, allowing you to set the compass to show true bearings directly. This eliminates the need for mental math in the field and reduces the chance of errors.

Site Surveys and Antenna Planning

Before installing any significant antenna system, conducting a proper site survey is essential. A compass plays several important roles in this process:

Obstacle Analysis By taking bearings to various obstacles (trees, buildings, power lines), you can create accurate maps showing where antenna placement might be problematic. This is especially important when planning directional antennas that need clear paths in specific directions.

Ground Slope Analysis Many compasses include clinometers (inclinometers) that measure ground slope. This information is crucial when planning guy wires for towers or determining optimal locations for ground plane antennas.

Property Line Verification When installing antennas near property boundaries, accurate bearing measurements help ensure compliance with local setback requirements and maintain good neighbor relations.

Integration with Modern Technology

While traditional compasses remain valuable, they work best when integrated with modern technology:

GPS and Mapping Software Combining compass bearings with GPS coordinates allows for precise plotting on digital maps. Many mapping applications can display both magnetic and true bearings, making it easier to correlate compass readings with digital information.

Smartphone Apps While not replacements for dedicated compasses, smartphone compass apps can be useful for quick checks and preliminary planning. However, be aware that phones can be affected by magnetic interference from radio equipment.

APRS Integration For operators using APRS (Automatic Packet Reporting System), accurate position and bearing information can be crucial for effective communication and coordination with other stations.

Comprehensive Compass Recommendations for Amateur Radio

Choosing the right compass depends on your specific needs, operating style, and budget. Here are detailed recommendations across various categories:

Premium Professional Compasses

Suunto MC-2G Global Compass Price Range: $80-120

This is often considered the gold standard for serious outdoor professionals. The MC-2G features a global needle that works accurately anywhere on Earth, eliminating the need for different compasses in different geographic zones. Key features include:

• Adjustable declination correction with easy-to-use tool
• Mirror for precise bearing shots and emergency signaling
• Clinometer for measuring slope angles
• Luminous markings for low-light conditions
• Sapphire jewel bearing for long-term accuracy
• Temperature compensation for consistent readings

Best for: Serious SOTA/POTA operators, emergency communicators, and operators who travel internationally.

Brunton TruArc 20 Price Range: $70-100

Designed for professional surveyors and outdoor guides, this compass offers exceptional accuracy and durability. Features include:

• Global needle system for worldwide use
• Tool-free declination adjustment
• Built-in clinometer with percentage and degree scales
• Rare earth magnet for fast needle settling
• Sapphire jewel bearing
• Waterproof construction

Best for: ARDF competitors, antenna installers, and operators requiring surveyor-grade accuracy.

Military-Grade Durability

Cammenga 27CS Lensatic Compass (Tritium) Price Range: $120-180

This is the same compass used by the U.S. military and represents the pinnacle of mechanical compass durability. Key features:

• Self-luminous tritium dial markings (no batteries required)
• Waterproof to considerable depths
• Shock-resistant construction
• Copper induction damping for steady needle
• Magnifying lens for precise readings
• Lifetime warranty

Best for: Emergency responders, military operators, and anyone requiring maximum durability.

Silva Ranger 2.0 Price Range: $50-80

A excellent compromise between professional features and reasonable cost. This compass has been trusted by military forces worldwide:

• High-quality mirror sighting system
• Built-in inclinometer
• Adjustable declination
• Robust construction suitable for harsh conditions
• Luminous markings
• Lanyard included

Best for: Field Day operations, emergency kits, and general outdoor use.

Budget-Friendly Options

Suunto A-10 Recreational Compass Price Range: $20-35

While basic, this compass offers surprising accuracy for its price point:

• Simple, reliable operation
• Fixed declination scale
• Luminous markings
• Lightweight and compact
• Perfect for beginners

Best for: New operators, backup compass, or casual use.

Coghlan’s Pin-On Ball Compass Price Range: $8-15

Ultra-compact option for minimal weight situations:

• Weighs less than 0.5 ounces
• Pin-on design for easy attachment
• Surprisingly accurate for its size
• Liquid-filled for stability

Best for: Ultralight SOTA operations or emergency kit addition.

Electronic and Digital Options

Garmin Foretrex 701 Ballistic Edition Price Range: $400-500

This wrist-mounted GPS unit includes a high-quality digital compass:

• 3-axis compass with tilt compensation
• GPS and GLONASS compatibility
• APRS messaging capability
• Night vision compatibility
• Extremely rugged construction
• Long battery life

Best for: Technical operators, SAR teams, and military communications.

Garmin eTrex 32x Price Range: $200-250

Handheld GPS with excellent compass capabilities:

• 3-axis tilt-compensated compass
• Preloaded TopoActive maps
• Paperless geocaching support
• 25-hour battery life
• Rugged, waterproof design

Best for: SOTA/POTA operators who want GPS and compass in one unit.

Practical Tips for Using Compasses in Amateur Radio

Avoiding Common Mistakes

Magnetic Interference Radio equipment can significantly affect compass accuracy. Keep your compass at least 3-6 feet away from:

• Transceivers and power supplies
• Metal antenna elements
• Vehicle engines and electrical systems
• Large metal structures

Reading Errors Always ensure the compass is level when taking readings. Tilt can introduce significant errors, especially with basic compasses.

Declination Confusion Always verify whether your calculations require magnetic or true bearings, and adjust accordingly.

Advanced Techniques

Triangulation for ARDF Take bearings from at least three different locations to accurately pinpoint a transmitter’s location. The intersection of bearing lines on your map shows the target location.

Back-Bearings for Navigation When hiking to a remote operating location, periodically take back-bearings to known landmarks. This helps ensure you can find your way back if conditions deteriorate.

Bearing Averaging In windy conditions or when maximum accuracy is needed, take multiple readings and average them for better precision.

Integration with Maps and Planning Tools

Using Topographic Maps

Understanding how to use your compass with topographic maps opens up advanced possibilities:

Contour Line Analysis Topographic maps show elevation changes through contour lines. This information helps predict line-of-sight paths for VHF/UHF communications and identifies potential RF reflection points.

UTM Grid References Many modern maps include UTM (Universal Transverse Mercator) grid systems that work well with GPS coordinates and compass bearings.

Digital Map Integration

Google Earth and Mapping Software Most mapping applications can display magnetic declination information and show both true and magnetic bearings. This makes it easy to plan antenna orientations before arriving at your operating location.

Propagation Prediction Tools When using HF propagation prediction software, accurate bearing information helps interpret predictions and optimize antenna pointing.

Emergency Preparedness and Compass Use

Building Emergency Kits

Every amateur radio emergency kit should include a quality compass. Consider these factors:

Redundancy Include both a primary compass and a backup. Different types (mechanical and electronic) provide redundancy against different failure modes.

Waterproofing Ensure your compass can survive harsh weather conditions. Many emergencies occur during severe weather when navigation becomes most challenging.

Lighting Choose compasses with luminous markings or include a small flashlight or red LED light for night use.

Search and Rescue Applications

Amateur radio operators often support search and rescue operations. Compass skills become critical in these situations:

Grid Search Coordination SAR operations often use grid search patterns that require precise navigation. Being able to follow and report accurate bearings is essential.

Resource Location When coordinating multiple search teams, being able to provide accurate directions to resources (water, shelters, hazards) using compass bearings improves efficiency and safety.

International Considerations

Operating Abroad

If you travel internationally with your amateur radio equipment, consider these compass-related factors:

Magnetic Declination Variations Declination varies significantly around the world. Some areas have declination exceeding 30°, making accurate correction essential.

Global vs. Regional Compasses Some compasses are designed to work only in specific magnetic zones. Global compasses work everywhere but cost more.

Cultural and Legal Considerations Some countries have restrictions on navigation equipment. Research local regulations before traveling with compasses or GPS units.

The Science of Compass Accuracy

Understanding Limitations

Even the best compasses have limitations that amateur radio operators should understand:

Temperature Effects Extreme temperatures can affect compass accuracy. Most quality compasses include temperature compensation, but very cheap models may be significantly affected.

Magnetic Dip Near the magnetic poles, compass needles tend to point downward as well as northward. This “magnetic dip” can affect accuracy and is why some compasses are designed for specific geographic zones.

Local Magnetic Anomalies Some geographic areas have local magnetic anomalies caused by iron ore deposits or other geological features. These can cause compass errors of several degrees.

Calibration and Maintenance

Regular Calibration Checks Periodically verify your compass accuracy against known bearings. Sunrise and sunset directions can provide approximate east-west references.

Bubble Inspection Liquid-filled compasses sometimes develop bubbles over time. Small bubbles usually don’t affect accuracy, but large bubbles may indicate seal failure.

Future Technology and Compass Evolution

Emerging Technologies

MEMS Sensors Micro-electromechanical systems (MEMS) are making digital compasses smaller, more accurate, and less power-hungry. These sensors are now found in most smartphones and GPS units.

Satellite-Based Systems While GPS provides position information, emerging satellite systems may eventually provide precise heading information without relying on magnetic fields.

Integration with SDR Software-defined radio (SDR) technology might eventually integrate direction-finding capabilities directly into transceivers, potentially reducing the need for separate compass equipment.

Conclusion: Your Path to Better Communications

In our digital age, it’s easy to overlook simple tools like compasses in favor of high-tech solutions. However, as any experienced amateur radio operator will tell you, the best tools are often the simplest ones. A compass doesn’t need batteries, won’t crash, and works reliably in conditions that would disable electronic alternatives.

Whether you’re a new operator setting up your first antenna or an experienced DXer chasing rare contacts, investing in a quality compass will pay dividends in improved communications, enhanced safety, and greater confidence in your operating abilities. The compass won’t make you a better operator overnight, but it will give you the tools to make informed decisions about antenna pointing, site selection, and navigation.

Remember that like any tool, a compass is only as good as the operator using it. Take time to learn proper compass techniques, understand magnetic declination in your area, and practice using your compass in various conditions. The investment in time and money will reward you with years of improved amateur radio experiences.

From casual weekend operations to emergency communications, from competitive ARDF to serious DXing, a compass remains one of the most versatile and valuable tools in the amateur radio toolkit. Don’t let its simplicity fool you—in the hands of a knowledgeable operator, a compass can be the key to unlocking better communications and safer operations.

So the next time you’re packing your gear bag, make sure that humble compass has a place alongside your sophisticated radio equipment. Your future contacts will thank you for the stronger signals, and you’ll appreciate the confidence that comes from knowing exactly where you’re pointing your antenna and how to find your way home.

What’s your experience with compasses in amateur radio? Have you found particular models or techniques especially useful? Share your experiences with the amateur radio community—we all learn from each other’s successes and challenges.

Remember: The best compass is the one you have with you and know how to use. Start with a basic model, learn the fundamentals, and upgrade as your needs and experience grow.

The post The Amateur Radio Operator’s Guide to Compasses: Your Silent Signal Companion appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

In an era where precise time synchronization is crucial for various applications, NMEATime2 emerges as an essential tool for those relying on GPS signals to discipline their PC clocks. Whether for scientific research, radio communication, or network operations, maintaining an accurate system clock can make a significant difference. This blog post delves into the features, functionality, and benefits of NMEATime2, a software designed to synchronize your PC clock using data from a GPS receiver.

What is NMEATime2?

NMEATime2 is a specialized PC time synchronization software that disciplines the computer’s clock using data derived from an NMEA-compatible GPS receiver. By leveraging the precise timing signals from the Global Positioning System (GPS), NMEATime2 ensures that your PC maintains accurate time, reducing discrepancies and eliminating drift.

The software operates as a system service, meaning it runs in the background without requiring user intervention. Using sophisticated digital filtering techniques, it mitigates jitter and ensures high-precision clock synchronization comparable to high-end oscillators like OCXO (Oven-Controlled Crystal Oscillators) and atomic rubidium clocks.

Key Features of NMEATime2

• Advanced Digital Filtering: The software uses a control loop that disciplines the PC clock based on the NMEA strings received from the GPS unit, reducing timing jitter and improving accuracy.
• System Service Mode: Unlike conventional applications, NMEATime2 runs as a Windows service, providing continuous and reliable time synchronization.
• Compatibility with USB and Serial GPS Devices: Many modern GPS receivers connect via USB rather than RS-232. NMEATime2 is designed to work with these devices, recognizing them as USB-to-serial communication ports.
• Supports Various NMEA Sentences: The software primarily relies on the GPGGA and GPRMC messages but also utilizes GPZDA, GPGSA, and GPGSV for enhanced accuracy.
• Graphical Time Difference Plot: Users can visualize synchronization performance through a real-time plot that highlights any discrepancies and correction actions taken by the software.

System Requirements

To use NMEATime2 effectively, your system must meet the following requirements:

• Operating System: Windows 7, 8, 8.1, or Windows 10.
• A GPS receiver capable of outputting NMEA sentences via USB or a serial (RS-232) port.
• The GPS unit must be configured to transmit specific NMEA messages at defined intervals:
  • GPGGA – Must be sent once per second.
  • GPRMC – Must be sent once per second.
  • GPZDA – Must be sent once per second (preferred for time reference).
  • GPGSA – Every two seconds.
  • GPGSV – Every two seconds.

Installation and Setup

Step 1: Download and Install

NMEATime2 is available as a free trial for 30 days, after which users need to purchase a license for $20.48 USD. Before installing a new version, it is recommended to uninstall any previous versions.

Step 2: Connect Your GPS Receiver

Ensure your GPS receiver is properly connected to your PC. If using a USB GPS device, ensure that the necessary drivers are installed so that the device appears as a serial (COM) port.

Step 3: Configure the Software

• Open NMEATime2 and select the appropriate COM port where your GPS device is connected.
• Verify that the software is receiving NMEA messages from the GPS.
• Enable automatic synchronization to allow the system service to discipline the PC clock continuously.

Step 4: Monitor Performance

NMEATime2 provides a visual representation of synchronization accuracy. The red line in the Time Difference Plot represents digital filtering in action, minimizing software jitter and improving time precision.

Why Use NMEATime2?

For users requiring precise timekeeping, NMEATime2 is an excellent alternative to internet-based time synchronization methods like NTP (Network Time Protocol). Unlike NTP, which relies on network connectivity and introduces potential delays, NMEATime2 directly references GPS signals, ensuring unmatched accuracy.

Additionally, professionals in amateur radio, astronomy, and scientific research often need highly precise timekeeping. For example, APRS (Automatic Packet Reporting System) and FT8 (a digital mode for amateur radio communication) depend on accurate timestamps, making NMEATime2 a valuable tool for radio operators.

Usage in Amateur Radio

Time synchronization plays a crucial role in amateur radio, especially in digital modes and satellite tracking. Here’s how NMEATime2 benefits radio operators:

• FT8 and Other Weak Signal Digital Modes: FT8, JT65, and other weak signal modes rely on precise timing to ensure successful communication. Even a small time drift can prevent successful decoding of signals. NMEATime2 ensures that your PC clock stays in sync with GPS time, reducing the risk of missed contacts.
• APRS and Packet Radio: APRS (Automatic Packet Reporting System) relies on accurate timestamps for proper data transmission. A synchronized PC clock ensures correct timing in beacon transmissions, making tracking and messaging more reliable.
• Satellite Communication and Doppler Shift Correction: Many amateur radio operators work with satellites for communication, requiring precise tracking and Doppler shift adjustments. Accurate time synchronization allows for better satellite pass predictions and automated frequency corrections.
• EME (Moonbounce) Communication: Earth-Moon-Earth (EME) communication demands ultra-precise timing due to the time delay introduced by signal travel between Earth and the Moon. NMEATime2 helps maintain synchronization, ensuring accurate transmission and reception windows.
• Contest Logging and DX Clusters: Many logging software solutions require accurate timestamps for contest logging and DX spotting. Using NMEATime2 ensures that logs remain consistent with real-time events, preventing discrepancies in contest submissions.

Final Thoughts

NMEATime2 stands out as a robust and reliable solution for PC time synchronization using GPS data. Whether for professional or personal use, it provides a straightforward yet highly accurate method to maintain precise system time. At an affordable price of $20.48, it is a worthwhile investment for anyone who requires GPS-disciplined time synchronization.

If you need accurate PC timekeeping without relying on network-based synchronization, give NMEATime2 a try. The 30-day free trial allows users to evaluate its performance before making a purchase decision.

For more information and to download the software, visit the official website or purchase via PayPal to receive your registration key within 48 hours.

The post NMEATime2: PC GPS Time Synchronization Software appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

APRS (Automatic Packet Reporting System) is a digital communications system used by amateur radio operators for local tactical communications and position tracking. An iGate (internet gateway) receives these radio packets and relays them to the internet, contributing valuable data to the global APRS network.

This guide, originally developed by KM6LYW, demonstrates how to build a receive-only APRS iGate using affordable components. For just $99, one can create a system that displays real-time APRS traffic including text messages, weather reports, beacons, positions, and object information.

Why Build an APRS iGate?

1. The APRS network benefits from more iGates to improve coverage
2. It’s an educational project combining radio, computing, and networking
3. Visualizing local APRS traffic in real-time is informative
4. It’s an affordable entry point into digital amateur radio

Parts List ($99 Total)

• $18 – Raspberry Pi Zero 2 W with headers (Adafruit)
• $4 – USB adapter cable (Amazon)
• $31 – RTL-SDR software defined radio (Amazon)
• $32 – Roll-up antenna (eBay)
• $14 – LCD Display (Amazon)

Software Installation

Update the Raspberry Pi and install the necessary packages:

sudo apt-get update
sudo apt-get install direwolf rtl-sdr git python3-pip fonts-dejavu python3-pil python3-pyinotify python3-numpy
sudo pip3 install --break-system-packages adafruit-circuitpython-rgb-display
sudo pip3 install --break-system-packages aprslib
git clone https://github.com/craigerl/direwatch...

Configuration

1. Enable SPI by editing the configuration file:

sudo nano /boot/firmware/config.txt
# Uncomment the spi line:
# dtparam=spi=on

2. Reboot the Raspberry Pi to apply the changes.
3. Create a Direwolf configuration file:

sudo nano direwolf.conf

4. Add the following configuration, replacing NOCALL with your amateur radio callsign and updating your GPS coordinates:

MYCALL NOCALL
IGSERVER noam.aprs2.net
IGLOGIN NOCALL 12345
PBEACON sendto=IG compress=1 delay=00:15 every=30:00 symbol="igate" overlay=X lat=39.911 long=-122.935 comment="Direwatch Rx-only igate"
AGWPORT 8000
KISSPORT 8001
ADEVICE null

Launching the iGate

Navigate to the direwatch directory and run the following commands:

cd direwatch
rtl_fm -s 22050 -g 49 -f 144.39M 2> /dev/null | direwolf -t 0 -r 22050 - > direwolf.log &
./direwatch.py -o -l direwolf.log -t "APRS"

Note: The standard APRS frequency in North America is 144.39MHz. This frequency may need to be adjusted depending on region.

What’s Happening?

1. The RTL-SDR receives radio signals on the APRS frequency
2. Direwolf decodes the APRS packets and logs them
3. The direwatch script displays the decoded information on the LCD screen
4. Packets are simultaneously relayed to the APRS-IS network via the internet

This iGate is now operational, contributing to the global APRS network while providing a real-time display of local APRS traffic.

Final Notes

This project, designed by KM6LYW, serves as an introduction to digital amateur radio and the APRS ecosystem. Building more iGates improves the network for everyone, and the visual feedback makes it an engaging project even for beginners.

For more detailed instructions and additional configuration options, visit the Direwatch GitHub repository.

(Note: An amateur radio license is required to legally transmit on these frequencies)

The post Building a $99 APRS Packet iGate in Under 10 Minutes appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

In a world where digital communication is often subject to surveillance, censorship, and centralized control, Reticulum stands as a revolutionary solution. Designed as a cryptography-based networking stack, Reticulum empowers individuals and communities to build local and wide-area networks using readily available hardware. Unlike traditional networking technologies, Reticulum operates efficiently even under extreme conditions, such as high latency and ultra-low bandwidth.

Reticulum is more than just a network—it is a tool for creating thousands of independent and autonomous networks that interconnect seamlessly. These networks are designed to function without kill-switches, external control, or centralized oversight, allowing users to communicate freely and securely. Reticulum enables sovereign, censorship-resistant, and decentralized communication, making it a game-changer for those seeking privacy, security, and resilience in their networks.

Unlike conventional network stacks, Reticulum does not rely on the IP protocol or higher layers. However, it can still be encapsulated over IP networks, allowing users to tunnel Reticulum traffic through the Internet or private IP infrastructures when necessary. By eliminating dependencies on traditional networking protocols, Reticulum optimizes performance and security. The stack is built directly on cryptographic principles, ensuring stable and resilient functionality even in trustless and adversarial environments.

One of the most remarkable aspects of Reticulum is its ease of deployment. It requires no kernel modules or special drivers, making it incredibly lightweight and accessible. Running entirely in user space, Reticulum can be installed on virtually any system that supports Python 3, from personal computers and embedded devices to large-scale infrastructure. This versatility ensures that users can establish secure and sovereign communication networks without specialized or expensive hardware.

Reticulum: A New Era of Secure Networking

Reticulum is the cryptography-based networking stack for building local and wide-area networks with readily available hardware. It can operate even with very high latency and extremely low bandwidth. Reticulum allows you to build wide-area networks with off-the-shelf tools, and offers end-to-end encryption and connectivity, initiator anonymity, autoconfiguring cryptographically backed multi-hop transport, efficient addressing, unforgeable delivery acknowledgements and more.

The vision of Reticulum is to allow anyone to be their own network operator, and to make it cheap and easy to cover vast areas with a myriad of independent, inter-connectable and autonomous networks. Reticulum is not one network. It is a tool for building thousands of networks. Networks without kill-switches, surveillance, censorship and control. Networks that can freely interoperate, associate and disassociate with each other, and require no central oversight. Networks for human beings. Networks for the people.

Reticulum is a complete networking stack, and does not rely on IP or higher layers, but it is possible to use IP as the underlying carrier for Reticulum. It is therefore trivial to tunnel Reticulum over the Internet or private IP networks.

Having no dependencies on traditional networking stacks frees up overhead that has been used to implement a networking stack built directly on cryptographic principles, allowing resilience and stable functionality, even in open and trustless networks.

No kernel modules or drivers are required. Reticulum runs completely in userland, and can run on practically any system that runs Python 3.

Reticulum: The Unstoppable, Sovereign Networking Stack

A Vision for Sovereign Communication

Reticulum is more than just a network—it’s a framework for building thousands of independent networks. Unlike traditional systems, Reticulum eliminates the need for central control, allowing anyone to operate their own sovereign communication infrastructure. The key vision behind Reticulum is to empower individuals and communities to create networks that are free from surveillance, censorship, and external control.

With Reticulum, users can establish highly secure communication channels, ensuring that their data remains private and tamper-proof. This is particularly crucial in regions where communication restrictions are imposed, or in emergency scenarios where traditional networks fail.

What Makes Reticulum Different?

While Reticulum serves the same fundamental purpose as other networking stacks—moving data reliably from one point to another—it does so in a completely different way. Here are some notable characteristics that set Reticulum apart:

Privacy & Security by Default

• Reticulum does not use source addresses in transmitted packets, making it impossible to trace the origin of communication.
• All encryption keys are ephemeral and provide forward secrecy, ensuring that past communications remain secure even if future keys are compromised.
• It is impossible to send or receive unencrypted packets within Reticulum, eliminating vulnerabilities associated with unprotected data transmission.

Decentralization & Sovereignty

• There is no central authority controlling address allocations; users can create addresses as needed.
• Once an address is generated, it remains globally reachable and portable, meaning it can be moved across different locations in the network while staying accessible.
• Networks built on Reticulum are self-configuring and resilient, adapting to various communication mediums seamlessly.

Interconnectivity & Versatility

• Reticulum supports a wide range of communication hardware, including LoRa radios, AX.25 packet radio TNCs, WiFi, Ethernet, serial devices, and even free-space optical links.
• It allows seamless integration over existing IP networks (TCP/UDP), meaning it can function over wired and wireless infrastructure while maintaining security and decentralization.
• By combining multiple communication mediums, Reticulum enables the creation of dynamic, self-healing mesh networks that are highly resistant to disruptions.

Supported Hardware & Interfaces

Reticulum is designed to work over virtually any medium that can sustain a half-duplex connection with at least 500 bits per second throughput. Some of the supported hardware and interfaces include:

• Ethernet and WiFi devices
• LoRa radios using RNode
• Packet radio TNCs (AX.25 and KISS-compatible)
• Any serial-based communication device
• TCP and UDP over IP networks
• Custom hardware via standard input/output (stdio) and pipes

For example, a simple Raspberry Pi setup connected to a LoRa radio, a packet radio TNC, and a WiFi network would allow devices on each of these mediums to communicate seamlessly, thanks to Reticulum’s self-configuring architecture.

How to Get Started with Reticulum

Getting started with Reticulum depends on your intended use case. However, installation is straightforward using Python’s package manager:

pip install rns

Once installed, you can start Reticulum manually or set it up as a system service using the rnsd utility. The first time Reticulum runs, it automatically generates a configuration file that helps you connect with local peers and expand the network from there.

For more details, consult the Getting Started Fast section of the Reticulum Manual.

Included Utilities for Network Management

Reticulum comes with several built-in utilities to simplify network setup and maintenance:

• rnsd – Runs Reticulum as a background service.
• rnstatus – Displays real-time information about network interfaces.
• rnpath – Manages and views routing paths.
• rnprobe – Diagnoses connectivity to specific destinations.
• rncp – Transfers files securely between nodes.
• rnx – Executes remote commands over Reticulum networks.

These tools ensure that even networks operating over extremely low-bandwidth mediums, such as LoRa or packet radio, function efficiently and reliably.

Applications Built on Reticulum

Reticulum powers several innovative applications that demonstrate its capabilities:

• Nomad Network – An off-grid, encrypted, and resilient mesh communication platform.
• Sideband – A user-friendly graphical messaging app for Linux, Android, and macOS.
• LXMF – A distributed, delay-tolerant messaging protocol designed for asynchronous communication.

These projects showcase Reticulum’s ability to facilitate secure and decentralized digital interactions without reliance on traditional internet infrastructure.

Performance & Future Development

Reticulum is optimized for a broad range of performance scenarios, with speeds ranging from 150 bits per second to 40 megabits per second across different mediums. While development continues, the focus remains on expanding functionality for low-bandwidth networks, ensuring long-term resilience and adaptability.

Join the Reticulum Community

If you’re interested in exploring Reticulum, the community offers multiple channels for support and discussion:

• GitHub Discussions
• Matrix Channel: #reticulum
• Reticulum Subreddit

Since Reticulum is still in beta, users should be aware of potential bugs or security improvements in future releases. However, its current stability and effectiveness make it a compelling choice for those seeking secure, decentralized communication solutions.

Conclusion

Reticulum represents a paradigm shift in digital communication, offering a powerful, censorship-resistant alternative to traditional networking protocols. Whether you’re building an off-grid messaging system, a disaster-resilient infrastructure, or simply seeking an alternative to centralized networks, Reticulum provides the tools to create truly sovereign and unstoppable communication systems.

Are you ready to take control of your own network? Install Reticulum today and start building the future of decentralized, autonomous communication!

For more info, visit https://github.com/markqvist/Reticulum

The post Reticulum: The Future of Secure and Resilient Networking appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Understanding DX Spider in Amateur Radio

Amateur radio, often called “ham radio,” is a fascinating hobby that connects enthusiasts across the globe through wireless communication. At the heart of this global network lies sophisticated software like DX Spider, a critical tool that revolutionizes how radio operators share information and track contacts worldwide.

What is DX Spider?

DX Spider is an open-source cluster software that serves as a sophisticated communication hub for amateur radio operators. Developed by a community of passionate ham radio enthusiasts, it provides a robust platform for:

• Real-time sharing of radio station spots
• Tracking rare DX (long-distance) contacts
• Facilitating global communication across multiple network nodes
• Providing a collaborative platform for radio enthusiasts

The Importance of Network Security

In the interconnected world of amateur radio, security is not just a technical requirement—it’s a community responsibility. An unsecured DX Spider node can:

• Introduce vulnerabilities to the entire amateur radio network
• Allow unauthorized access and potential misuse
• Compromise the integrity of communication channels
• Risk disrupting valuable communication infrastructure

Who Should Read This Guide?

This comprehensive security guide is essential for:

• DX Spider node system operators (sysops)

Essential Security Measures for DX Spider Clusters

1. Keep Your Cluster Software Updated

Regularly updating your DX Spider software is the first line of defense against potential security threats.

Why Updates Matter:

• Patch known vulnerabilities
• Improve system performance
• Add new security features
• Ensure compatibility with latest network standards

Update Procedure:

1. Download the Update Verification Script wget -q https://raw.githubusercontent.com/EA3CV/dxspider_info/main/check_build.pl
2. Move the Script to Appropriate Directory mv check_build.pl /spider/local_cmd/
3. Automate Version Checks with Crontab
   • Edit the crontab file: nano /spider/local_cmd/crontab
   • Add automated update check: 18 03 * * 1,2,3,4,5 spawn('cd /spider/local_cmd; wget -q https://raw.githubusercontent.com/EA3CV/dxspider_info/main/check_build.pl -O /spider/local_cmd/check_build.pl')
   Note: Use crontab.guru for syntax verification, keeping in mind DXSpider’s unique crontab configuration

2. Limit and Secure Node Connections

Controlling network connections is crucial for maintaining system integrity and preventing network overload.

Connection Best Practices:

• Limit connections to 4-6 trusted nodes
• Use strong, unique passwords
• Verify the reputation of connected nodes

Connection Setup Procedure:

1. Coordinate with Partner Node Sysop
   • Establish trust
   • Agree on secure connection parameters
2. Configure Connection in DX Spider Console set/register <partner_call> set/spider <partner_call> set/password <partner_call> <strong_password>
3. Edit Connection Configuration File nano /spider/connects/<partner_call>
4. Add Password Authentication 'word:' '<your_secure_password>'

3. Identify and Avoid Insecure Nodes

Protect your network by being selective about node connections.

Red Flags: Avoid Nodes That:

• Run outdated or unsupported software versions
• Allow unrestricted spot submissions
• Lack proper user connection logging
• Have connections with other known insecure nodes

Evaluation Checklist:

• Request software version information
• Check node connection logs
• Verify authentication mechanisms
• Assess overall network hygiene

4. Implement Strict User Registration

Controlling user access is fundamental to maintaining a secure DX Spider cluster.

Registration Benefits:

• Prevent unauthorized spot submissions
• Create accountability
• Reduce spam and network abuse
• Enhance overall network trust

User Registration Procedure:

1. Modify Startup Configuration nano /spider/scripts/startup
2. Set Security Variables set/var $main::reqreg = 1 # Restrict spotting to registered users set/var $main::passwdreq = 0 # Password required for spot submission
3. Register Users set/register <callsign> set/password <callsign> <secure_password>
4. Password Distribution
   • Use secure communication channels
   • Send credentials via encrypted email
   • Use private messaging platforms
   • Avoid public communication methods

Additional Security Recommendations

Monitoring and Logging

• Implement comprehensive logging
• Regularly review connection logs
• Set up alerts for suspicious activities

Backup and Recovery

• Maintain regular system backups
• Create disaster recovery plans
• Test restoration procedures periodically

Community Collaboration

• Stay informed about network security trends
• Participate in amateur radio security forums
• Share best practices with fellow sysops

Conclusion

Securing your DX Spider cluster is an ongoing commitment to the amateur radio community. By implementing these comprehensive security measures, you contribute to a more robust, reliable, and trustworthy global communication network.

Original Guide Compiled By: Mikel EA2CW

Stay Secure, Stay Connected! 73

The post Securing Your DX Cluster: Essential Measures to Minimize Attacks appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Prerequisites

Before starting, make sure you have:

• A Verotelecom VGC VR-N76 radio
• An Android device with Bluetooth
• APRSDroid installed (Download here)
• A valid APRS-IS passcode (visit https://pass.hamradio.my)
• A registered APRS callsign with SSID (e.g., 9M2PJU-7)

Step-by-Step Setup

1. Enable Bluetooth on the VR-N76

1. Power on the VR-N76 and ensure Bluetooth is enabled.
2. Enter the Bluetooth settings from the radio menu.
3. Make the radio discoverable so that the Android device can detect it.

2. Pair the VR-N76 with Your Android Device

1. Open the Bluetooth settings on your Android device.
2. Search for available devices and select VR-N76.
3. If prompted, enter the default pairing code (0000 or 1234).
4. Confirm that the device is successfully connected.

3. Configure APRSDroid

1. Open APRSDroid and navigate to Preferences.
2. Under Connection Protocol, select Bluetooth KISS TNC.
3. Tap TNC Bluetooth Device and select VR-N76 from the list.

4. Start APRS Transmission

1. Return to the main screen in APRSDroid.
2. Tap Start Tracking to initiate communication with the KISS TNC.
3. Watch for APRS packets being received and transmitted.
4. Check your APRS location on aprs.fi by searching your callsign.

5. Troubleshooting Tips

• If APRSDroid fails to connect, ensure Bluetooth is enabled on both devices.
• Try re-pairing the Bluetooth connection and restarting APRSDroid.
• Verify the KISS TNC settings.
• Make sure the VR-N76 is configured correctly for packet transmission.

Conclusion

With the Verotelecom VGC VR-N76 and APRSDroid, you can easily integrate APRS functionality into your mobile setup without additional hardware. This setup is great for tracking your location, sending messages, and viewing APRS traffic in real-time.

I’ve also created a YouTube video demonstration showing the full setup and testing process. Watch it here:

If you have any questions or run into issues, feel free to leave a comment below or reach out on hamradio.my.

Buy Verotelecom VGC VR-N76 here https://www.verotelecom.com/VR-N76-Dual-Band-Handheld-Radio-p2511333.html?parent_user_id=18552174&utm_source=sns_share&utm_medium=share_url

The post Setting Up Bluetooth KISS TNC on Verotelecom VGC VR-N76 with APRSDroid appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.