Description of the Tucson Monsoon Data Collection System

MONSOON DATA COLLECTION SYSTEM

I’ve been sharing plots that I automatically generate daily from the sensed data from my Monsoon Data Collection system that sits on my back porch.  I figured that there might be interest in what this system consists of and the vision for what this data could provide.

Photo

System Bill of Materials:

  • Embedded Adventures MOD-1016 Lightning Sensor ((Link)
  • Embedded Adventures MOD-1022 Environmental Sensor ((Link)
  • Adafruit TSL2591 High Dynamic Range Digital Light Sensor ((Link)
  • Raspberry Pi 2 Model B (Link)
  • Raspberry Pi 1/2 size breadboard (Link)
  • Raspberry Pi Digital I/O Extender (Link)
  • Wires, etc., to connect the Raspberry Pi to the I2C Sensors

Sensor Overview

MOD-1016

The Embedded Adventures MOD-1016 is a breakout CCA based on the AS3935 lighting/storm sensor (Link).  This part is interesting because it attempts to handle the more challenging aspects of calibration at the factory .  This saves the experimenter from writing a lot of calibration code.  The MOD-1016 can interface with I2C or SPI, but I typically choose I2C because I’m pretty familiar with the protocol on the Raspberry Pi.

This part also sends interrupts to the Raspberry Pi when something interesting happens.  If it senses excess noise in the environment (for example, my RPi case fan that’s acting up), it will send the interrupt so that the RPi can raise the noise floor.  It will mask what it determines to be human made disturbers that aren’t real lightning (i.e., the microwave oven!).  And finally, it will send an interrupt to inform the RPi when it senses lightning.  When requested by the RPi, the sensor will then deliver a unitless intensity value and an estimated distance.

The AS3935 Franklin Lightning Sensor(tm) is made by AMS and advertises detection of cloud to ground and cloud to cloud lightning within a 40km range.  The part seems to do what it advertises.  The only troubles I have had with it involve interrupts getting “stuck” that force my interrupt service routine to go nuts to service them.  This happened once and I powered the system down for a minute, which fixed it.

Coming soon:

  • Description of other sensors
  • Description of the problem being addressed
  • Description of the intent for the data
  • Discussion of the SW architecture of the system
  • Link to GitHub repository

 

Leave a Reply

Your email address will not be published. Required fields are marked *