Document History
	Version	Date	Authors	Description	Validator	Validation Date
	0.0.1	18/01/2016	MACE Quentin, NOUGUIER Thibaut, RAMEL Régis	Développement d'une application de détection de passages devant un capteur de présence	Oliver Gattaz	06/04/2016

Introduction

Goal of the project

The aim of the project is to learn how to use the Cohorte platform to develop a web application which displays an historic of measures made by a sensor and stored on a remote server.

The main point of the project is to be able to transmit and process the information from the measures given by the sensor to the processed data on the user interface. Moreover, there is a more mathematical step, that consist in calculating the speed with the frequency, and filtering the signal to eliminate noise.

Scope of the product

The implementation of the sensor on the Raspberry and the process of measures can be added on any other application that needs movement detection in front of the sensor. The steps of calculation and storage on the server have to be autonomous so that any number of sensors are connected to the application.

The storage on the server and the interface have to be scalable. During the project, we only have one sensor, but the application we want to develop should be able to displays data form several sensors, which are characterised by a unique identifier, a name, an owner, GPS coordinates, … Besides, an interface has to be implemented on the Raspberry so that the owner can define all these attributes on the sensor in a way that it can be clearly identified by the Cohorte application.

Definitions, acronyms and abbreviations

Raspberry Pi : Reduced size computer (ARM processor), compatible with devices like keyboards, mouses, … The Raspberry Pi can host a program, providing many opportunities of use. In our project, the Raspberry is linked to the Arduino, and host the python modules that process the data and send it to the server.

Arduino : Programmable microcontroller able to generate and analyse electric signals. For our project, the Arduino get the measures from the HB100 sensor. Once the voltage and frequency values are available, they are transformed into distance and speed values, and send to the Raspberry by serial link.

ARM processor : Low consumption processor, equipped with a simpler architecture than other families of processors. ARM processors are mainly used on embedded computing like smartphones.

HB100 : Proximity sensor that provide a voltage and frequency measure. The voltage gives an information about the distance between the sensor and the object, whereas the frequency allows to calculate the speed of the object thanks to the Doppler effect (see below). The distance variation corresponds to the direction of movement.

Cohorte : Development platform created by Isandlatech that provides tools to program distributed applications on different independent devices, including the programming languages. Cohorte allows to do component oriented programming, which means that the application is flexible, and the different components are autonomous.

SQLite : Database engine in a C library that allows table interrogation with SQL requests. In our server, the database contains only one table, so SQLite is quite enough for the management of the server.

Doppler effect : Physical phenomenon that consist in a frequency shift between the transmitter and the receiver when the distance between them is changing. With this phenomenon, we can calculate the speed of an object thanks to the relation between the measured frequency and the speed of the object.

Raw data : Data returned by the sensor and send to the Arduino (voltage, frequency, timestamp).

Processed data : Data returned by the process of raw data on the Raspberry (average speed, maximum speed, direction, date).

Synthetic data : Analysis of processed data. For example, it could be a distribution of the flow during a month, or at a precise moment of the day, or also an historic of speed.

Timestamp : date, hour, minute and second when the measure is done.

Description of the project

Product perspective

The product is meant to be a presence detector whose measurements are saved to interrogate them in the user interface. We could imagine many use like domestic surveillance (a detector with a bell), or also a road traffic detector.

In a fuller version of the product, we should integrate an authentication system that allows groups of users with different access permissions.

Product functions

The sensor is able to measure speed and distance. Therefore, the aim is to detect the speed of objects in front of the sensor (pedestrians, cyclists, cars, …) and date this detection. The web interface gets the data from the server and displays it with the possibility to restrict to a certain time of day, or a date range, or to make graphs.

General constraints

The constraints of the project are the use of Cohorte and the Raspberry Pi with the sensor.

There is no constraint about the programming language, because thanks to Cohorte, the different components can be developed in different languages : Python or Java for the Raspberry, Java and SQLite for the server, and HTML/CSS/Javascript for the web interface.

Specific requirements, covering functional, non-functional and interface requirements

Functional requirements

Data acquisition function

Getting of physical values : speed and distance

Sending of processed data by consuming a service provided by a remote component.

Aggregation function

Storage of the data in a server.

User interface function

Data presentation components.

Non-functional requirements

Quality of the network

Store the data on the device allows to avoid losing data in the event of link loss.

Sensor environment

The measurements have to be filtred to eliminate the noise generate by the environment (street, wind, …).

Interface requirements

Compatibility multi-platform (different browser, mobile version of the software).

Interactivity (date range selection, creation of graphs, …).

Cas d'usage

Interaction de l’utilisateur avec l’interface web

- L’utilisateur entre sur le site web et s’authentifie avec un login et un mot de passe

- L’utilisateur peut choisir de cliquer sur “tout” pour afficher l’ensemble des données de tous les capteurs (triées par date décroissante)

-la date / vitesse moyenne / sens / capteur

- L’utilisateur choisit un capteur parmi la liste des capteurs installés (vert : connecté, rouge : déconnecté) :

-onglet données élaborées :

-le système affiche les données élaborées dans un tableau (triées par date décroissante)

- la date (Heure / Minute / Jour / Mois / Année) / vitesse moyenne (km/h) / sens (sens du capteur, contresens du capteur)

- L’utilisateur peut cliquer sur les liens de pagination pour naviguer dans les données élaborées

- L’utilisateur peut filtrer les données affichées en fonction des paramètres suivants :

- entre deux dates d1 et d2

- une vitesse max / min.

- onglet données synthétisées :

- L'utilisateur peut obtenir des analyses paramétrées des données élaborées en choisissant l'option "historique" en fontion de :

- un type de donnée :

- le nombre de passages

- la vitesse moyenne (km/h)

- la vitesse maximum (km/h)

- une plage de date :

- une date de début (JJ/MM/AAAA)

- une date de fin (JJ/MM/AAAA)

- une plage horaire :

- heure de début (HH/MM)

- heure de fin (HH/MM)

- L'utilisateur peut également obtenir une répartition des vitesses de passage en choisissant l'option "répartition" en fonction de :

- onglet administrateur :

- le système affiche un tableau des événements relatifs au capteur sélectionné (trié par date décroissante) :

- une plage de date :

- une date de début (JJ/MM/AAAA)

- une date de fin (JJ/MM/AAAA)

- une plage horaire :

- heure de début (HH/MM)

- heure de fin (HH/MM)

- la date (Heure / Minute / Jour / Mois / Année)

- l’état (connecté, déconnecté)

- L’utilisateur peut se déconnecter

Interaction du technicien avec le capteur

- Le technicien branche le capteur au réseau internet du client

- Le technicien démarre le capteur

Interaction du technicien avec l’interface d’administration du capteur

- Le technicien ouvre la page d’administration du capteur

- Le technicien remplit un formulaire :

- L’identifiant du capteur

- Coordonnées GPS du capteur (longitude latitude, altitude (décimales))

Appendicies

Read first:

Cohorte

cohorte.github.io

Microwave Motion Sensor

Making the electronics for $7 USD doppler motion sensor

Raspberry Frequency measurment

SRS - Tachymètre

Contents