Free 150-page practical reference

Build a mesh
that matters.

The practical, protocol-honest guide to Meshtastic, MeshCore, Reticulum, OpenMANET, and controlled cross-mesh operation for families, preparedness groups, field teams, and resilient communities.

Current supported hardwareAntennas and NanoVNAChannels and encryptionEmergency playbooksOpenMANET backboneXTOC™ cross-mesh relay

Get the complete mesh guide.

Enter your email. The 150-page PDF appears here immediately.

Ultimate Mesh Preparedness Guide

Operational emails only. Unsubscribe whenever you want. We do not sell your information.

The Ultimate Mesh Radio Preparedness Guide cover

150 practical pages / PDF
Pick the right stackUnderstand what Meshtastic, MeshCore, and Reticulum actually do differently.
Engineer real linksPlacement, antennas, Fresnel clearance, feedline, and measured coverage.
Keep it poweredHonest battery, solar, cold-weather, enclosure, and restart planning.
Use it under pressureClear messages, check-ins, nets, logs, drills, and fallback decisions.
Three ecosystems. Three different models.

Stop treating every LoRa mesh like the same network.

The guide explains where each protocol fits, where it does not, and why they cannot relay one another without separate radios, deliberate gateways, or a human handoff.

MESHTASTIC

Approachable group messaging

Phone-linked messages, positions, telemetry, channels, managed flooding, and a broad supported-device ecosystem.

→
MESHCORE

Deliberate LoRa infrastructure

Companions, repeaters, advertised contacts, explicit paths, channels, and room servers for delayed continuity.

→
RETICULUM

Identity across many interfaces

Destinations, announces, links, LXMF, RNode LoRa, local IP, wired paths, and mixed-media backbones.

No product is required to use the guide. The first 94 pages stand on protocol, radio, power, security, and field practice. XTOC, XCOM, XNODE, XCORE, XINTEL, and XCAM appear later as an optional coordination layer.
PLANPeople, places, decisions, PACE methods, message classes, acknowledgements.
BUILDCurrent hardware choices, legal bands, antennas, feedline, batteries, solar, and enclosures.
DEPLOYMeshtastic, MeshCore, and Reticulum configuration with compatibility warnings.
OPERATEWildfire, flood, winter, earthquake, blackout, shelter, convoy, backcountry, and neighborhood playbooks.
RECOVERTroubleshooting, key rotation, identity backup, second-operator handoff, and after-action improvement.
Every page earns its place

Reference, procedure, warning, and field worksheet.

Each technical page gives you the principle, what to configure, what to avoid, a field rule, and a place to record measured evidence.

  • Current official hardware shortlists with revision and band checks
  • Message formats that fit constrained radio links
  • Coverage acceptance tests instead of distance promises
  • Version-sensitive Meshtastic roles and MeshCore path-hash compatibility
  • Reticulum identities, destinations, links, LXMF, RNode, and interface boundaries
  • Legal, privacy, source-confidence, and failure-recovery guidance
Choose from current official support

Hardware by role, not hype.

The manual points back to current official flashers and documentation because board revisions and firmware support change quickly.

Role What matters Current examples covered
Personal / tracker Low power, simple controls, safe charging, rugged carry. RAK4631/WisBlock, T1000-E, Wio Tracker L1, T-Echo, Heltec T114/T096 and current equivalents.
Standalone field terminal Screen or keyboard, local maps, phone independence, tested UI. T-Deck, T-Deck Pro, T-LoRa Pager and supported standalone MeshCore/RNode builds.
Base / gateway Stable USB or LAN, logging, external antenna, independent power. Supported ESP32/nRF52 LoRa boards plus XCOM/XTOC or Reticulum on a local computer.
Relay / room / propagation node Height, continuous power, legal duty cycle, remote recovery, maintenance. Role-specific MeshCore images, carefully selected Meshtastic infrastructure roles, or prepared Reticulum transport/propagation nodes.
Optional X Suite integration

Use software as the backbone without making it the price of admission.

Independent mesh users get a complete field manual. X Suite owners get a clear way to connect radio traffic to maps, tasks, logs, monitoring, local AI, simple family check-ins, and local video evidence.

XTOC

One operational picture

Map nodes, positions, routes, status, messages, zones, contacts, and tasks while keeping source and timestamp visible.

XCOM

The moving field edge

Portable mapping, Mesh2.0, Reticulum, repeater tools, logbook, and prepared local PWA workflows.

XNODE

One-button family actions

Simple prepared check-in and HELP packets with recognizable Unit IDs and available position.

XCORE

Local evidence assistant

Analyze saved mesh records and snapshots with human review and evidence-bounded prompts.

XINTEL

Radio monitoring support

Watch legally receivable audio for selected terms, then verify the original evidence before acting.

XCAM

High-bandwidth local context

Keep video on suitable LAN links and send only concise, timestamped event metadata over LoRa.

Build the smallest network that answers a real question

Measure the route. Train the people. Keep the fallback.

Download the guide, choose one ecosystem, configure two devices, walk one meaningful route, and record where the link actually works.

Follow local radio law and official emergency guidance. Do not interfere with emergency traffic, expose sensitive location data, or treat packet delivery as proof of safety. Mesh is a useful communications layer, not a rescue guarantee.



FOLLOW MKME ON GOOGLE

Keep MKME in your search results

Add MKME STORE as a preferred source for our latest guides, field tutorials, and product updates.