Skip to main content

​
Overview

OWL DMS supports multiple firmware types for Duck devices, each designed for specific use cases. This guide covers firmware options for both PapaDuck (gateway) and MamaDuck (sensor node) devices.

​
PapaDuck Firmware Variants

PapaDuck devices serve as the gateway between your mesh network and the cloud. Choose the variant that matches your connectivity requirements.
Description: The standard PapaDuck firmware connects to your WiFi network to relay mesh network data to the cloud. This is the recommended option when you have reliable WiFi coverage at your gateway location.Features:
  • Connects to 2.4GHz WiFi networks
  • Secure TLS connection to AWS IoT Core
  • Receives and forwards all mesh network messages
  • Queues messages when temporarily disconnected
  • LED status indicator for connection state
Requirements:
ComponentDetails
HardwareAny supported PapaDuck device
WiFi Network2.4GHz network (5GHz not supported)
PowerContinuous USB or wall power recommended
LED Status Indicators:
LED ColorStatus
GreenWiFi connected, communicating with cloud
RedNo WiFi connection
BlueTransmitting data
Use Cases:
  • Indoor gateway installations
  • Locations with reliable WiFi coverage
  • Office or building deployments
  • Home mesh network setups
Description: This advanced PapaDuck variant provides dual connectivity using both WiFi and LTE cellular. WiFi is the primary connection, but if WiFi becomes unavailable, the device automatically falls back to LTE to ensure your mesh network data always reaches the cloud.Features:
  • Primary WiFi connection with automatic LTE fallback
  • Seamless switching between WiFi and cellular
  • Periodic WiFi reconnection attempts (every 10 minutes when on LTE)
  • Secure TLS connection over both WiFi and cellular
  • Message queuing during connection transitions
  • LED status indicator for connection state
Special Hardware Required: This firmware requires specific hardware - see requirements below.
Hardware Requirements:
ComponentDetails
BoardLilyGo T-SIM7000G with LoRa Hat
SIM CardActivated IoT SIM card (Hologram recommended)
AntennaLTE antenna (included with board)
PowerUSB or battery power
The LilyGo T-SIM7000G board combines the SIM7000G cellular modem with an ESP32. You need the version with the LoRa hat attachment to enable mesh network communication.
What You Need to Provide:
  1. LilyGo T-SIM7000G board with LoRa Hat - Available from LilyGo or electronics retailers
  2. Activated IoT SIM card - The firmware is configured for Hologram SIM cards by default, but other IoT SIM providers work as well
  3. WiFi credentials - Your 2.4GHz network SSID and password
  4. LTE antenna - Usually included with the board
Connection Priority:
PriorityConnectionWhen Used
1WiFiAlways preferred when available
2LTEAutomatic fallback when WiFi unavailable
LED Status Indicators:
LED ColorStatus
GreenConnected (WiFi or LTE)
RedNo connection (neither WiFi nor LTE)
BlueTransmitting data
Connection Behavior:
  • On startup, attempts WiFi connection first
  • If WiFi fails after 3 retries, initializes LTE modem
  • When on LTE, periodically checks for WiFi availability (every 10 minutes)
  • Automatically switches back to WiFi when it becomes available
  • Messages are queued if both connections temporarily fail
Use Cases:
  • Remote or outdoor gateway installations
  • Locations with unreliable WiFi
  • Mobile gateway deployments
  • Disaster response and emergency networks
  • Agricultural or rural deployments
  • Backup connectivity for critical networks

​
MamaDuck Firmware Types

MamaDuck devices collect sensor data and relay messages through the mesh network. Some firmware types require physical sensors to be connected to GPIO pins.
Device Compatibility: The sensor firmware types below are available for MamaDuck devices only.
Description:
Sends GPS coordinates periodically through the mesh network, perfect for asset tracking and mobile monitoring applications.Features:
  • Built-in GPS functionality (no external sensors needed)
  • Periodic location updates
  • Configurable update intervals to optimize battery life
  • Latitude, longitude, and altitude tracking
