XCOM™ Offline Radio Communication Suite
XCOM™ Offline Radio Communication Suite

XCOM™ Offline Radio Communication Suite

XCOM™ Offline Radio Communication Suite (PWA)

XCOM™ is an offline-first radio communication suite and PWA for
ham radio, shortwave, and modern mesh radio networks —
with a heavy focus on Meshtastic, MeshCore, and MeshChat (Reticulum / RNode).
It’s built as the field companion to XTOC™ so you can
form packets, move updates, and keep a tactical map synced using almost any method:
copy/paste, QR, SMS, email, Winlink, Meshtastic, MeshCore, Reticulum (MeshChat), or local MANET links.
Download the guide set (PDF): Disaster Operations Guide | MILSIM Operations Guide
Use the disaster guide for civil response workflows and the MILSIM guide for multi-day tactical / airsoft events with XCOM, XINTEL, XCORE, ATAK, APRS, JS8Call, FLDIGI, VarAC, mesh, MANET, SATCOM, drones, QR handoff, thermal printing, and TOC workflows. Both guides now include radios quick-listen playbooks for disaster teams and MILSIM field operators, plus detailed Digi Modes, APRS, JS8Call, FLDIGI, and VarAC use cases.

Hot topics it supports:

  • Multilingual UI: English, Traditional Chinese (繁體中文), Ukrainian (Українська), Persian (فارسی).
  • Meshtastic PWA tools: connect, import channel labels, message on channels, and DM nodes by clicking (Web Bluetooth where supported; on iPhone/iPad this is best effort only and cannot be guaranteed).
  • MeshCore support: import/visualize MeshCore traffic and plot packets on the map.
  • NEW: MeshChat (Reticulum / RNode): connect to the XTOC reticulum-bridge over a trusted LAN/localhost, scan a provisioning QR, announce, see peers/interfaces, and move XTOC packet text over RNS (including an RNode over Bluetooth/serial).
  • NEW: Radios workbench: bring the XTOC three-bay quick-listen SDR deck into XCOM; launch radio-helper/windows/Start-XCOM-Radio.bat and use scanner, HF, or dual-band faces with local browser audio.
  • OpenMANET node mapping: plot OpenMANET node locations on the tactical map and optionally assign nodes to roster members.
  • Packet workflows to/from XTOC™: build, chunk, export, import, and overlay field intel.
  • NEW: Secure Session (Trust Link): link to the TOC with a one-time challenge/response, then auto-sign every packet so XTOC can verify it and reject replays/forgeries — regardless of transport.
  • Offline maps: cache AO tiles for use with no signal.
  • SATCOM: download/import TLE sets, store a local satellite library for offline use, and visualize HAM satellite passes/footprints.
  • VOACAP HF prediction: fast point-to-point propagation planning.
  • Offline callsign database: lookup + path plotting without internet.
  • QSO logger: field logging with ADIF/CSV export.
NEW: ViperGram radio-audio transport: render XTOC packet text as a robust OFDM WAV burst, play it into a radio, import recordings back into XCOM/XTOC, use on-demand live mic listen in XCOM/XTOC, or let XINTEL auto-decode the burst off-air continuously.

What XCOM™ is

XCOM™ is an offline-capable Progressive Web App (PWA) designed as the
field companion to XTOC™. It lets operators
build, move, receive, and visualize operational packets while also providing
Meshtastic + MeshCore mapping, radio planning, and reference tools —
even with no signal.

