> 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/particle-iot.md). # Particle IoT ### Overview The Particle Data Logger is the primary data logger platform used in many 3D-PAWS deployments. 3D-PAWS supports two Particle platforms: * **Particle Boron** – cellular connectivity * **Particle Argon** – WiFi connectivity In a 3D-PAWS station, the Particle data logger: * collects measurements from connected environmental sensors * stores time-stamped observations on a microSD card * transmits observations through the Particle Cloud * supports remote monitoring and diagnostics * supports remote firmware updates The **Boron** is typically used for remote deployments that require cellular connectivity, while the **Argon** can be used where reliable WiFi is available. *** #### Sensors Supported The Particle 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 (PM2.5) * ultrasonic distance measurements for stream level, storm surge, and snow depth * soil moisture and temperature * leaf wetness * light measurements using the legacy light sensor Actual sensor support depends on the firmware configuration and available data logger connections. *** #### Assemble the Particle Data Logger Use the instruction slides and tutorial videos below to assemble the Particle data logger hardware. **Instruction Slides for Assembling the Data Logger** {% embed url="" %} **Tutorial Videos for Assembling the Data Logger** {% embed url="" %} {% hint style="info" %} The video playlist demonstrates the complete assembly process. Use the playlist controls to move between individual assembly videos. {% endhint %} *** #### Set Up the Particle Data Logger After assembling the hardware, use the setup slides below to configure the Particle device and prepare it for use with 3D-PAWS. **Instruction Slides for Setting Up the Data Logger** {% embed url="" %} *** #### 3D-PAWS Particle Firmware The current 3D-PAWS Particle firmware is maintained in the **3D-PAWS Particle FullStation GitHub repository**. [**https://github.com/3d-paws/3D-PAWS-Particle-FullStation**](https://github.com/3d-paws/3D-PAWS-Particle-FullStation) To download the firmware: 1. Open the repository. 2. Select the green **Code** button. 3. Select **Download ZIP**. The repository is the primary reference for current firmware releases, configuration information, and firmware documentation. *** #### Particle Data Logger Wiring Use the wiring diagram below when connecting sensors and instruments to the Particle data logger.
{% hint style="warning" %} Verify sensor pin assignments and connections before applying power. The physical connector or data logger pin label does not necessarily identify the signal type. {% endhint %} For additional background on Grove, Qwiic, Dupont, I²C, digital pulse, and analog voltage connections, see **Cables and Connectors**. *** #### Particle Cloud and Remote Management Particle-based stations use the Particle Cloud for remote communication and device management. Particle devices support: * event streaming, including **FS** and **INFO** messages * remote commands through **DoAction** * over-the-air firmware updates * remote device monitoring through the Particle Console * management of groups or fleets of devices through Particle Products **Particle Resources** Use the following Particle resources when configuring or managing a data logger: * [**Particle Device Setup**](https://setup.particle.io/) – initial device configuration * [**Particle Status LED and Device Modes**](https://docs.particle.io/troubleshooting/led/) – interpreting device status and connection behavior * [**Particle Console**](https://docs.particle.io/getting-started/console/console/) – monitoring and managing individual devices * [**Particle Products**](https://docs.particle.io/getting-started/products/introduction-to-products/#introduction) – managing groups or fleets of 3D-PAWS devices *** #### Particle Data Logger Architecture In a Particle-based 3D-PAWS station, observations move from the sensors through the data logger and Particle Cloud before reaching the 3D-PAWS data services. **Sensors → Particle Data Logger → Particle Cloud → CHORDS → Grafana** The Particle data logger collects and stores observations locally, while the Particle Cloud provides the communications layer used to transmit data and manage the device remotely. {% hint style="info" %} For information about transferring observations from Particle Cloud to CHORDS, see **Particle / CHORDS Integrations**. {% endhint %} *** #### Cellular Connectivity and Third-Party SIMs Particle Boron models provide cellular connectivity for remote deployments. Cellular compatibility depends on the Boron model and the cellular networks available at the deployment location. Some deployments may require an external SIM rather than the Particle internal SIM. → [**Use a Third-Party SIM with the Boron**](https://docs.google.com/document/d/1fyzIF64ErrC-jGK6rduwHd6FOxpQzs5SD4UBigmqnyI/edit?tab=t.0#heading=h.9lhrwate7irz) *** #### Firmware Configurations 3D-PAWS Particle firmware can be configured for different monitoring applications and operational requirements. Configuration may affect: * measurement intervals * reporting intervals * power consumption * supported sensors * communications behavior The latest firmware and configuration documentation should be obtained from the [**3D-PAWS Github repository**](https://github.com/3d-paws). {% hint style="info" %} Use the firmware documentation associated with your station configuration rather than assuming that all Particle-based 3D-PAWS stations use the same measurement or reporting intervals. {% endhint %} *** #### LoRa Remote Sensors Particle-based stations can also serve as gateways for remote sensor units that communicate using LoRa. Remote sensor units using [**Adafruit Feather M0 data loggers**](/building-3d-paws/setting-up-the-data-logger/adafruit-feather-m0.md) can be used for measurements such as: * soil moisture and temperature * precipitation * stream level * snow depth In this configuration, remote sensor units transmit observations over LoRa to a central 3D-PAWS station. The Particle Boron then forwards those observations through its cellular connection. This allows sensors to be distributed in locations that do not have direct cellular or WiFi connectivity. *** #### Power Considerations Particle data logger power consumption varies with: * connected sensors * cellular signal conditions * measurement frequency * reporting interval * firmware configuration * communications activity Solar and battery systems should therefore be sized for the specific station configuration and deployment environment. {% hint style="info" %} Previously calculated Particle system power values should be treated as planning estimates unless they have been verified through direct measurements on the complete station configuration. {% endhint %} See [**Solar Power**](/building-3d-paws/solar-power.md) for guidance on station power systems. --- # 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/particle-iot.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.