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

K3DO-T1

!7a6d6334 · updates every minute

100% 4.11 V · 2 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.

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 18 days Sep 28 to Nov 15 · 18 active days · 105 RF frames · 3 gateways

Sep 28 Nov 15

Most recent

KR4CKW-BASE 151m Pi3 MeshtasticD no pin 429m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
KR4CKW-BASE 1 RF — hop distance not reported — 2h 31m ago
Pi3 MeshtasticD 2 RF — hop distance not reported — 7h 9m 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.