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

SDGMRS EOC

!d0c1e879 · updates every minute

97% 4.15 V · 10 h 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.

7 max hops — This station sets its traffic to be rebroadcast up to 7 times; the maximum Meshtastic allows. — 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 61 days Sep 15 to Nov 14 · 61 active days · 1782 RF frames · 40 gateways

Sep 15 Nov 15

Most recent

CWP3Node 601m CommGuy Base - MeshAdv 601m ERM Gateway 684m MTDL Base - MaxOffRoadin WRUV246 no pin 1044m ERM Base M2 Temp 1224m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
CWP3Node 1 RF — relayed — not attributable — 10h 1m ago
CommGuy Base - MeshAdv 1 RF — relayed — not attributable — 10h 1m ago
ERM Gateway 1 RF — hop distance not reported — 11h 24m ago
MTDL Base - MaxOffRoadin WRUV246 1 RF — relayed — not attributable — 17h 24m ago
ERM Base M2 Temp 1 RF — hop distance not reported — 20h 24m ago
FoxTastic-Home 1 RF — hop distance not reported — 20h 24m 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.