CrawlSpaceSensor

From RevSpace
Jump to: navigation, search
Project CrawlSpaceSensor
CrawlSpaceSensor.jpg
Water level sensor inside crawl space
Status In progress
Contact bertrik
Last Update 2017-05-22

Introduction

This is a project idea for monitoring the crawl space under a house for water ingress. Basically looking for a nice use case to try out these miniature LIDAR sensors that are now available cheaply (about E8,-).

This things monitors the crawl space for the following properties:

  • water level (in case it is flooded), using a VL53L0X lidar sensor
  • humidity and temperature using a DHT11 or DHT22

Measurement data is uploaded once an hour over WiFi to an MQTT server.

Since there is likely no mains power easily available in a crawl space, it is battery operated.

TODO:

  • think about the measurement mechanics: direct measurement of level, or floaty thing (ball) in a tube

Theory

Reflection

The range measurement of the VL53L0X module is based on time-of-flight of the laser signal reflecting off a surface.

Wikipedia shows the formula for the reflection off an interface between two materials with different refractive index at normal incidence, examples:

  • for air-glass, we have n1=1.00 and n2=1.50, the reflection coefficient is 4%.
  • for air-water, we have n1=1.00 and n2=1.33, the reflection coefficient is 2%.

A reflection coefficient of 2% is quite low, and indeed some experimentation showed difficulties determining range towards the fluid level in a glass of water. Perhaps a practical way is to measure distance to some floating object instead, like a piece of white polystyrene foam, or a ping-pong ball.

Calibration

We're considering only a ranging offset error in the measurement system.

Assume:

  • L is the water level (mm)
  • R is the distance measured by the lidar between the module and the water

The water level L can be calculated from the range R as follows:

 level L (mm) = Constant C (mm) - range R (mm)

So, once we know the actual water level L (as measured using some external means) and range R (as measured by the lidar module), we can calculate the constant C as:

 C = L + R

Design

The plan is to use an ESP8266 to read the sensors, connect to the house WiFi and upload the measurement data once an hour. When not measuring, the ESP8266 is put in deep-sleep mode. Time-of-day is retrieved using (S)NTP.

Hardware

  • ESP8266 in a Wemos D1 mini board, because they're so easy to use
  • LiFePO4 battery, because they have about the right voltage for direct drive and are safe to use
  • VL53L0X LIDAR module to accurately measure the water level
  • DHT11, DHT22 or AM2302 to measure humidity and temperature

Pin connections

ESP8266 pin Connect to Remark
D0 ESP8266 RESET Loopback wire to allow the ESP to wake itself from deep sleep
D1 VL53L0X SCL I2C clock
D2 VL53L0X SDA I2C data
D3 VL53L0X SHDN Shutdown pin
D5 DHT11 GND GND from GPIO
D6 DHT11 DATA DHT11 DATA pin
D7 DHT11 VIN Power supply from GPIO
3V3 VL53L0X VIN Power supply
GND VL53L0X GND Ground

VL53L0X LIDAR

This module integrates a VCSEL laser, a photo diode, probably some analog circuitry and a small microcontroller to do digital processing. It has an I2C interface, but it seems you need a library from ST to get an actual meaningful distance out of it.

I'm not actually sure how it works exactly, it measures the time-of-flight between light sent out by the laser and received back through the photo diode. Apparently it involves averaging a lot of individual measurements, since the API manual mentions:

 "Increasing the timing budget increases the range measurement accuracy. That is: x N on timing budget => standard deviation / square root of N. For example is the timing budget is increased by a factor of x 2, then the range measurement standard deviation decreases by square root of 2."

Taking a measurement after reset requires a couple of initialisation/calibration steps, I need to figure out which ones are actually relevant for my use case.

The API describes basically three ranging profiles with impact on the time required to do one measurement:

  • high accuracy
  • high speed
  • long range.

I plan to use the high accuracy mode since measurement time is not very important (doing only one measurement per hour and the run-time is already dominated by other tasks).

The API user manual indicates the following settings for high accuracy mode:

  • a "signal rate" of 0.25 (I guess this is a measure for the amplitude of the laser return signal)
  • a "sigma" of 18 mm
  • a measurement timing budget of 200 ms

I think the accuracy can be further improved, e.g. by increasing the measurement time and reducing the sigma limit. According to the remark mentioned earlier, I expect that doubling the accuracy requires four times the measurement time. So for example, I think it should be possible to spend 3200 ms instead of 200 ms on the measurement, which theoretically should give 4 times the accuracy.

Using a cover glass on top of the sensor makes things more complicated, so I plan to not use a cover glass.

Software

Source code

The source code for the measurement application is available on github.

I'm using the pololu library for communication with the VL53L0X. As I understand this is not simply a wrapper around the code from ST, but is a kind of reverse engineered code.

Measurement cycle timing

Software tasks in one measurement cycle are: (estimated run-time)

  • wake up from deep sleep (0.3s)
  • connect and authenticate to the WiFi (4.8s)
  • perform an SNTP request to get the current date/time (0.1s)
  • perform a distance measurement using the LIDAR (0.2s)
  • perform temperature/humidity measurement (0.1s)
  • publish measurements to MQTT (0.1s)
  • calculate sleep time until next wakeup and enter deep-sleep (0.0s)

Total about 5.6 seconds per measurement cycle.

Initially, when no WiFi network is known, the sensor starts its own access point presenting a captive portal allowing a WiFi network to be selected.

Data format

The plan is to encode the measurement data in JSON and post it as text on a MQTT topic.

Exampled of proposed data format:

{
    "id": "12AABB",
    "time": 123456789,
    "humidity": 87,
    "temperature": 21.4,
    "range": 78
}

Where id is the ESP8266 unique id (in hex), time is in seconds since 1970/1/1 (UTC), humidity in percent, temperature in degrees Celcius and range in millimeters.

The "range" value represents the distance between the sensor and the fluid. A higher range means a lower fluid level.

Libraries

The plan is to use the following libraries:

  • WifiManager to handle WiFi authentication and presenting a captive portal if it cannot authenticate
  • pololu VL53L0X library

Battery Life

A typical LiFePO4 "AA" (14500) type battery has 700 mAh capacity. An 18650 type battery has approximately double capacity compared to a 14500 battery, about 1500 mAh.

Sleep current is estimated to be about 0.15 mA total (about 80 uA for the ESP8266 in deep-sleep, about 50 uA for the DHT11/22, about 5 uA for the VL53L0X in HW standby mode).

When awake, current consumption is estimated to take 70 mA on average for 5.6 seconds. This means each measurement takes about 0.11 mAh.

So, over one measurement cycle of one hour, total charge consumed sums up to a total of about 0.26 mAh. With a 700 mAh battery this would allow about 2500 measurements, making the battery last about 100 days.

Interesting links