Build Instructions

Collapse

• 1

  Step 1: Wiring the Sensor Node

  Follow the system connection matrix to wire your sensory peripherals directly to a 30-pin ESP32 DevKit v1. All peripherals operate natively at 3.3V logic levels:

   DHT11 VCC connects directly to the ESP32 3V3 power rail.

   DHT11 DATA connects to GPIO 23.

   DHT11 GND connects to the common system GND plane.

   IR Flame Sensor VCC connects directly to the ESP32 3V3 power rail.

   IR Flame Sensor DO connects to GPIO 25. This digital signaling output pin drops to an active LOW state whenever infrared radiation from an open flame is verified.

   IR Flame Sensor GND connects to the common system GND plane.

   Neo-6M GPS VCC connects to 3V3.

   Neo-6M GPS TX connects directly to GPIO 16 (mapped to hardware Serial2 RX).

   Neo-6M GPS RX connects directly to GPIO 17 (mapped to hardware Serial2 TX).

   Neo-6M GPS GND connects to the common system GND plane.

  Note: The primary Ground Control Station (GCS) base unit requires no sensor wiring layouts; it operates as a standalone bare ESP32 linked directly to a laptop via its USB interface connection.

• 2

  Step 2: Setting Up the IDE Environment & Libraries

  1. Open your Arduino IDE application interface.
  2. Navigate directly to File > Preferences and add the official Espressif development link to your Additional Boards Manager URLs field:

  https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_index.json

   3. Open Tools > Board > Boards Manager, run a targeted search for esp32 by  Espressif Systems, and initialize the download. This framework provides native, underlying libraries for both WiFi.h and esp_now.h.

   4. Access Sketch > Include Library > Manage Libraries and install the following toolkits:

  • DHT sensor library (distributed by Adafruit)
  • Adafruit Unified Sensor (underlying dependency layer)
  • TinyGPS++ (distributed by Mikal Hart)

   5. Connect your device to a data port, select Tools > Board > ESP32 Dev Module, and establish the mapped active COM Port link.

• 3

  Step 3: Configuring & Flashing Firmware Nodes

  Download the complete core codebase files directly from the repository index. For every independent sensor node deployed into your canopy grid, you must manually iterate the variables inside the configuration block at the top of the AranyaLink_Node.ino file before hitting upload.

  // Change these parameters sequentially for every individual hardware node deployed
  
  #define NODE_ID 1 // Unique integer tracking index per node: 1, 2, 3, 4...
  
  #define NODE_LAT_FALLBACK 12.345678 // Default deployment latitude coordinate quadrant
  
  #define NODE_LON_FALLBACK 98.765432 // Default deployment longitude coordinate quadrant
  
  #define TEMP_THRESHOLD 50.0f // Trigger target in °C (raise to 55.0f-60.0f in extreme summer environments)
  
  #define FLAME_ACTIVE LOW // Low setting matches standard KY-026 active outputs
  
  

  •   NODE_ID: Every independent field module must carry its own standalone sequence integer to map verification traces accurately across data packets .

  •  Fallback Coordinates: These values function as geometric placeholders during initialization loops until the active Neo-6M module gains a satellite fix, which automatically overrides fallback telemetry with live streaming coordinate flags.

  To prepare your receiver base station, open AranyaLink_GCS.ino and upload the firmware directly to your baseline ESP32 module with zero software parameter alterations required.

View all 6 instructions