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

Meshtastic 8e48

!03a8f9f0 · firmware 2.8.2.d5f1619 · reports 2 node(s) online locally · 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.

History

Heard on 2 days Nov 15 to Nov 16 · 2 active days · 8 RF frames · 1 gateway

Nov 15 Nov 16

Most recent

N1DSK-9 579m Meshtastic 7164 no pin 887m

Who heard it

Last 24 hours.

This node is a gateway. It has received 1 node(s) itself (1 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
N1DSK-9 8 RF — 6.5 dB … 6.0 — 9h 39m ago
Meshtastic 7164 heard by this node 1 RF — 6.8 dB — 14h 47m 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.