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

KK4VTF Atlavox Beacon

!ae62e496 · updates every minute

87% 4.03 V · 15 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.

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 17 days Oct 30 to Nov 15 · 17 active days · 257 RF frames · 16 gateways

Oct 30 Nov 15

Most recent

Peacock Point 241m PersonaNonGrata [MQTT] [BOT] no pin 241m Broadband Operations & Relay Gateway 510m Moka 671m KO4HXD- 2 967m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Broadband Operations & Relay Gateway 1 RF — 0.8 dB — 8h 30m ago
Moka 5 RF — -16.8 dB … -18.8 — 11h 11m ago
Peacock Point 2 RF — relayed — not attributable — 4h 1m ago
PersonaNonGrata [MQTT] [BOT] 3 RF — relayed — not attributable — 4h 1m ago
KO4HXD- 2 2 RF — relayed — not attributable — 16h 7m 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.