Use it to (examples):

  • Create XTOC-compatible packets (markers, zones, events, updates, notes) and move them via copy/paste, QR, SMS, email, Winlink, Meshtastic, MeshCore, Reticulum (MeshChat), or MANET.
  • Create EVENT packets for training/incidents/emergencies (status, schedule, label, location) and plot them on the tactical map.
  • Send squad/group CHECKIN/LOC updates: include multiple team members in one check-in (Units picker shows U### + label).
  • Tag multiple units on most packets: use Source Unit(s) multi-select for SITREP/TASK/CONTACT/RESOURCE/ASSET/ZONE/EVENT (packets send Unit IDs only; names are looked up locally).
  • If you import a roster with Squads from XTOC, unit pickers are grouped by squad for faster selection.
  • Operate as a field console: send updates toward the TOC and import TOC packets back into XCOM.
  • Quick-listen a local voice channel in Radios, confirm whether the net is active, then escalate it to XINTEL or a dedicated receiver if it becomes a sustained watch.
  • Map and review Meshtastic nodes and messages; import channel labels and DM nodes by clicking; visualize mesh traffic for situational awareness.
  • Plot OpenMANET nodes on the tactical map and optionally assign nodes to roster members.
  • Import and visualize MeshCore packets (traffic, nodes, events) and overlay them on the tactical map.
  • Plan satellite passes to identify viable radio communication windows (SATCOM: local TLE library + pass planner + HAM footprints).
  • Find repeaters by location with tones, offsets, modes, and notes.
  • Browse shortwave broadcasts by time (“what’s on now”) or frequency.
  • Maintain references for packet radio nodes / BBS stations.
  • Download offline map tiles for your Area of Operations.

Built for bad connectivity

XCOM™ is local-first. Your data stays on your device and the app continues to function
when connectivity is limited, unreliable, or intentionally avoided.
That’s why it pairs so well with Meshtastic and MeshCore — networks designed for real-world conditions.
  • No accounts. No login, no cloud dependency.
  • Offline maps. Cache raster tiles for your AO and use them later with no signal.
  • Offline search. Cities, QTHs, callsigns, and references from local datasets.
  • Store-and-forward mindset. Build packets now, move them later (perfect for mesh relays).

XTOC™ companion workflow (field ↔ TOC)

XCOM™ runs on devices away from the TOC.
XTOC™ maintains the operational picture. XCOM™ feeds it — including updates moved over Meshtastic, MeshCore, or any low-connectivity path.
  • Field builds a packet in XCOM → transfers it (Meshtastic / MeshCore / QR / copy / Winlink / email) → TOC imports into XTOC.
  • TOC publishes updates/markers/zones → transfers outward → field imports into XCOM overlays.
  • Packets are chunked to survive tight character limits and “dumb pipes.”
  • New radio-audio path: field can export a ViperGram burst, send it over plain radio audio, and have the receiver use on-demand live mic listen in XCOM/XTOC or unattended XINTEL auto-decode into XTOC.
XCOM™ does not replace XTOC™. It extends it to the edge with mesh-friendly workflows.

Related XTOC walkthrough

See the TOC-side aircraft tracking and surveillance workflow XCOM can feed from the field.

NEW: ViperGram radio-audio packet transport

ViperGram turns XTOC packet text into a robust OFDM audio burst you can play into almost any radio/audio path. That gives you a packet transport with no TNC, no data port, and no special cabling requirement. Record the burst and XCOM/XTOC can import it back into packet text, or use Audio Import / Live Listen for on-demand microphone receive. Run XINTEL on the receive side when you want continuous unattended decode into XTOC.
  • Waveform: mono 16-bit PCM WAV at 8000 Hz.
  • Timing: 180 ms lead-in, 240 ms inter-burst gap, 180 ms tail, with a 10 ms cosine ramp on each burst edge.
  • OFDM symbol: 1280 useful samples (160 ms) plus 160 sample guard/cyclic prefix (20 ms) = 180 ms on-air.
  • Burst format: 7 symbols total = noise, sync, preamble, then 4 payload symbols. Total burst duration is 1260 ms.
  • Carrier plan: 256 active carriers, bins 112..367, spacing 6.25 Hz, occupied audio about 700 Hz..2293.75 Hz.
  • Modulation: differential QPSK.
  • Bit handling: 32-column bit interleave, xorshift32 payload whitening, CRC-32 validation, and multi-burst text reassembly.
  • Compatibility: solves the same operational problem as Rattlegram-style radio audio transfer, but it is not wire-compatible with Rattlegram.
byte 0   0x56                magic 'V'
byte 1   0x47                magic 'G'
byte 2   0x01                format version
byte 3   protection code     1=Strong, 2=Medium, 3=Normal
byte 4   burst index         1-based
byte 5   burst total         total bursts in message
byte 6   payload length      clear payload bytes in this burst
byte 7   burst repeats       repeats used by this protection profile
byte 8   CRC32 byte 0        payload CRC, least-significant byte first
byte 9   CRC32 byte 1
byte 10  CRC32 byte 2
byte 11  CRC32 byte 3
byte 12+ whitened payload bytes
  • Strong: 85 clear payload bytes, duplicated payload bitstream, 2 repeats.
  • Medium: 128 clear payload bytes, 2 repeats.
  • Normal: 170 clear payload bytes, 1 transmit.
  • Big operational win: you can export the burst in XCOM, transmit it over plain radio audio, then receive it either with on-demand live mic listen in XCOM/XTOC or with XINTEL auto-import on the receive side.

What’s inside

Purpose-built modules for mesh, field comms, and radio operations:
  • Meshtastic (PWA): connect to Meshtastic devices (Web Bluetooth where supported; iPhone/iPad best effort only),
    view nodes, map positions, and send/receive messages.
  • MeshCore support: import and visualize MeshCore packet logs/traffic and plot nodes/events on the map.
  • Mesh Packet Visualization: overlay imported mesh traffic on the tactical map for situational awareness and after-action review.
  • Radios (Workbench): the same three-bay XTOC quick-listen deck for browser-based receive via radio-helper and an RTL-SDR.
  • XTOC Comm: create/import structured packets (CLEAR or SECURE) including CONTROL (T=16) for Sentinel output control, optionally establish a Secure Session (Trust Link) to auto-sign packets, chunk for tight limits, and move via copy/QR/ViperGram audio/Meshtastic/MeshCore/Reticulum (MeshChat)/MANET.
  • XTOC Data Vault: local packet archive — browse, search, decode, and push geo packets to the map overlay.
  • Backup & Update: export/restore backups, repair/update the PWA shell, and merge XTOC exports into XCOM (XTOC → XCOM Import) without wiping existing data.
  • Map (Tactical Field View): XTOC-style map with offline tile caching and overlays (XTOC markers/zones + mesh layers).
  • Satellite Pass Planner: identify viable radio communication windows for satellite comms planning.
  • Repeaters: searchable repeater map with detailed station info.
  • Packet Stations: packet node/BBS reference + your own local entries.
  • Shortwave Broadcasts: HF schedules by time (“what’s on now”) or by frequency.
  • Predict (VOACAP + tools): offline callsign lookup + path plotting + HF prediction.
  • QSO Logbook: offline-first logging with ADIF/CSV export.
  • ASCII Tools: clean copy/paste banners for packets and BBS posts.
  • Ham Clock: time, band, and operating reference.

HF planning, monitoring & signal hunting

A major strength of XCOM™ is that it does not stop at a repeater list or a packet form. It gives you the planning layer that helps you decide what to monitor, what band to try, and where to point before you waste time in the field.
  • Predict: search a callsign, city, grid square, or map-picked target; draw the path; measure distance; adjust UTC, solar flux, mode, and power; then see current and future band windows.
  • Shortwave Broadcasts: browse an offline worldwide HF schedule snapshot by time or frequency so you can answer “what is on right now?” even when disconnected.
  • Repeaters + Packet Stations: find local infrastructure fast, inspect frequencies and notes, and keep your own packet node list for the places you actually operate.
  • Azimuthal Map + Ham Clock: get true beam headings, short-path/long-path awareness, greyline context, and DE/DX distance in seconds.
  • SATCOM: keep a local TLE library, visualize HAM footprints, and plan the next usable satellite window without depending on a live website.

Live overlays, interop & field awareness

XCOM™ is built for real field information flow. It can ingest outside feeds, plot them, and keep them organized next to your XTOC workflow instead of leaving them spread across separate apps.
  • Map overlays: imported XTOC markers, zones, events, and packet-derived geometry can be rendered locally on the tactical map with offline raster caching.
  • Mesh/OpenMANET picture: plot Meshtastic, MeshCore, and OpenMANET nodes, review traffic, and optionally assign nodes to roster members after an XTOC import.
  • Aircraft (ADS-B): connect a local dump1090/readsb feed, test it, and render nearby aircraft on the map for surveillance support or general field awareness.
  • ATAK (CoT): connect to atak-helper, monitor live Cursor-on-Target traffic, and customize how CoT points render on the map.
  • APRS bridge: use the Radio module plus aprs-bridge when you want a ham-friendly transport path for CLEAR packet lines.
  • Radios workbench: check a local voice frequency in seconds, confirm whether the channel is active, and hand it off to XINTEL or a dedicated receiver if it becomes important.

NEW: Radios quick-listen workbench

XCOM™ now includes the same three-bay radios workbench used in XTOC. Start radio-helper/windows/Start-XCOM-Radio.bat, open Radios, choose a scanner / HF / dual-band face, and get immediate browser audio from a local RTL-SDR.
  • Disaster use: shelter or branch staff can check weather, volunteer, utility, or transport traffic before the TOC commits a full-time monitoring position.
  • MILSIM use: recon or FOB leads can confirm admin, safety, medic, drone, or liaison channels before re-tasking a radio operator.
  • Escalation rule: use Radios for fast human listen. Move the channel to XINTEL or a dedicated receiver when you need long-duration watch, clips, or hit rules.

Field ops, automation & recovery

Good field software is not only about transport. It also needs to help you stay organized, recover quickly, and avoid losing the work you did offline.
  • XTOC Comm + XTOC Data: generate/import structured packets, chunk for tight channels, review stored history, and push geo packets back onto the map overlay.
  • Triggers: schedule communications windows, alarms, and time-based reminders for nets, check-ins, logistics, and recurring field tasks.
  • Logbook + ASCII tools: log contacts quickly, export ADIF/CSV later, and generate clean text banners for packet posts or BBS traffic.
  • Backup & Update: export/restore local data, merge XTOC backups into XCOM without wiping existing work, repair a stuck app shell, and request persistent storage.
  • XCORE™ integration (optional): hand local snapshots and packet context to a trusted local XCORE node when you want grounded review, anomaly checks, or packet drafting support.

Meshtastic mapping, messaging & node visualization

Meshtastic is one of the most in-demand topics in off-grid comms.
XCOM™ is built to be Meshtastic-friendly with workflows that match real field usage:
local-first, low bandwidth, and store-and-forward.
  • Connect to a Meshtastic device (Web Bluetooth where supported) and view nodes on a map. On iPhone/iPad, treat this as best effort only.
  • Import channel labels and quick-select a channel by clicking.
  • DM by clicking: click a heard node to quickly set a direct destination.
  • Send/receive messages and keep a local traffic log.
  • Use XTOC Comm to chunk and move XTOC packets over the mesh (Meshtastic transport profile).
Think: Meshtastic + XTOC = mesh-to-TOC operational picture.

MeshCore support (import, map overlays, packet plotting)

XCOM™ also supports MeshCore workflows by allowing you to
import MeshCore traffic/logs and visualize packets, nodes, and events on the tactical map.
This is ideal for operational review, coverage notes, and building a real-world “mesh picture.”
  • Connect to MeshCore (Web Bluetooth where supported) or import MeshCore traffic/logs and plot it on the map.
  • Visualize node activity for situational awareness and after-action review.
  • Direct addressing: MeshCore DMs use a pubkey prefix and tight limits (~160 bytes) — use the MeshCore transport profile in XTOC Comm to chunk safely.
  • Convert relevant observations into XTOC-compatible packets.

NEW: MeshChat (Reticulum / RNode) packet transport

Reticulum (RNS) is a powerful off-grid networking stack. XCOM™ includes a MeshChat module that connects to the XTOC reticulum-bridge over a trusted LAN/localhost, enabling XTOC packets to move over Reticulum networks (including an RNode over Bluetooth/serial).
  • Bridge host: run reticulum-bridge on the device attached to the RNode (usually the XTOC laptop), then share a provisioning QR.
  • Where to find it: in your download ZIP, look for reticulum-bridge/ next to index.html (see reticulum-bridge/README.md).
  • Field device: scan the QR to auto-configure Bridge URL + destination hash, then connect and send.
  • Broadcast + Direct: send packet lines to broadcast, or DM a specific hash; see peers, interfaces, connected clients, and traffic.
  • Chunking: use the Reticulum transport profile in XTOC Comm (conservative ~320 chars/line) so packets survive narrow links.
Security note: the bridge is designed for trusted LANs only (permissive CORS, no authentication).

SATCOM (HAM satellites)

Local-first satellite tracking for field ops: download/import TLE sets, keep a local satellite library for offline use, and visualize satellites on the tactical map with ground tracks and HAM footprints.
  • Download + save: pull TLE groups from Celestrak (or import/paste your own).
  • Local library: TLEs are stored on-device (IndexedDB) so SATCOM keeps working offline.
  • Map overlay: render satellites as subpoints + predicted tracks; click for details (look angles / reachability).
  • HAM focus: show approximate footprints for HAM sats and a next-pass planner for FM voice satellites.
Tip: filter the SATCOM overlay to a small set of satellites for best map performance.

HF propagation & VOACAP prediction

XCOM™ includes a VOACAP-based HF prediction engine optimized for
field decision-making — fast point-to-point planning without needing a laptop stack of tools.
  • Point-to-point HF path predictions using callsigns or coordinates.
  • Band viability by time of day (local & UTC).
  • Quick answers to “What band should I try right now?”
  • Designed for intermittent or no connectivity.
Use data, not guesswork, when conditions are marginal.

Prediction workflow that is actually useful in the field

The Predict module is more than a callsign lookup box. It is a fast planning workflow for answering the question operators ask under pressure: which path and which band should I try next?
  • Start from real inputs: use a callsign, city, grid square, or a point you pick on the map.
  • See the path: XCOM™ draws the great-circle route and distance so you understand the kind of HF problem you are solving.
  • Tune the model: adjust UTC, solar flux, mode, power, and forecast hours to match the real conditions you care about.
  • Look ahead: compare current band guidance with the next several hours so you can decide whether to transmit now, wait, or switch tactics.
  • Stay offline: the core lookup and planning workflow is designed to stay useful even when internet access is weak or absent.

Shortwave schedule browser for “what’s on now”

Shortwave Broadcasts gives you an offline worldwide HF schedule snapshot you can browse by time or by frequency. It is useful for monitoring, signal hunting, and basic situational awareness when you want to know what should be on the air before you start spinning the dial.
  • By time: see what should be active right now using either Local time or UTC.
  • By frequency: search a frequency with tolerance so you can identify likely stations fast.
  • Filter noise: search by station, ITU, language, target, or remarks, and optionally hide utility/time stations when you only want broadcasters.
  • Built for monitoring: useful for travel, field kits, HF monitoring, and pre-mission listening plans when internet access is gone.

XCOM™ – Offline Radio Communication Suite

XCOM™ – Offline Radio Communication Suite

Offline callsign database (USA & Canada)

Built-in offline callsign database for fast identification and planning when there’s no internet.
  • Instant local lookup with stored QTH/location data.
  • One-tap path plotting and VOACAP prediction integration.
  • Useful for HF planning, packet routing, and traffic analysis.

Offline databases are snapshots — verify when precision matters.

QSO logger (offline-first)

A fast, offline-first QSO logbook built for real operating — ideal for field ops, POTA/SOTA, and emergency use.
  • Log callsign, band, mode, time, reports, and notes.
  • Integrated offline callsign lookup for faster entry.
  • Works fully offline once installed/loaded.
  • Export logs in ADIF or CSV.
Capture the contact now — export later.

Quick start (offline)

1) Install as an app

  • iOS: open https://mkme.org/xcom/ in Safari → activate while online → try Mesh → Connect while still in Safari → Share → Add to Home Screen
  • Android: Chrome → Install app
  • Desktop: Chrome/Edge → Install
