> 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/commands-v3-state-machine/reference/log-entries.md).

# Log entries

Every entry the robot code logs to the `.wpilog`, by table. Entries marked **RAIDLogs** are read by name; don't rename them. See [Logging](https://docs.raidrobotics.org/commands-v3-state-machine/guide/logging.md).

## Robot-wide (RobotLog)

| Entry                                   | Type    | Meaning                       |              |
| --------------------------------------- | ------- | ----------------------------- | ------------ |
| `DS:enabled`                            | boolean | Robot enabled                 | **RAIDLogs** |
| `DS:autonomous`                         | boolean | In autonomous                 | **RAIDLogs** |
| `Robot/LoopTimeMs`                      | double  | How long the loop's code took | **RAIDLogs** |
| `Robot/MatchTime (s)`                   | double  | Match time remaining          |              |
| `SystemStats/BatteryVoltage`            | double  | Battery voltage               | **RAIDLogs** |
| `SystemStats/BrownedOut`                | boolean | Controller browned out        | **RAIDLogs** |
| `SystemStats/CPUTemp (C)`               | double  | Controller CPU temperature    |              |
| `SystemStats/CANBus/Utilization`        | double  | Mechanism bus load, 0 to 1    | **RAIDLogs** |
| `SystemStats/CANBus/OffCount`           | int     | Bus-off count                 | **RAIDLogs** |
| `SystemStats/CANBus/ReceiveErrorCount`  | int     | Receive errors                | **RAIDLogs** |
| `SystemStats/CANBus/TransmitErrorCount` | int     | Transmit errors               | **RAIDLogs** |

## Drive (SwerveTelemetry)

| Entry                      | Type              | Meaning                            |              |
| -------------------------- | ----------------- | ---------------------------------- | ------------ |
| `Drive/Pose`               | Pose2d            | Where the robot thinks it is       | **RAIDLogs** |
| `Drive/MeasuredSpeeds`     | ChassisVelocities | How fast it's really moving        | **RAIDLogs** |
| `Drive/CommandedSpeeds`    | ChassisVelocities | How fast the code asked it to move | **RAIDLogs** |
| `Drive/Field`              | Field2d           | Field widget                       |              |
| `Drive/OdometryPeriod (s)` | double            | Odometry thread period             |              |
| `Drive/FailedDaqs`         | int               | Failed odometry reads              |              |

## Superstructure

| Entry                           | Type        | Meaning                                    |              |
| ------------------------------- | ----------- | ------------------------------------------ | ------------ |
| `Superstructure/State`          | string      | `IDLE`, `INTAKING`, `HOLDING` or `SCORING` | **RAIDLogs** |
| `Superstructure/Has Game Piece` | boolean     |                                            |              |
| `Superstructure/Ready To Score` | boolean     |                                            |              |
| `Superstructure/Want Intake`    | boolean     | Intake request is up                       |              |
| `Superstructure/Want Score`     | boolean     | Score request is up                        |              |
| `Superstructure/Drawing`        | Mechanism2d | Side-view drawing                          |              |

## Mechanisms

| Entry                       | Type    | Meaning                       |
| --------------------------- | ------- | ----------------------------- |
| `Mechanism1/Angle (deg)`    | double  | Measured angle                |
| `Mechanism1/Target (deg)`   | double  | Where `goTo` told it to go    |
| `Mechanism1/At Target`      | boolean | Within tolerance              |
| `Mechanism1/Command`        | string  | Running command, or `none`    |
| `Mechanism2/Has Game Piece` | boolean | Beam break sees a piece       |
| `Mechanism2/Target (V)`     | double  | Voltage it was told to run at |
| `Mechanism2/Command`        | string  | Running command, or `none`    |

## Vision

| Entry                                  | Type    | Meaning                                             |
| -------------------------------------- | ------- | --------------------------------------------------- |
| `Vision/Mode`                          | string  | `MEGATAG_1` or `MEGATAG_2`                          |
| `Vision/Trusted`                       | boolean | `false` while ignored                               |
| `Vision/<camera>/Connected`            | boolean |                                                     |
| `Vision/<camera>/Used`                 | boolean | Any frame used this loop                            |
| `Vision/<camera>/Rejection`            | string  | Why the newest frame was dropped (`""` = used)      |
| `Vision/<camera>/Pose`                 | Pose2d  | Latest estimate                                     |
| `Vision/<camera>/Tag Count`            | int     |                                                     |
| `Vision/<camera>/Avg Tag Distance (m)` | double  |                                                     |
| `Vision/<camera>/Trust (m)`            | double  | Standard deviation given to the drivetrain          |
| `/limelight-<name>/...`                |         | Each camera's own NetworkTables data (**RAIDLogs**) |

## Auto

| Entry                         | Type   | Meaning                    |
| ----------------------------- | ------ | -------------------------- |
| `Auto/Target Pose`            | Pose2d | Where `driveTo` is heading |
| `Auto/Distance To Target (m)` | double |                            |

## Events

`RobotLog.event(...)` writes timestamped lines, including:

* `Robot code started`
* `Superstructure: HOLDING -> SCORING` (every state change)
* `Superstructure: asked to score with no game piece; skipped`
* `Auto: pose reset to ...`, `Auto: driving to ...`, `Auto: arrived at ...`
* `Auto: step N, ...`, `Auto: finished`

## The .hoot file

Every CTRE device's signals are in the `.hoot` file, written by Phoenix. The template adds:

* `RobotLog` (string): `started`
* `DriveState` (struct): the whole swerve drive state
* `SysIdTranslation_State`, `SysIdSteer_State`, `SysIdRotation_State`, `Rotational_Rate`: SysId


---

# 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/commands-v3-state-machine/reference/log-entries.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.
