A Windows communication system for sending messages, files and structured emergency traffic directly over VHF/UHF FM or HF β without the Internet, Winlink or any central server.
Guardian turns a Windows PC and an amateur-radio transceiver into an independent digital messaging station.
Instead of relying on the Internet or a central messaging service, Guardian communicates directly over radio.
Operators can compose an email-like message, attach files, address it to another callsign and send it across an amateur-radio network.
Guardian handles:
- radio control;
- station discovery;
- route selection;
- relay stations;
- frequency changes;
- message queues;
- VARA data transfer;
- delivery tracking.
The result is a decentralized store-and-forward radio messaging network that can continue operating when normal network infrastructure is unavailable.
Guardian is designed for licensed amateur-radio operation, experimentation and emergency-communications exercises. It is not a certified public-safety or life-safety system.
Most digital amateur-radio applications solve one specific part of the communication chain.
Guardian tries to connect the entire workflow.
Compose a message
β
βΌ
Find destination
β
ββββββββ΄ββββββββ
β β
Direct RF Relay path
β β
ββββββββ¬ββββββββ
β
βΌ
Negotiate radio link
β
βΌ
VARA FM / HF
β
βΌ
Message + files
β
βΌ
Delivery receipt
Guardian uses short ARDOS control transmissions to coordinate stations and VARA FM/HF to move the actual payload.
The control layer answers questions such as:
- Is the destination reachable?
- Which station should receive the message next?
- Is a relay required?
- Which frequency should be used?
- Is the receiving station busy?
- Was the message forwarded?
- Did it finally reach its destination?
The operator does not need to manually orchestrate every individual step.
Send text and attachments directly between two radio stations.
No Internet connection and no central mailbox are required.
The header shows genuine VARA byte progress for both outgoing and incoming messages. Optional payload settings provide either native VARA FILES compression or Guardian's single-pass BZIP2 compression; the two modes are mutually exclusive and BZIP2 keeps the standard ZIP whenever compression would make it larger.
After the final acknowledgement, the destination can optionally append both callsigns as a 40 WPM Morse ID.
A station that cannot reach the destination directly can hand the message to another Guardian station.
The relay stores the message locally and forwards it when the next hop becomes available.
OK7AAA ββββΊ OK7BBB ββββΊ OK7CCC ββββΊ OK7DDD
Source Relay Relay Destination
Delivery state follows the message across the network.
Guardian can determine the next hop using several sources of information:
- manually configured routes;
- a shared network topology;
- stations heard directly on the radio;
- assisted route discovery;
- experimental live network topology.
Operators can therefore build anything from a simple two-station link to a larger regional radio network.
Guardian includes structured message templates for:
- ICS-213
- ICS-214
- IARU emergency messages
- SITREP
Messages remain ordinary interoperable text inside the Guardian transport rather than being locked into a proprietary document format.
Guardian includes an operational station map.
The map can show:
- your own station;
- recently heard stations;
- Maidenhead locators;
- radio links and message activity;
- distance and bearing;
- 50 / 100 / 200 km range rings;
- route availability;
- current network alerts.
A station can be selected directly on the map to start composing a message.
The map can also be prepared for offline operation and exported as PNG. Guardian 1.1.1 additionally recognises a manually supplied XYZ tile tree at maps\tiles\<zoom>\<x>\<y>.png beside the installed application. It remains unused until the operator selects Use manually installed map in the map window and confirms the choice; without both the files and that consent, the normal ΔΓZK background behaves exactly as before.
Guardian stations can broadcast short network-wide alerts independently from ordinary mail.
Alerts can be received, displayed and relayed by other Guardian stations and can optionally be transmitted across configured channels.
Guardian supports both VARA FM and VARA HF.
The same mailbox and routing model can therefore be used for local VHF/UHF networks and longer-distance HF communication.
| FM | HF | |
|---|---|---|
| Control modem | AFSK 1200 | MFSK-16 |
| Payload | VARA FM | VARA HF |
| Typical use | Local / regional | Regional / long distance |
| Routing | β | β |
| Relay | β | β |
| Attachments | β | β |
Guardian automatically selects the appropriate ARDOS control modem for the operating mode.
Guardian can operate everything on one frequency or separate the network into a calling channel and a working channel.
For example:
145.500 MHz
ARDOS calling / coordination
β
β stations negotiate
βΌ
145.350 MHz
VARA payload transfer
β
βΌ
145.500 MHz
return to calling channel
With CAT-controlled radios, Guardian can perform the required QSY automatically.
Radios without CAT can still be used through an operator-confirmed tuning workflow.
Guardian 1.1 provides task-oriented workspaces instead of exposing protocol internals to the operator.
Station status, radio and VARA connectivity, control-channel state and current operation.
A local store-and-forward mailbox with:
- Inbox
- Outbox
- Sent
- Transit
Messages can contain text, structured traffic and file attachments.
One operational view for:
- Routes
- Heard stations
- Network builder
- Route discovery
- Live topology
Routes clearly show where the information came from instead of mixing permanent configuration and temporary RF observations.
Operational and diagnostic information for troubleshooting radio, control-channel and payload activity.
A Guardian network can be planned centrally without manually creating a different routing table for every computer.
Define the links once:
OK7BBB
/ \
OK7AAA OK7DDD
\ /
OK7CCC
The same topology can be distributed to all stations.
Each Guardian installation uses its own callsign to calculate the appropriate local next-hop routes automatically.
Manual routes remain available as overrides.
Guardian can also search for a destination that is not already present in the configured topology.
Stations cooperate using bounded multi-hop route discovery.
SOURCE
β
ββββΊ Relay A
β β
β ββββΊ Relay B
β β
β ββββΊ DESTINATION
β
βββββββββ discovered route ββββββββ
Discovery is deliberately bounded to avoid uncontrolled radio traffic.
The resulting dynamic route is temporary and remains distinct from permanent network configuration.
In Assisted mode the source operator can review a discovered path before the payload is transmitted.
Guardian supports a wide range of radios through Hamlib / rigctld.
Depending on the radio and interface, Guardian can control:
- frequency;
- mode;
- PTT;
- signal level;
- automatic QSY.
For simpler radios and interfaces, serial RTS/DTR PTT is also supported.
This makes Guardian usable with both modern CAT-controlled transceivers and much simpler FM radios.
Different radios and interfaces can be stored as named profiles.
For example:
IC-705 Portable
IC-705 Base
AIOC Handheld
FTDX10 HF
Changing station hardware therefore does not require re-entering the complete CAT and PTT configuration.
Guardian includes its own VARA monitoring window.
It provides:
- live RX spectrum;
- waterfall;
- RX/TX frequency;
- PTT state;
- VARA connection state;
- FM/HF passband scaling.
The monitor observes the selected radio input and does not independently key the transmitter.
The radio messaging system itself does not require Internet access.
Messages, attachments, routes, heard stations and delivery state are stored locally.
Network access is used only for optional functions such as:
- downloading updates;
- installing verified Hamlib packages;
- downloading VARA after operator confirmation;
- obtaining map tiles before offline use;
- optional Windows position detection.
Once the required software and map data are present, the core messaging system operates over radio.
Guardian 1.1.1 preserves the 1.1.0 radio, messaging and map behaviour and adds only an explicitly confirmed, manually installed XYZ map alternative. The existing ΔΓZK background remains the default.
| Capability | Status |
|---|---|
| Direct VARA FM messaging | β Confirmed on air |
| Direct VARA HF messaging | β Confirmed on air |
| AFSK FM control channel | β Confirmed on air |
| MFSK HF control channel | β Confirmed on air |
| Attachments | β Confirmed on air |
| Network alerts | β Confirmed on air |
| Automatic CAT QSY | β Confirmed on hardware |
| Calling / working channel split | β Confirmed on air |
| Production channel scanner | β Confirmed on hardware |
| No-CAT / serial PTT operation | β Confirmed on hardware |
| Shared network topology | β Implemented |
| Assisted multi-hop discovery | π§ͺ Implemented and software tested |
| Live topology advertisements | π§ͺ Experimental |
See STATUS.md for the complete engineering and field-verification record.
Download the latest installer:
The Windows package already contains Python and the required Python libraries.
A separate Python installation is not required.
Windows warning
Current builds are not Authenticode signed. Windows may therefore display Unknown publisher or a Microsoft Defender SmartScreen warning.
Download Guardian only from this repository's Releases page and verify the supplied SHA-256 manifest when required.
After installing Guardian:
- Open Operation β Station readiness
- Enter your callsign
- Configure the radio
- Select RX and TX audio devices
- Locate or install Hamlib
- Locate or install VARA FM / VARA HF
- Connect the radio
- Connect VARA
- Start the ARDOS control channel
- Compose a message
Guardian does not automatically begin transmitting when the application starts.
RF activity is explicitly initiated by the operator.
Guardian uses VARA as the payload modem but does not redistribute it.
VARA remains separately licensed third-party software.
The Station Readiness assistant can, after operator confirmation:
- download the reviewed VARA archive from the official distribution server;
- verify its expected size and SHA-256;
- ask again before starting the vendor installer.
Guardian never silently accepts or installs third-party software.
Guardian communicates with CAT radios through rigctld.
Hamlib can be installed automatically from:
Operation β Station readiness
Guardian downloads the reviewed portable package, verifies it and installs it into the Guardian application-data directory.
Administrator rights are not normally required.
Python 3.11 or later is required when running Guardian from source.
git clone https://github.com/bubakbubak500/ARDOS-Guardian.git
cd ARDOS-Guardian
.\setup.ps1
.\run.ps1To create the standalone Windows build:
.\build.ps1Output:
dist\Guardian\Guardian.exe
The README provides the high-level overview of Guardian.
Detailed design and implementation information is intentionally kept elsewhere:
- PRODUCT.md β product scope and operational boundaries
- STATUS.md β development history, field tests and current verification
- docs/MULTIHOP_DISCOVERY.md β multi-hop discovery
- SECURITY.md β security policy
- GitHub Releases β installers and release notes
Guardian automates parts of a radio communication workflow.
It does not determine whether a transmission is legal.
The operator remains responsible for:
- possessing the required amateur-radio licence;
- permitted frequencies;
- bandwidth and emission mode;
- transmit power;
- identification requirements;
- third-party traffic restrictions;
- local amateur-radio regulations.
Guardian is experimental software and must not be the sole communication system for situations involving immediate risk to life.
Guardian is developed around real radio operation.
Field reports are particularly useful.
When reporting a radio-related problem, please include where possible:
- Guardian version;
- radio model;
- interface;
- CAT / PTT configuration;
- VARA FM or VARA HF;
- frequency and mode;
- relevant Guardian diagnostic export.
Bug reports and development discussions are welcome through GitHub Issues.

