> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidlogs/reference/checks.md).

# What the checks look for

The checks are rules, run on each match's logs. Thresholds can be tuned per season in [Checks](https://docs.raidrobotics.org/raidlogs/programmers/checks.md).

| Check               | Looks for                                                                                                                     |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Brownout            | The roboRIO browning out                                                                                                      |
| Battery sag         | Voltage dropping too low, and a weak battery at the start of the match                                                        |
| Device reboot       | A CAN device restarting mid-match                                                                                             |
| CAN dropout         | A device dropping off CAN, telling lost power from lost CAN                                                                   |
| Motor temperature   | Motors running hot                                                                                                            |
| Current limit hits  | Motors held at their current limit                                                                                            |
| Stall               | A motor drawing current without moving                                                                                        |
| Disabled mid-match  | A lost connection, an e-stop or a crash during a real match                                                                   |
| Robot code restart  | The robot code restarting during a match                                                                                      |
| Driver station link | Lost connection while enabled, packet loss, trip time, a pegged CPU or CAN bus, controllers dropping out. Starts experimental |

The robot's log needs an enabled signal. Without one, the report card says so: times count from the start of the log and the start-of-match battery check can't run.


---

# 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://docs.raidrobotics.org/raidlogs/reference/checks.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.