Configuration Options:
SettingOptionsRecommendation
GPS Interval5, 10, 15, 30, or 60 minutes15-30 min for balanced battery/accuracy
Update FrequencyLow to HighHigher frequency = more battery drain
Use Cases:
  • Asset tracking and logistics
  • Personnel location monitoring
  • Mobile sensor deployment
  • Wildlife tracking
  • Vehicle fleet management
Hardware Requirements:
  • No external sensors required
  • GPS module included in standard MamaDuck hardware
Description:
Monitors temperature and atmospheric pressure using the BMP180 sensor. Ideal for weather monitoring and basic environmental sensing.Features:
  • Temperature measurement (-40°C to +85°C)
  • Barometric pressure (300-1100 hPa)
  • Low power consumption
  • I2C communication protocol
Configuration Options:
SettingOptionsNotes
Sensor Interval30 sec to 60 minHow often sensor readings are taken
GPIO PinConfigurablePin for sensor connection (I2C SDA/SCL)
Hardware Required: You must physically connect a BMP180 sensor to your MamaDuck device before using this firmware.
Hardware Connection:Required Components:
  • BMP180 sensor module
  • 4 jumper wires
Wiring Diagram:
BMP180 PinMamaDuck PinDescription
VCC3.3VPower supply
GNDGNDGround
SDAGPIO 21 (default)I2C Data
SCLGPIO 22 (default)I2C Clock
Most BMP180 modules operate at 3.3V. Double-check your module’s voltage requirements before connecting.
Use Cases:
  • Weather station networks
  • Altitude monitoring
  • Indoor/outdoor climate tracking
  • Agricultural monitoring
Description:
Advanced temperature and pressure monitoring with higher precision than BMP180. Ideal for applications requiring accurate environmental data.Features:
  • Higher precision measurements
  • Temperature measurement (-40°C to +85°C)
  • Barometric pressure (300-1250 hPa)
  • Better noise performance
  • Low power consumption
Configuration Options:
SettingOptionsNotes
Sensor Interval30 sec to 60 minMeasurement frequency
GPIO PinConfigurablePin for sensor connection (I2C)
Hardware Required: You must physically connect a BMP390 sensor to your MamaDuck device before using this firmware.
Hardware Connection:Required Components:
  • BMP390 sensor module
  • 4 jumper wires
Wiring Diagram:
BMP390 PinMamaDuck PinDescription
VCC3.3VPower supply
GNDGNDGround
SDAGPIO 21 (default)I2C Data
SCLGPIO 22 (default)I2C Clock
Precision Comparison:
MetricBMP180BMP390
Pressure Accuracy±1 hPa±0.5 hPa
Temperature Accuracy±1°C±0.5°C
Power ConsumptionStandardLower
CostLowerHigher
Use Cases:
  • Precision weather monitoring
  • Scientific data collection
  • Altitude-sensitive applications
  • Research deployments
Description:
Monitors temperature and relative humidity using the DHT11 sensor. Perfect for indoor climate monitoring and agricultural applications.Features:
  • Temperature measurement (0-50°C)
  • Relative humidity (20-90%)
  • Cost-effective solution
  • Simple single-wire digital interface
Configuration Options:
SettingOptionsNotes
Sensor Interval30 sec to 60 minReading frequency
GPIO PinConfigurableDigital pin for sensor data
Hardware Required: You must physically connect a DHT11 sensor to your MamaDuck device before using this firmware.
Hardware Connection:Required Components:
  • DHT11 sensor module
  • 3 jumper wires
Wiring Diagram:
DHT11 PinMamaDuck PinDescription
VCC5V (or 3.3V)Power supply
GNDGNDGround
DATAGPIO 4 (default)Data signal
DHT11 sensors can work with both 3.3V and 5V. Check your module’s specifications. Some modules have built-in pull-up resistors.
Sensor Specifications:
SpecificationRange/Value
Humidity Range20-90% RH
Humidity Accuracy±5% RH
Temperature Range0-50°C
Temperature Accuracy±2°C
Sampling RateMax 1Hz (once per second)
Use Cases:
  • Indoor climate monitoring
  • Greenhouse automation
  • HVAC optimization
  • Food storage monitoring
  • Museum/archive environmental control
