> For the complete documentation index, see [llms.txt](https://docs.voting.works/vxsuite-user-manual-v4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voting.works/vxsuite-user-manual-v4/vxscan/vxscan-diagnostics.md).
# VxScan Diagnostics
The diagnostics interface is used to test hardware before or between elections and monitor the status of the machine. It is accessible from both the election manager and system administrator menus.
The VxScan diagnostics screen shows information about how the machine is configured, how much storage is left on the device, and the current status of the scanner and printer. Prior to each election, walk through each test to verify each component is in working order. During normal operations, if one of the components fails, VxScan will display an error message on screen.
Select *`Perform Test Scan`* and insert a blank sheet of paper as prompted. This test verifies the scanner is clean and ballot images are clear. If the test fails, you'll be prompted to clean the scanner. The test will also fail if the sheet is not blank.
Select *`Print Test Page`* to ensure the paper roll is installed properly. If the paper roll was installed backwards, nothing will print. After the test print completes, you must indicate whether the print was successful or not.
Select *`Test Sound`* to verify the speaker is working properly.
Select *`Test Uninterruptible Power Supply`* to confirm that the UPS is connected and fully charged.
The most recent test result for each piece of hardware is shown on the diagnostics screen and included in the readiness report.
The readiness report can be used as a record of system diagnostic verification. Select *`Save Readiness Report`* to save a copy to a USB drive.
Example VxScan Readiness Report
---
# 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.voting.works/vxsuite-user-manual-v4/vxscan/vxscan-diagnostics.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.
.png?alt=media)