How to Test and Map Meshtastic Coverage

How to turn field observations into an honest, repeatable public coverage map.

Decide what the map means

A coverage map can represent predicted reach, one-time observations, repeated successful delivery or a service expectation. Those are not equivalent. MeshAtlas should label predicted and measured areas separately and record the test date, modem preset, test-node antenna, height and direction. A point where one beacon was heard is evidence of reception at that moment—not proof of dependable messaging everywhere around it.

Design the test

Keep the infrastructure node fixed and use a known mobile test node. Record its hardware, antenna, firmware, region, preset, frequency slot, transmit power and placement in the vehicle or on the person. Select routes that cross predicted coverage boundaries, terrain shadows, valleys, dense urban blocks and important user locations. Include stationary checkpoints as well as moving samples.

Test uplink and downlink. A map built only from packets transmitted by the mobile node can hide a weak mobile receive path. Use numbered messages or automated beacons with timestamps, and keep a record of packets sent—not just packets received—so packet loss can be estimated.

Collect useful fields

Field	Why it matters
Time and coordinates	Places the observation and supports later comparison
Sender and receiver	Defines the tested direction
Sequence number	Reveals missing packets
RSSI and SNR	Describes the received packet at that receiver
Hop information	Separates direct coverage from relayed delivery
Preset and firmware	Makes results reproducible
Antenna and placement	Explains major link-budget differences

Map direct and mesh service separately

If the goal is to evaluate one infrastructure site, prevent other relays from turning the result into an accidental regional mesh test, or at least mark packets that arrived through hops. Direct radio coverage answers where that site can be heard. End-to-end mesh coverage answers where users can exchange packets through the currently available network. Both maps are useful, but combining them without distinction produces misleading conclusions.

Interpret boundaries honestly

Radio coverage is probabilistic and changes with foliage, weather, vehicle orientation, buildings, local interference and receiver position. Show measured points or confidence bands rather than drawing a hard circle. Mark dead zones inside the broader area. Repeat important routes at different times, and retain negative samples. “No reception” is valuable data when the test setup and transmitted sequence are known.

Publish metadata and limitations

A public map should state when it was measured, what equipment was used, whether the packets were direct, which preset applied and how many attempts supported each classification. Avoid publishing a private host’s exact location if approximate coordinates are the agreed policy. Archive the raw data so later firmware, antenna or site changes can be compared.

Classify service levels

Instead of coloring every received point equally, define useful classes. For example: reliable two-way direct service, intermittent direct service, service available only through the current mesh, and no verified service. Publish the packet-count threshold used for each class. A community may choose stricter thresholds for fixed facilities than for casual outdoor messaging.

Do not interpolate confidently across untested valleys, streets or the far side of a ridge. Terrain and urban clutter create sharp local changes. An honest sparse map with visible evidence is more useful than a smooth polygon that suggests certainty.

Repeat after meaningful changes

Create a new test version after moving an antenna, changing feed line, power, preset, firmware or relay topology. Keep previous observations instead of silently overwriting them; they explain why coverage changed. Seasonal foliage can also justify summer and winter datasets. When volunteers contribute results, provide one test profile and minimum metadata so their points can be compared.

Related field guides

Official sources

Firmware, applications and documentation change over time. Confirm current setting names and applicable regional rules before commissioning or changing live infrastructure.