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

DD-mt2

!3f8afdfe · updates every minute

56% 3.77 V · 18 days ago — telemetry is far patchier than position (only about a quarter of nodes send it at all), so an old reading here is ordinary rather than a sign of trouble.

History

Silent for 18d 14h Sep 19 to Oct 28 · 34 active days · 1698 RF frames · 6 gateways

Sep 19 Nov 16

Most recent

DD-mt3 26770m Alpha137_Base 26880m DD10-mtb 26880m DD04-mt4 27224m

Who heard it

DD0 stations first (2), then direct links. Last 24 hours, plus 4 direct link(s) heard earlier.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
DD-mt3 both ways 355 RF — 8.0 dB … 5.5 — 18d 14h ago
DD04-mt4 heard by this node 6 RF — 7.5 dB … 5.5 — 18d 21h ago
Alpha137_Base heard by this node 131 RF — -2.0 dB … -19.8 — 18d 16h ago
DD10-mtb heard by this node 12 RF — 6.5 dB … 5.5 — 18d 16h 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.