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

Meshtastic 7625

!8e317625 · updates every minute

99% 4.18 V · 8 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.

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 35 days Oct 9 to Nov 15 · 35 active days · 315 RF frames · 18 gateways

Oct 9 Nov 15

Most recent

ERM Gateway 48m CWP3Node 102m KQ4OOB - Base 236m ERM Base M2 Temp 288m Meshtastic eeff no pin 1008m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
ERM Gateway 2 RF — hop distance not reported — 48 min ago
CWP3Node 3 RF — relayed — not attributable — 1h 42m ago
KQ4OOB - Base 4 RF — hop distance not reported — 3h 56m ago
ERM Base M2 Temp 3 RF — relayed — not attributable — 4h 48m ago
Meshtastic eeff 1 RF — relayed — not attributable — 16h 48m 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.