> 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/setting-up-the-data-logger/arduino-mkr.md).

# Arduino MKR

### Overview

The **Arduino MKR Data Logger** is a microcontroller-based platform that can be used to operate a 3D-PAWS weather station. It provides low-power sensor polling, local data storage, and optional cellular data transmission.

The MKR platform runs the **3D-PAWS MKR Full Station firmware**, which reads environmental sensors, timestamps observations, and stores measurements locally on a microSD card. When connectivity is available, data can be transmitted to remote services such as **CHORDS** for visualization and analysis.

The MKR system is designed for **compact, low-power weather stations**, making it suitable for solar-powered deployments and experimental monitoring systems.

***

### Supported Hardware

The MKR implementation typically uses one of the following boards:

* **Arduino MKR NB 1500** – LTE cellular connectivity
* **Arduino MKR GSM 1400** – GSM cellular connectivity

Supporting components typically include:

* MicroSD card for local data storage
* Real-Time Clock (RTC) module
* Cellular SIM card
* Cellular antenna
* EEPROM memory

***

### Instruction Slides for Assembling the Data Logger

{% embed url="<https://docs.google.com/presentation/d/1hOtuYt_uVrD-8RlnOs4yGO56pUlioobT/view>" %}

***

### Sensors Supported

* Light sensor
* Rain Gauge
* Anemometer
* Wind Vane
* Radiation Shield (Temperature, Pressure, & Relative Humidity)
* Globe Temperature
* Air Quality (PM 1.0, 2.5, 10)
* Distance Gauge (Stream, Storm Surge, and Snow Height)
* Soil Moisture and Temperature
* Leaf Wetness

Additional sensors may be integrated depending on the station configuration.

***

### Data Flow

In a typical MKR-based station, data flows through the system as follows:

```
Sensors
   ↓
Arduino MKR Data Logger
   ↓
Local Storage (microSD card)
   ↓
Cellular Network
   ↓
CHORDS Data Portal
   ↓
Grafana Visualization
```

Local storage ensures measurements are preserved even if connectivity is temporarily unavailable.

***

### Firmware

The firmware used for MKR-based stations is available from the 3D-PAWS GitHub repository:

**3D-PAWS MKR Full Station**

{% embed url="<https://github.com/3d-paws/3D-PAWS-MKR-FullStation>" %}

The repository contains:

* station firmware
* configuration parameters
* sensor interface libraries
* hardware pin mappings

Users should download the latest version when configuring a station.

***

### Notes

* Stations using MKR should be fully tested before deployment to verify sensor readings and connectivity.
* A properly configured **SIM card and cellular signal** are required for remote data transmission.
* Local SD storage provides a backup if cellular connectivity is interrupted.

***

### MKR Wiring Diagram

<figure><img src="/files/wY7IgeVMeXPQ0CkAKeAE" alt=""><figcaption></figcaption></figure>


---

# 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/building-3d-paws/setting-up-the-data-logger/arduino-mkr.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.
