Radio & mesh concepts
Mesh networks combine RF settings, shared secrets, and topology. This page explains shared theory so you can configure Meshtastic® or MeshCore™ without guessing—always apply local regulations for power and duty cycle. For where to tap in the app, use Meshtastic mobile app or MeshCore mobile app. For when to pick which stack (ad-hoc vs stable infrastructure), read the comparison on Introduction.
Channels, names, and keys
- Channel name – Human-readable label; everyone on the channel must use the same name and key material (depending on platform).
- Pre-shared key (PSK) – Shared secret for a private group. If one device is wrong, you will see silence or garbled traffic—there is nothing to “debug” over the air without matching keys.
- Public / default channels – Convenient for testing; treat them as public regardless of the name.
Meshtastic® supports multiple channels with different keys; plan one primary for your crew and add extras for special cases.
Region and frequency
Region selects permitted bands, channel plans, and often power limits. Wrong region is both illegal and antisocial to other spectrum users.
After setting region:
- Re-check TX power defaults.
- Confirm antenna is appropriate for the band and connector type.
RF parameters (how speed vs range works)
- Spreading factor (SF) – Higher SF generally increases range and reduces data rate; airtime increases (watch duty cycle limits).
- Bandwidth – Wider bandwidth can increase throughput but changes sensitivity tradeoffs depending on stack defaults.
- Coding rate – Error correction tradeoffs where exposed by the firmware.
If messages are slow but reliable, you may be airtime-limited or simply long-range constrained—raising TX power is not always the right first move.
Node identity
- Long name / short name – Shown to peers; avoid embedding sensitive personal data.
- User info / team fields – Treat as public metadata on shared channels.
Power and batteries
Higher TX power:
- Increases current and heat.
- May reduce battery life faster than expected.
- Still cannot fix a bad antenna or obstructed path.
Mesh behavior (expectations)
- No guarantee of routes – Topology changes with movement, foliage, and interference.
- Hidden-node problems happen when two endpoints cannot hear each other but both hear a third—adding a repeater or improving antenna height may help.
- Encryption protects payload in many designs; metadata patterns may still leak information—study your threat model.
Best practices (short list)
- Match keys exactly across nodes on a private channel.
- Document your region and channel plan for the team.
- Test with two nodes before scaling up.
- Iterate RF settings deliberately—change one major variable at a time.
Platform-specific screens differ—use the Meshtastic mobile app or MeshCore mobile app guide and upstream docs for exact menu paths.