Approachable group messaging
Phone-linked messages, positions, telemetry, channels, managed flooding, and a broad supported-device ecosystem.
The practical, protocol-honest guide to Meshtastic, MeshCore, Reticulum, OpenMANET, and controlled cross-mesh operation for families, preparedness groups, field teams, and resilient communities.
Enter your email. The 150-page PDF appears here immediately.
Operational emails only. Unsubscribe whenever you want. We do not sell your information.
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.
Phone-linked messages, positions, telemetry, channels, managed flooding, and a broad supported-device ecosystem.
Companions, repeaters, advertised contacts, explicit paths, channels, and room servers for delayed continuity.
Destinations, announces, links, LXMF, RNode LoRa, local IP, wired paths, and mixed-media backbones.
Each technical page gives you the principle, what to configure, what to avoid, a field rule, and a place to record measured evidence.
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. |
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.
Map nodes, positions, routes, status, messages, zones, contacts, and tasks while keeping source and timestamp visible.
Portable mapping, Mesh2.0, Reticulum, repeater tools, logbook, and prepared local PWA workflows.
Simple prepared check-in and HELP packets with recognizable Unit IDs and available position.
Analyze saved mesh records and snapshots with human review and evidence-bounded prompts.
Watch legally receivable audio for selected terms, then verify the original evidence before acting.
Keep video on suitable LAN links and send only concise, timestamped event metadata over LoRa.
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.
Save it locally, choose the mesh or combination of meshes for your task, and test each link plus any XTOC™ cross-mesh relay end to end.
FOLLOW MKME ON GOOGLE
Add MKME STORE as a preferred source for our latest guides, field tutorials, and product updates.