> 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/es/instrumentos/mantenimiento-rutinario-de-las-estaciones.md).

# Mantenimiento Rutinario de las Estaciones

El mantenimiento regular es fundamental para garantizar la confiabilidad y precisión de los datos de la estación meteorológica. Esto incluye revisiones rutinarias de la limpieza y calibración de los sensores, así como verificar que todas las conexiones estén seguras y libres de corrosión. Inspeccione el montaje de la estación y su integridad estructural, especialmente después de eventos meteorológicos extremos, para prevenir daños o desalineaciones. Además, actualice el software y el firmware periódicamente para incorporar correcciones de errores y nuevas funciones. Al priorizar estas tareas, puede evitar vacíos de datos, mantener la precisión de los sensores y prolongar la vida útil del equipo, asegurando en última instancia que la estación continúe proporcionando datos meteorológicos consistentes y fiables a lo largo del tiempo.

{% embed url="<https://docs.google.com/presentation/d/1REiTkhZ0cCW801s1za9OFODzGhFviQEL/edit?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 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/es/instrumentos/mantenimiento-rutinario-de-las-estaciones.md?ask=<question>&goal=<user_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.