iPhone/iPad note: Apple has made Web Bluetooth difficult for installed PWAs. XCOM™ will try to work in Safari/Home Screen mode, but Meshtastic/MeshCore BLE support on iOS is best effort only and cannot be guaranteed. If the Home Screen install fails to connect, reopen mkme.org/xcom in Safari and try Mesh there while online.

2) Cache offline maps

  • Open Map → Offline Raster
  • Pan/zoom AO
  • Download tiles while online

3) Run the field-to-TOC loop

  • Build packet → transfer over Meshtastic / MeshCore / MeshChat (Reticulum) / MANET / QR / copy → import into XTOC.
  • Import TOC updates → overlay on map → share onward through the mesh, Reticulum, or LAN.
  • Reticulum tip: run reticulum-bridge on the TOC device connected to the RNode, then scan the provisioning QR in XCOM MeshChat.

Compliance notes

XCOM™ can generate SECURE (encrypted) payloads. You are responsible for legal and regulatory compliance.
Amateur radio note: Do not transmit encrypted/obscured content on ham bands. Use CLEAR mode where appropriate.

Privacy & data

  • Local-first: data stored on your device.
  • No accounts: no login, no analytics.
  • Offline-friendly: most features work without internet once installed.

FAQ

Does XCOM™ work with Meshtastic?
Yes. XCOM™ supports Meshtastic workflows including mapping nodes, messaging, and mesh-friendly packet transfer paths.

