Skip to content

debugging: a collision says whether it hit the header or the payload #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
A13xB0 wants to merge 3 commits into
base: main
Choose a base branch
from
Open

debugging: a collision says whether it hit the header or the payload #47

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
032c2b3
debugging: a collision says whether it hit the header or the payload
LargeSpark Oct 16, 2026
732ba3a
debugging: say which nodes are told a frame failed
LargeSpark Oct 16, 2026
cbf3cfc
debugging: a frame never locked onto leaves the preamble flag set
LargeSpark Oct 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions pages/debugging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,17 @@ consoles and link budgets, with the Inspector for whichever node is selected.
| no route | nothing relayed it | regions, `flood_max`, loop detection |
| dropped by region | the node does not hold the scope | the region map, or the scope being sent on |

A collision says where it landed. "Decoded its header, then N symbol(s) were
destroyed" is a frame whose payload failed its CRC; "locked on, then N of its 8
header symbols were destroyed" is a header the receiver could not read. The
receiving node's firmware is told the same thing its radio would report: a CRC
error, with the damaged bytes, or a header error and nothing more. A frame the
receiver could detect and never locked onto, because something stronger
swamped it while its preamble was still to be found, raises nothing, as on the
radio: on a native node the preamble flag stays set until the firmware clears
it, and a receiver re-armed part-way through a frame loses that frame. Only
native firmware builds that support it are told; emulated boards are not yet.

"It did not arrive" and "it arrived 3 dB under the floor" lead to completely
different fixes, which is why the cause is recorded rather than a boolean.

Expand Down