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

heltec power

!74111d8d · updates every minute

3 max hops — This station sets its traffic to be rebroadcast up to 3 times; the firmware default. — 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 5 days Nov 8 to Nov 15 · 5 active days · 15 RF frames · 3 gateways

Nov 8 Nov 15

Most recent

mah base 139m SLT-2798 1192m W⚓ 1233m card2 356f 2249m JT HeltecV4 (MQTT) 3682m

Who heard it

Last 24 hours, plus 4 direct link(s) heard earlier.

This node is a gateway. It has received 3 node(s) itself (11 RF frame(s)) and uplinks its own traffic straight to MQTT — so it is not heard by anything the way an ordinary node is. MQTT is the way out, not a receiver: traffic reaches it through a gateway, and this node is its own.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
mah base both ways 52 RF — 7.5 dB … 5.2 — 2h 19m ago
SLT-2798 both ways 53 RF 0 7.8 dB … -5.2 2 19h 52m ago
W⚓ heard by this node 4 RF — 5.5 dB … -4.8 — 20h 33m ago
card2 356f heard by this node 110 RF 0–1 7.5 dB … 5.2 6 1d 13h ago
JT HeltecV4 (MQTT) 12 RF — 7.0 dB … 2.8 — 2d 13h ago
Meshtastic d8dc heard by this node 1 RF — 1.2 dB — 4d 19h ago
stic2814 heard by this node 1 RF — 6.0 dB — 6d 6h 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.