> 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/adafruit-feather-m0.md). # Adafruit Feather M0 ### Overview The Adafruit Feather M0 is a compact microcontroller platform used in 3D-PAWS for low-power environmental monitoring and distributed sensor deployments. Depending on the hardware and firmware configuration, a Feather-based station can: * collect measurements from connected environmental sensors * store observations locally on a microSD card * timestamp observations using a real-time clock (RTC) * transmit observations over WiFi * transmit observations over point-to-point LoRa to a central 3D-PAWS gateway * operate as a LoRaWAN node * operate as a standalone data logger without network connectivity Three primary deployment approaches are supported: * **WiFi** – for sites with reliable wireless network access * **LoRa / LoRaWAN** – for low-power wireless sensor deployments * **Local Logging** – for sites where observations are stored locally and retrieved during maintenance visits *** #### Supported Feather Hardware The Feather hardware used depends on the communications requirements of the deployment. For wireless deployments: * **Adafruit Feather M0 RFM95 LoRa Radio** * **Adafruit Feather M0 WiFi with ATWINC1500** For local data logging without network connectivity: * **Adafruit Feather M0 Adalogger** The local logging configuration requires a real-time clock to provide accurate timestamps. Recommended RTC: * **DS3231** {% hint style="info" %} Select the Feather hardware based on the communications available at the deployment site and the role the unit will perform within the observation network. {% endhint %} *** #### Sensors Supported The Feather data logger can support the core 3D-PAWS instruments as well as several additional environmental sensors, including: * rain gauge * anemometer * wind vane * radiation shield sensors for temperature, relative humidity, and pressure * black globe temperature * air quality sensors (PM1.0, PM2.5, PM10) * ultrasonic distance measurements for stream level, storm surge, and snow depth * soil moisture and temperature * leaf wetness * light sensor Actual sensor support depends on the Feather hardware, firmware configuration, and available connections. *** #### Assemble the Feather Data Logger Use the instruction slides below to assemble the Feather data logger hardware. **Instruction Slides for Assembling the Data Logger** {% embed url="" %} *** #### 3D-PAWS Feather Firmware The current Feather firmware is maintained in the **3D-PAWS Feather FullStation GitHub repository**. {% embed url="" %} The repository contains current firmware versions and configuration information for Feather-based 3D-PAWS systems. {% hint style="info" %} Use the GitHub repository as the primary reference for current firmware behavior, supported sensors, measurement intervals, and configuration options. {% endhint %} *** #### Feather Wiring Use the wiring diagram below when connecting sensors and other components to the Feather data logger.
{% hint style="warning" %} Verify sensor pin assignments and wiring before applying power. The connector type or data logger pin label does not necessarily identify the signal type. {% endhint %} For background on Grove, Qwiic, Dupont, I²C, digital pulse, and analog voltage connections, see **Cables and Connectors**. *** #### Feather Data Logger Architecture Feather-based systems collect observations locally and then either store or transmit them depending on the selected configuration. A typical network-connected data flow is: **Sensors → Feather Data Logger → Local Storage → Communications Network → Data Service** The communications path depends on whether the station is using WiFi, point-to-point LoRa, LoRaWAN, or local-only logging. *** #### WiFi Configuration A WiFi Feather can be used where reliable wireless network infrastructure is available. In this configuration: * the Feather collects sensor observations * observations are stored locally * data is transmitted through WiFi to the configured data service This configuration is best suited to stations located near reliable network infrastructure. *** #### LoRa and LoRaWAN Communication Feather-based 3D-PAWS systems can use LoRa radio communication in two different ways: * **LoRaWAN Node** – communication through a compatible LoRaWAN gateway and network * **LoRa Remote Unit** – point-to-point communication with a central 3D-PAWS gateway These configurations may use similar radio hardware, but they differ in how observations are transmitted and routed. *** #### LoRaWAN Node In the **LoRaWAN Node** configuration, the Feather communicates with a compatible LoRaWAN gateway rather than directly with a 3D-PAWS Particle gateway. A typical data path is: **Sensors → Feather LoRaWAN Node → LoRaWAN Gateway → LoRaWAN Network / Data Service** The exact path from the LoRaWAN network to the final data service depends on the network and integration being used. {% hint style="info" %} A LoRaWAN deployment requires compatible LoRaWAN gateway and network infrastructure. This is different from the 3D-PAWS LoRa Remote Unit configuration, which sends observations directly to a central 3D-PAWS gateway. {% endhint %} *** #### LoRa Remote Unit In the **LoRa Remote Unit** configuration, the Feather acts as a remote sensing node. The remote unit: * collects observations from one or more connected sensors * transmits observations over a point-to-point LoRa radio link * sends the observations to a central 3D-PAWS station A Particle Boron equipped with a LoRa receiver is typically used as the central gateway. The data flow is: **Remote Sensors → Feather LoRa Remote Unit → LoRa Radio Link → Particle Boron Gateway → Particle Cloud → CHORDS → Grafana** This configuration is useful for distributed sensor networks where individual sensor locations do not have direct WiFi or cellular connectivity. Typical remote measurements may include: * soil moisture and temperature * precipitation * stream level * snow depth {% embed url="" %} **Instruction Slides for Assembling the Particle LoRa Receiver Harness** {% embed url="" %} *** #### Radio Frequency Considerations LoRa and LoRaWAN radio frequencies are regulated differently by country and region. Verify that the selected Feather radio hardware, frequency band, and operating configuration comply with local spectrum regulations before deployment. *** #### Local Logging Configuration Where network connectivity is unavailable, the Feather can operate as a standalone data logger. In this configuration: * observations are collected from connected sensors * data is stored locally on the microSD card * the RTC provides observation timestamps * no network connection is required * observations are retrieved manually during maintenance visits This configuration can be useful for remote monitoring sites where communications infrastructure is unavailable. *** #### Power Considerations Feather-based systems are designed for low-power environmental monitoring. Actual power consumption depends on: * the Feather board being used * connected sensors * WiFi, LoRa, or LoRaWAN communications * measurement and reporting intervals * firmware configuration Low power requirements make Feather systems particularly useful for remote sensor nodes and distributed monitoring networks. *** #### When to Use a Feather A Feather-based data logger may be appropriate when a deployment requires: * very low power consumption * point-to-point LoRa communication * LoRaWAN connectivity * distributed remote sensor nodes * standalone local data logging * a compact microcontroller-based system For stations that require direct cellular connectivity and extensive remote device management, a Particle-based data logger may be more appropriate. --- # 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/adafruit-feather-m0.md?ask=&goal= ``` `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.