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

Celerity Solar

!a0cc127c · updates every minute

91% 4.07 V · 41 min ago

3 max hops — This station sets its traffic to be rebroadcast up to 3 times; some frames went out with a smaller budget, as low as 2 — Meshtastic spends fewer hops on a reply than on a broadcast, so this is the reply economy rather than a second setting; the firmware default. — 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 30 days Oct 15 to Nov 15 · 30 active days · 3323 RF frames · 27 gateways

Oct 15 Nov 15

Most recent

JT HeltecV4 (MQTT) 36m !9e766638 no pin 40m TTB Base ed94 40m BenClient 40m Mandarin a37e💥 156m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
JT HeltecV4 (MQTT) 1 RF — relayed — not attributable — 36 min ago
!9e766638 1 RF — relayed — not attributable — 40 min ago
TTB Base ed94 11 RF 1 relayed — not attributable 1 40 min ago
BenClient 26 RF 1 relayed — not attributable 1 40 min ago
Mandarin a37e💥 17 RF — relayed — not attributable — 2h 36m 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.