> For the complete documentation index, see [llms.txt](https://frc-radio.vivid-hosting.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://frc-radio.vivid-hosting.net/overview/upgrading-firmware/checking-firmware-version.md).

# Checking Firmware Version

There are several ways you can tell what version of firmware is on your radio.

## 2025 Kit of Parts Radios

All radios shipped in the 2025 Kit of Parts come with v1.1.2 loaded on them. 

## Check The Box Label

Every box the radio ships in has a label with the firmware version on it. This is only reliable for radios where the firmware has never been updated. 

## Check The Status Page

Set a [static IP](https://www.trendnet.com/press/resource-library/how-to-set-static-ip-address) on your computer:

```
IP Address: 192.168.69.2
Subnet Mask: 255.255.255.0
Gateway: Leave Blank
DNS: 192.168.69.1 or Leave Blank
```

With the radio connected to your computer, you can go to `http://192.168.69.1/status`. This page will display the current firmware version loaded on the radio. 

**NOTE:** This method will work on any radio.

## Check The Config Page (>1.2.3 Only)

Set a [static IP](https://www.trendnet.com/press/resource-library/how-to-set-static-ip-address) on your computer:

```
IP Address: 192.168.69.2
Subnet Mask: 255.255.255.0
Gateway: Leave Blank
DNS: 192.168.69.1 or Leave Blank
```

With the radio connected to your computer, you can go to `http://192.168.69.1/`. This will take you to the radio configuration page which will display the current firmware version. 

**Note:** This method only works if the radio has been updated to 1.2.3 or greater. 


---

# 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://frc-radio.vivid-hosting.net/overview/upgrading-firmware/checking-firmware-version.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.