> 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/validating-rf-performance.md).
# Validating RF Performance
## Overview
Starting in the VH-109 1.2.0 firmware release, teams will be able to validate RF performance in regard to their mounting configuration on their robot.
An RF performance indicator is displayed in both "Robot Radio" and "Access Point" modes.
When configured as an access point, additional details are displayed.
Connectivity Statistics displayed while in Team Access Point mode
## Connection Quality
The connection quality levels are as follows:
| Quality Level | Pass/Fail |
| ---------------------------------------------------- | --------- |
| Excellent (4 Bars) | Pass |
| Good (3 Bars) | Pass |
| Caution (2 Bars) | Pass |
| Warning (1 Bar) | Fail |
When using a VH-109 in the team access point mode, ensure that the VH-109 is oriented such that the LEDs are facing toward the field and ethernet ports are facing toward the Red and Blue alliance stations. The VH-109 in the team access point mode should be placed at the scoring table position at an elevated position using the stand provided in the ***VH-109 -> VH-113 Conversion Kit***
Navigate to the configuration page assigned to the team number at **`http://10.XX.YY.4/`**
The connection quality for the link should be "Excellent" or "Good". When "Caution" is displayed often, try an alternative mounting location for your radio based on the [Mounting Your Radio](/overview/mounting-your-radio.md) guide.
When "Warning" is displayed, your radio MUST be moved to ensure a competitive experience during a match.
---
# 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/validating-rf-performance.md?ask=&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.
