Difference between revisions of "RPi/datalogger"

From Interaction Station Wiki
Jump to: navigation, search
m
m
Line 20: Line 20:
 
[[File:RPIDL DISP GPS Connected.jpg|300px|GPS disconnected]]<br>
 
[[File:RPIDL DISP GPS Connected.jpg|300px|GPS disconnected]]<br>
 
The last line will show the actual time in UTC and the GPS status shows either if it is waiting for a GPS fix or (when the blue light on the GPS is blinking) the LAT and LON coordinates of the last received message.
 
The last line will show the actual time in UTC and the GPS status shows either if it is waiting for a GPS fix or (when the blue light on the GPS is blinking) the LAT and LON coordinates of the last received message.
 +
 +
=Preparing a new install=
 +
Create a Dexter GrovePi SD card following one of the following paths explained in the Dexter Industries GrovePi manual: https://www.dexterindustries.com/BrickPi/brickpi-tutorials-documentation/getting-started/pi-prep/
 +
<br><br>
 +
Next in the home directory clone the grovepy_sensorlogger git repository:
 +
<syntaxhighlight lang="bash" enclose="div">
 +
git clone https://github.com/mywdka/grovepi_sensorlogger.git
 +
</syntaxhighligh>
 +
<br>
 +
Copy <code>grovepi_sensorlogger/fs/boot/sensors.txt</code> into the boot partition of the SD card (/boot on the PI itself). Adjust according to the installed sensor as outlined below.<br>
 +
<br>
 +
Copy <code>grovepi_sensorlogger/fs/etc/rc.local</code> into <code>/etc/rc.local</code> on the PI or create your own startup script starting <code>sensorlogger.py</code>.
  
 
=Attaching the sensor=
 
=Attaching the sensor=

Revision as of 20:57, 30 April 2017

Sensor shield with gas sensor attached

Overview

The data logger is a grovepi+ shield with attached:

  • a grove sensor
  • a grove OLED 128x64 display
  • a GPS USB dongle


The PI can be powered by a USB power bank.
Note: When using a Raspberry PI A or B (not B+) the sudden current draw may cause the powerbank to shutdown. Quickly unplugging an plugging back in can help. If not, remove the grove shield, plug in the powerbank and attach the shield. From B+ and up this problem does not occur.

As soon as the datalogger is booted (can take a while) the OLED screen will show something similar as:
GPS disconnected
It shows the following:

  • type of sensor
  • GPS status
  • sensor data


If the GPS is switched on (blue led on the GPS dongle is on) the display will show the following:
GPS disconnected
The last line will show the actual time in UTC and the GPS status shows either if it is waiting for a GPS fix or (when the blue light on the GPS is blinking) the LAT and LON coordinates of the last received message.

Preparing a new install

Create a Dexter GrovePi SD card following one of the following paths explained in the Dexter Industries GrovePi manual: https://www.dexterindustries.com/BrickPi/brickpi-tutorials-documentation/getting-started/pi-prep/

Next in the home directory clone the grovepy_sensorlogger git repository:

git clone https://github.com/mywdka/grovepi_sensorlogger.git
</syntaxhighligh>
<br>
Copy <code>grovepi_sensorlogger/fs/boot/sensors.txt</code> into the boot partition of the SD card (/boot on the PI itself). Adjust according to the installed sensor as outlined below.<br>
<br>
Copy <code>grovepi_sensorlogger/fs/etc/rc.local</code> into <code>/etc/rc.local</code> on the PI or create your own startup script starting <code>sensorlogger.py</code>.

=Attaching the sensor=
Currently there are 7 sensors possible:
* Sound sensor (connected to A0)
* Moist sensor (connected to A0)
* Temperature & Humidity (connected to D4)
* Gas sensor MQ-9 (connected to A0)
* LDR (non-grove) (connected to A0)
* Air quality sensor (connected to A0)
* UV sensor (connected to A0)

The OLED display has to be connector to I2C-1

The datalogger needs to be told what sensor is connected. To do this there is a file in the BOOT partition of the Raspberry PI SD card. This file is called <code>sensors.txt</code>. In this file uncomment the sensor connected and comment the rest by placing a # in front of the sensor name.<br>

