> 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/programmers/pit-laptop-tools.md).

# Pit laptop tools

Two commands, run from a checkout of the RAIDLogs repo with Bun.

## Convert hoot files

`bun run hoots <folder>` converts every CTRE `.hoot` file in a folder (for example a USB stick) to a `.hoot.wpilog` beside it, using CTRE's owlet. File names are kept exactly, because RAIDLogs reads the match and CAN bus from them. Get owlet from CTRE's CLI tools page, then put it on your PATH, pass `--owlet <path>`, or set `OWLET`. Add `--watch` to convert new files as they're copied in.

## Upload without signing in

`bun run hoots <folder> --watch --upload --event <event key>` also uploads each converted file and any `.wpilog`, `.dslog` and `.dsevents` that appears, filing each into its match. A file that can't be placed is refused, never guessed.

It needs a pit uploader key: an admin makes one in **Manage › API keys › Pit uploader keys** (it's shown once). On the laptop, set `RAIDLOGS_UPLOAD_KEY` to the key and `RAIDLOGS_URL` to the app's Convex site URL. A key can upload log files and nothing else. If the laptop is lost, revoke the key and make a new one.

## Replay the checks

`bun run replay <files or folders>` runs the checks on this laptop exactly as the app does, prints each match's findings, and ends with how often each check fired. Try a threshold change with `--set stall.amps=60` on a season of real logs before changing a default. `bun run replay --help` lists every check and setting.


---

# 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/programmers/pit-laptop-tools.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.
