> 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/station-maintenance-and-operations/station-maintenance.md).

# Station Maintenance

### Overview

Routine maintenance ensures that 3D-PAWS stations continue to operate reliably and produce high-quality data over time.

Maintenance includes inspection, cleaning, system checks, and periodic component replacement.

***

### Routine Maintenance

Perform regular inspections:

* inspect sensors and mounts for damage
* verify all cables and connections are secure
* clean the sensors and solar panel (remove dust and debris)
* check battery condition and voltage
* ensure the enclosure is sealed and protected from moisture

***

### Sensor Maintenance

#### Rain Gauge

* remove debris (leaves, dirt, insects)
* ensure tipping mechanism moves freely
* verify level installation

***

#### Wind Sensors

* confirm free rotation (no binding)
* inspect for physical damage or debris
* check mounting stability

***

#### Radiation Shield (Temperature / Humidity / Pressure)

* clean surfaces if dirty
* ensure ventilation openings are clear
* verify no insect nesting

***

#### Soil Sensors (if installed)

* confirm good soil contact
* inspect for disturbance or exposure
* check cable integrity

***

### System Checks

* confirm data transmission is active
* verify sensor readings are updating
* check for unexpected or unrealistic values
* monitor battery voltage trends

***

### Lifecycle Planning

Over time, components may degrade or fail. Plan for:

* sensor replacement
* battery replacement
* cable wear and repair
* enclosure maintenance

| Component        | Typical Lifespan |
| ---------------- | ---------------- |
| Batteries        | 2–3 years        |
| Sensors          | 3–5 years        |
| Cables           | 3–5 years        |
| 3D-printed parts | 5+ years         |

→ See [**Sensor Lifecycle Planning**](/station-maintenance-and-operations/sensor-lifecycle-planning.md)

***

### Documentation

Record maintenance activities:

* date and conditions
* work performed
* issues observed
* parts replaced

→ See [**Station Metadata**](/deploying-3d-paws/station-metadata.md) and [**Asset Management**](/station-maintenance-and-operations/asset-management.md)

***

### Common Maintenance Issues

The following issues may develop over time and can often be identified during routine maintenance:

| ❌ Issue              | ✅ Action                                |
| -------------------- | --------------------------------------- |
| No data transmission | Check power and connectivity            |
| Incorrect readings   | Inspect sensors and siting              |
| Intermittent data    | Check wiring and connections            |
| Physical damage      | Repair or replace components            |
| Low battery          | Check solar input and replace if needed |

***

### Summary

Regular maintenance improves system reliability, extends station lifespan, and ensures consistent data quality.

***

### Instruction Slides for Routine Maintenance

{% embed url="<https://docs.google.com/presentation/d/1lMNNqnBr8TgxWYTIGRd9mA-_XadPr-9D/edit?ouid=102244773211795243299&rtpof=true&sd=true&usp=sharing>" %}


---

# 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://3dpaws.comet.ucar.edu/station-maintenance-and-operations/station-maintenance.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.