← Plan comms · Digital bundle

Workflow · Offline

Meshtastic Field Workflow

License-free LoRa mesh text for property, farm, and emcomm contingency — when voice repeaters and cell are unavailable.

New to mesh? First week guide Property sizing guide

1 — Preset & hardware

Meshtastic presetsModem settings by region Mesh decoderExtract node names from share URLs Digital modes bundleDMR + mesh references

2 — Placement & power

Mesh range is terrain-limited. Elevate antennas, minimize obstructions, and plan solar/USB power for fixed nodes.

Horizon / LOSLine-of-sight estimate Field power hubBattery and solar sizing

3 — Channel keys & coordination

  • Shared channel key: All nodes in a deployment must use the same channel name and PSK. Exchange keys out-of-band (in person or phone) — do not publish incident keys on public forums.
  • Encryption policy: Meshtastic default encryption protects casual eavesdropping but is not a substitute for served-agency secure systems. Treat mesh as situational awareness text, not classified traffic.
  • Interoperability: Mesh does not bridge to voice nets, LTE, or ICS voice without a human relay. Document who reads mesh and who keys the repeater in your PACE plan.

4 — Test & document

  1. Pair nodes and confirm channel/PSK matches preset.
  2. Send text and position reports between buildings — note hop count.
  3. Record node names and roles in frequency scratch pad or incident workspace.
  4. Add Meshtastic as C or E in PACE planner.

Emcomm context: mesh carries situational text — not replacement for SKYWARN voice nets or ICS voice traffic. Pair with deployment workflow step 2.