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

LANTANA G2

!a038f664 · updates every minute

powered 7 h ago — this node reports itself externally powered rather than running on a battery.

6 max hops — This station sets its traffic to be rebroadcast up to 6 times; some frames went out with a smaller budget, as low as 5 — 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 62 days Sep 15 to Nov 15 · 62 active days · 2187 RF frames · 31 gateways

Sep 15 Nov 15

Most recent

Meshtastic eeff no pin 115m ERM Base M2 Temp 474m KQ4OOB - Base 835m CWP3Node 1315m CENCOM 1395m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Meshtastic eeff 408 RF — -7.0 dB … -15.5 — 1h 55m ago
ERM Base M2 Temp 2 RF — hop distance not reported — 7h 54m ago
KQ4OOB - Base 2 RF — hop distance not reported — 13h 55m ago
CWP3Node 1 RF — relayed — not attributable — 21h 55m ago
CENCOM 1 RF — hop distance not reported — 23h 15m ago
FoxTastic-Home 1 RF — hop distance not reported — 23h 55m 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.