Does XCOM™ support MeshCore?
Yes. XCOM™ supports MeshCore workflows by allowing you to import and visualize MeshCore traffic/logs and plot packets/nodes on the map.

Does XCOM™ support Reticulum / MeshChat?
Yes. XCOM™ includes a MeshChat (Reticulum) module that connects to the XTOC reticulum-bridge over a trusted LAN/localhost so you can move XTOC packet text over Reticulum networks (including an RNode over Bluetooth/serial).

Is XCOM™ just a repeater map?
No — it’s a full offline radio suite with Meshtastic/MeshCore tools, packet formation, tactical mapping, HF prediction, and logging.

Does XCOM™ require a server?
No. The core app is a static PWA and runs locally in your browser once installed/loaded.

Do I need a license key?
On first run (when hosted), XCOM™ may prompt for a license key. Activate once while online, then keep using it offline on that device.

Will it work offline?
Yes. Install it as a PWA, and it will keep working offline after it’s loaded. Offline map tiles must be cached while online.

Which browsers are recommended?
Modern Chrome/Edge/Safari. For Meshtastic/MeshCore BLE, Chrome/Edge on desktop or Android remain the recommended path. On iPhone/iPad installed from mkme.org/xcom, Apple’s current PWA/Web Bluetooth restrictions mean support is best effort only and cannot be guaranteed.

What is the best way to try mesh on iPhone/iPad?
Open mkme.org/xcom in Safari, activate while online, go to Mesh, tap Connect, and complete any prompt/helper flow there first. Then add it to the Home Screen and test again. If it still fails, use Safari directly or move mesh operations to Chrome/Edge on desktop or Android.

Are frequencies guaranteed accurate?
Treat any directory as a reference. Always listen/verify on-air and follow your local regulations.