> 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/preparacion-del-registrador-de-datos-raspberry-pi.md).

# Preparación del registrador de datos Raspberry Pi

La Raspberry Pi 3B+ junto con un Grove Base Hat se utiliza como un registrador de datos flexible para los siguientes sensores: luz, temperatura, humedad, presión, velocidad/dirección del viento y precipitación, utilizando la [biblioteca de Python 3D-PAWS](https://github.com/3d-paws/3D-PAWS-Raspberry-Pi). Esta configuración admite conectividad celular y Wi-Fi para la transmisión remota de datos. El Grove Hat simplifica las conexiones de los sensores mediante puertos I2C, UART o analógicos, mientras que se puede añadir un módem celular opcional para conectividad 2G/LTE. Los datos se almacenan localmente en una tarjeta SD como respaldo en caso de que la conexión celular o Wi-Fi falle. La biblioteca 3D-PAWS proporciona scripts preconstruidos para el sondeo de sensores y el registro de datos.

Para más información sobre el Registrador de Datos con Raspberry Pi, visite nuestra página de Registradores de Datos:

{% content-ref url="/pages/0mPbQIlbyEGe8ByIGn1B" %}
[Raspberry Pi](https://3dpaws.comet.ucar.edu/es/registradores-de-datos/raspberry-pi.md)
{% endcontent-ref %}

{% embed url="<https://docs.google.com/presentation/d/1sH6N3GTW11H_3-o4cB8OhboRhFW9mXof/edit?ouid=102244773211795243299&rtpof=true&sd=true&usp=drive_link>" %}


---

# 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/preparacion-del-registrador-de-datos-raspberry-pi.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.
