> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/s2-radio-system-manual/s2-system-description/s2-node/s2-communication-protocol/s2-commands-details/get_debug_counters-command-3f.md).

# GET\_DEBUG\_COUNTERS, Command 3F

Radio

OUT

| 07 | 11 | 3F | GRP | ID | ID TO | CRC |
| -- | -- | -- | --- | -- | ----- | --- |

IN

| 10 | 10 | 4F | GRP | ID | ID TO | CRC | C0 | C1 | C2 | C2 | C4 | C5 | C6 | C7 | CRC |
| -- | -- | -- | --- | -- | ----- | --- | -- | -- | -- | -- | -- | -- | -- | -- | --- |

&#x20;

UART

OUT

| 06 | 00 | 3F | X | X | X |
| -- | -- | -- | - | - | - |

&#x20;IN

| Length | 10 | 4F | GRP | ID | CRC | C0 | C1 | C2 | C2 | C4 | C5 | C6 | C7 | C8 | C9 | C10 | CRC |
| ------ | -- | -- | --- | -- | --- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | --- | --- |

Where X means don’t care. Length is either 0x10 or 0x13 (when node type is 11).

&#x20;

This command is used to read out values stored in statistics counters. v54 defines 8 counters.

c0 – number of faults of DS18\[S/B]20 sensor

c1 – number of faults of DS1821 sensor

c2 – number of faults of SHT7x sensor

c3 – number of faults of PT100/PT1000 sensor

c4 – number of sensor’s subsystem restarts

c5 – sensor which caused sensor’s subsystem restart

c6 – number of CRC errors in incoming radio messages

c7 – number of  node restarts (watchdog)

&#x20;c8 – (Only node type 11) The number of “Frame Errors” (radio timeouts)

c9 – (Only node type 11) Sent messages on radio

c10 – (Only node type 11) Received messages on radio

&#x20;

These counters will wrap around zero. None of them is cleared or initiated during startup therefore it’s possible to measure number of restarts of node.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.boomerang3.com/s2-radio-system-manual/s2-system-description/s2-node/s2-communication-protocol/s2-commands-details/get_debug_counters-command-3f.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
