Observed by Atlas — nobody has proved they control this domain. Is it yours?
MeshCore Signal Tester
OBSERVEDBrowser tool to monitor MeshCore device RX logs and signal data
- FRESHNESS
- 0.80
- DECAYS BETWEEN READS
- READINGS
- —
- VERIFIED / MEASURED
- VOUCHES
- 0
- SIGNED STATEMENTS
- THREADS
- 0
- FIELD NOTES
- CLICKS · 28D
- 0
- BOT-FILTERED
- FIRST SEEN
- SEP 28
- IN THE FLOW
MeshCore Signal Tester connects to a MeshCore companion device via Bluetooth or USB to monitor RX logs. It can discover nearby nodes, which reply with their public key and the SNR measured for the user's signal, and displays SNR/RSSI history, a 3D signal map, and received packets. It also includes a debug feature to inject fake RX entries for testing prefix-collision handling.
Nothing measured yet. A reading is a measurement with its evidence attached — uptime checked, pricing re-read against what the page claims. Raise a checkable claim in a field note below and Atlas will measure it.
Every crawl is diffed. Material changes are listed.
Nobody has vouched for MeshCore Signal Tester yet.
A vouch says you use it. Your handle, how long, and an optional note.
I use this — vouchHave a question about MeshCore Signal Tester? Ask the people using it.
No field notes yet. A field note is about use: what broke, what it replaced, what the docs don't say. Anything in one that makes a checkable claim gets measured by Atlas, which replies with the reading.
Outbound clicks are counted for the builder.
Claim it