=Reading the log file=
As soon as the datalogger is turned on and the GPS is connected it will start logging data in the <code>log.csv</code> file in the BOOT partition of the Raspberry PI SD card. It will start logging even if there is no valid GPS fix. So the logger can be used indoors as well. Wheter there is a valid GPS coordinate associated with a log entry can be seen by the Fix field in the log file. If this field contains a 0 the coordinates for this entry are either the last valid coordinates or the coordinates hardcoded if there has not been a fix before.

The log.csv is a standard CSV file with the following columns:
* timestamp (UTC)
* latitude
* longitude
* signal quality
* sensor type
* following column(s) are sensor dependant

Each time the datalogger is started a new header and entries are appended to any existing log file. Hence it is possible for the log.csv file to contain multiple headers. If a clean log file is needed, remove it before starting the datalogger or remove previous entries up to the last occurrence of the header. <br>

==Example log entry==
<code>
timestamp (UTC),latitude,longitude,signal quality,sensor type,density

13:38:54,51.918777,4.486358,0,"Grove gas MQ9 sensor (CO, Coal, Liquified)",0.12
<code>
<br>
==Adding new sensors==
The code can be found in the MyWDKA GitHub repository: https://github.com/mywdka/grovepi_sensorlogger
Sensor entries are in the sensors subdirectory. It is easiest to have a look at the existing sensors and copy e.g. simple_light.py as a general framework:

<syntaxhighlight lang="Python" line start="1" enclose="div">
import time
import grovepi
from threading import Thread

class Sensor(Thread):
    def __init__ (self, pin, avg_fraction=0.8):
        Thread.__init__(self)
        self.name = "Simple light sensor"
        self.shortname = "light"
        self.pin = pin
        self.avg_fraction = avg_fraction
        self.value = 0
        self.avg_value = 0
        self.stop = False

        grovepi.pinMode(pin, "INPUT")

    def get_log_header(self, delimiter):
        return "raw%caverage" % (delimiter)

    def get_log_string(self, delimiter):
        return "%.2f%c%.2f" % (self.value, delimiter, self.avg_value)

    def get_str1(self):
        return "val: %.2f" % (self.value)

    def get_str2(self):
        return "avg: %.2f" % (self.avg_value)

    def avg(self, current, new, fraction):
        return (current * (1.0-fraction)) + (new * fraction)

    def run(self):
        while not self.stop:
            try:
                self.value = grovepi.analogRead(self.pin)
                self.avg_value = self.avg(self.avg_value, self.value, self.avg_fraction)
            except IOError as e:
                print ("light sensor exception: %s" % (e))
            time.sleep(0.01)

Add a corresponding entry to the import select statement (or better, improve this ugly thing :) in sensorlogger.py

  1. if SENSOR == 'sound':
  2.     from sensors.sound import Sensor
  3.     sensor = Sensor(0, 0.5)
  4. elif SENSOR == 'dht':
  5.     from sensors.dht import Sensor
  6.     sensor = Sensor(4)
  7. elif SENSOR == 'uv':
  8.     from sensors.uv import Sensor
  9.     sensor = Sensor(0)
  10. elif SENSOR == 'dust':
  11.     from sensors.dust import Sensor
  12.     sensor = Sensor()
  13. elif SENSOR == 'gas':
  14.     from sensors.gas import Sensor
  15.     sensor = Sensor(0)
  16. elif SENSOR == 'air':
  17.     from sensors.air import Sensor
  18.     sensor = Sensor(0)
  19. elif SENSOR == 'moist':
  20.     from sensors.moist import Sensor
  21.     sensor = Sensor(0)
  22. elif SENSOR == 'simple_light':
  23.     from sensors.simple_light import Sensor
  24. sensor = Sensor(0)


Start the datalogger.py script with the sensor as first argument. This can be done in rc.local or any other startup script. As example:

cat /boot/sensor.txt | grep -v "#" | xargs sudo python /home/pi/grovepi_sensorlogger/sensorlogger.py &