> For the complete documentation index, see [llms.txt](https://wzdocs.eaganrobotics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wzdocs.eaganrobotics.com/landing-page.md).

# Landing Page

Thank you for attending our week zero event! In order to allow the event to run as smoothly as possible for your team, we ask that you complete a couple short tasks prior to your arrival on Saturday morning.

* Driver Station
  * Update to latest version: ≥25.0
  * Does your Ethernet adapter/port function correctly? If you have any issues at the event we have USB to Ethernet adapters that can be checked out for the duration of the event.
* Radio
  * Update to latest version: ≥1.2.9
    * This is very important to avoid firmware corruption issues
    * We do have a couple extra radios that can be checked out, but supply is very limited
  * Find a way to mount the radio high up on your robot and on metal to act as a heatsink; see the vh-109 setup documentation
* Robot

We appreciate your help in allowing us to provide you with the best experience possible. See you on Saturday!


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wzdocs.eaganrobotics.com/landing-page.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.