> For the complete documentation index, see [llms.txt](https://3dpaws.comet.ucar.edu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://3dpaws.comet.ucar.edu/building-3d-paws/building-the-core-instruments/testing-the-sensors.md). # Testing the Sensors Guide to verifying 3D-PAWS sensors on a Raspberry Pi before field installation and deployment. Before installing instruments on the weather station, it’s crucial to test all sensors to ensure they’re working correctly. This can be done using a **Raspberry Pi** equipped with a **Grove Base Hat**, which provides easy connections for various sensors. The [**3D-PAWS software**](https://github.com/3d-paws/3D-PAWS-Raspberry-Pi), available on GitHub, simplifies the testing process by handling sensor data acquisition and communication. By following this setup, you can validate sensor functionality and accuracy in a controlled environment before deploying them in the field. You can test the following sensors on the Raspberry Pi at this time: * Anemometer * Wind Vane * Tipping Bucket Rain Gauge * Temperature, Pressure, Relative Humidity sensors * Light Sensor ### Instruction Slides for Testing the Instruments {% embed url="" %} ### Tutorial Video for Aligning the Wind Vane to 0° (N) This video demonstrates testing the Wind Vane. {% embed url="" %} --- # 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://3dpaws.comet.ucar.edu/building-3d-paws/building-the-core-instruments/testing-the-sensors.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.