Description:
Controls external addressable LEDs (NeoPixel/WS2812B) to display rainbow patterns. Useful for visual indicators, device testing, and demonstrations.Features:
  • Rainbow pattern display
  • Supports multiple LEDs in series
  • Addressable RGB control
  • Configurable LED count
Configuration Options:
SettingOptionsNotes
Number of LEDs1-60Total LEDs in your strip/ring
GPIO PinConfigurableDigital pin for LED data
PatternRainbow (default)Pattern display mode
Hardware Required: You must physically connect WS2812B/NeoPixel LEDs to your MamaDuck device before using this firmware.
Hardware Connection:Required Components:
  • WS2812B LED strip or NeoPixel ring
  • External power supply (for >8 LEDs)
  • Jumper wires
Basic Wiring (1-8 LEDs):
LED PinMamaDuck PinDescription
VCC5VPower (USB power OK for few LEDs)
GNDGNDGround
DINGPIO 4 (default)Data input
For More LEDs (>8):
When using more than 8 LEDs, use an external 5V power supply. Connect the power supply ground to MamaDuck GND, but power the LEDs from the external supply’s 5V output.
Power Considerations:
LED CountCurrent DrawPower Source
1-8 LEDs<400mAUSB power OK
9-30 LEDs400mA-2AExternal 5V required
30+ LEDs2A+Dedicated power supply
Use Cases:
  • Device status indication
  • Network presence visualization
  • Testing and demonstrations
  • Event notifications
  • Educational projects

​
Configuration Best Practices

  • Increase sensor intervals: 30-60 minutes for sensors, 30-60 minutes for GPS
  • Disable external LEDs: Turn off when not needed for testing
  • Choose appropriate sensors: BMP390 uses less power than DHT11 at high sampling rates
  • Optimize GPS interval: Use 30-60 minute intervals for non-critical tracking
  • BMP180/390: Allow 2-3 minutes warm-up time after power-on
  • DHT11: Don’t sample faster than once every 2 seconds
  • GPS: Allow clear view of sky for best accuracy
  • All sensors: Protect from direct sunlight and moisture
  • Verify voltage levels: Most sensors use 3.3V, some tolerate 5V
  • Use quality jumper wires: Poor connections cause intermittent failures
  • Secure connections: Use hot glue or electrical tape to prevent disconnections
  • Test before deployment: Verify sensor readings before field installation
  • Document GPIO pins: Note which pins you used for future reference

​
Troubleshooting

Check:
  • Sensor is properly connected to correct GPIO pins
  • Power and ground connections are secure
  • GPIO pin number matches firmware configuration
  • Sensor is compatible (voltage levels)
Solution:
  • Verify wiring with multimeter
  • Try different GPIO pins
  • Check sensor with example code
Common causes:
  • Sensor needs warm-up time
  • Poor electrical connections
  • Sensor damaged or counterfeit
  • Sampling rate too high
Solution:
  • Wait 2-3 minutes after power-on
  • Replace jumper wires
  • Source sensors from reputable suppliers
  • Increase sensor interval
Check:
  • Device has clear view of sky
  • GPS antenna is connected
  • Allow 1-2 minutes for initial fix
  • Not indoors or under heavy foliage
Solution:
  • Move to open area
  • Check antenna connection
  • Wait for initial satellite lock
Check:
  • LED data pin connected to correct GPIO
  • LEDs powered (5V for WS2812B)
  • Ground shared between Duck and LEDs
  • Number of LEDs matches configuration
Solution:
  • Verify wiring connections
  • Test LEDs with separate power supply
  • Reduce number of LEDs if underpowered

​
Next Steps

Flash Firmware

Ready to flash? Follow the flashing guide

Device Types

Learn more about Duck device types

Network Management

Manage your deployed devices

Dashboard

View sensor data in real-time

​
Support

Need help with firmware or connecting sensors?

OWL IoT Discord Community

Ask the community for help

Email Support

Contact our support team