PacketTrends Mesh a public map of nodes that asked to be on one map stations

ViVSoft.live M9

!daf1569b · updates every minute

5 max hops — This station sets its traffic to be rebroadcast up to 5 times; some frames went out with a smaller budget, as low as 1 — Meshtastic spends fewer hops on a reply than on a broadcast, so this is the reply economy rather than a second setting; above the default of 3. — this is what the station SETS, not how far away it is; the value is carried unchanged through every relay.

This node advertises a name but no position, so it has no pin on the map. That is an ordinary state rather than a fault — a node broadcasts its identity on one schedule and its location only if its owner enabled that, and most of the mesh never does.

History

Heard on 2 days Nov 13 to Nov 14 · 2 active days · 27 RF frames · 4 gateways

Nov 13 Nov 15

Most recent

ViVSoft.live MQTT Gateway 678m david79-uconsole 1023m Peacock Point 1055m Magi-Mesh aea4 1160m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
ViVSoft.live MQTT Gateway 19 RF 0 7.2 dB … 4.8 1 11h 18m ago
david79-uconsole 2 RF — -18.0 dB — 17h 3m ago
Peacock Point 1 RF — relayed — not attributable — 17h 35m ago
Magi-Mesh aea4 1 RF — relayed — not attributable — 19h 20m ago
Reading the hop budget. Every Meshtastic frame carries a hop limit that each relay decrements. A reception showing 0 left is one that arrived with nothing to spare — one more relay in the path and it would not have arrived at all. That is the closest this data comes to explaining a loss, and it is still not a loss: a frame that was dropped is exactly the one that never reached a gateway to be counted here.