Difference between revisions of "SRS - Tachymètre"
Jump to navigation
Jump to search
Regis.Ramel (talk | contribs) |
Regis.Ramel (talk | contribs) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 71: | Line 71: | ||
: Getting of physical values : speed and distance |
: Getting of physical values : speed and distance |
||
: Sending of processed data by consuming a service provided by a remote component. |
: Sending of processed data by consuming a service provided by a remote component. |
||
− | |||
'''Aggregation function''' |
'''Aggregation function''' |
||
: Storage of the data in a server. |
: Storage of the data in a server. |
||
− | |||
'''User interface function''' |
'''User interface function''' |
||
Line 82: | Line 80: | ||
== Non-functional requirements == |
== Non-functional requirements == |
||
'''Quality of the network''' |
'''Quality of the network''' |
||
+ | : Store the data on the device allows to avoid losing data in the event of link loss. |
||
− | : Une solution de stockage des mesures dans le cache du Raspberry permet de prévenir la perte des données en cas d'indisponibilité du réseau. |
||
− | ''' |
+ | '''Sensor environment''' |
+ | : The measurements have to be filtred to eliminate the noise generate by the environment (street, wind, …). |
||
− | : Il est nécessaire de traiter les mesures pour ne pas tenir compte du bruit dû à l'environnement. |
||
− | == |
+ | == Interface requirements == |
+ | : Compatibility multi-platform (different browser, mobile version of the software). |
||
− | '''Ergonomie''' |
||
+ | : Interactivity (date range selection, creation of graphs, …). |
||
− | : Compatibilité multi-support (différents navigateurs, version mobile). |
||
− | : Interactions (sélection de plage de dates, affichage de graphiques, …). |
||
− | : Nécessité de transparence pour l'utilisateur. |
||
− | = |
+ | = Use case = |
− | == Interaction |
+ | == Interaction between user and web interface == |
+ | : - The user connects to the website and authenticate with his loin and password |
||
− | : - L’utilisateur entre sur le site web et s’authentifie avec un login et un mot de passe |
||
+ | : - The user can choose to click on “all” to display all the data from every sensors (sorted in descending order of date) |
||
− | : - 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) |
||
+ | :: Data displayed : date, average speed, maximum speed, direction, sensor |
||
− | :: -la date / vitesse moyenne / sens / capteur |
||
+ | : - The user choose a sensor in the sensor list (green : connected, red : disconnected) |
||
− | : - L’utilisateur choisit un capteur parmi la liste des capteurs installés (vert : connecté, rouge : déconnecté) : |
||
− | :: - |
+ | :: - Processed data tab : |
+ | ::: - The system displays the processed data in a table (sorted in descending order of date) |
||
− | ::: -le système affiche les données élaborées dans un tableau (triées par date décroissante) |
||
+ | :::: Data displayed : date, average speed, maximum speed, direction, sensor |
||
− | :::: - la date (Heure / Minute / Jour / Mois / Année) / vitesse moyenne (km/h) / sens (sens du capteur, contresens du capteur) |
||
− | ::: - |
+ | ::: - The user can click on pagination links to browse the data. |
+ | ::: - The user can filtrate the data with two types of parameters : |
||
− | ::: - L’utilisateur peut filtrer les données affichées en fonction des paramètres suivants : |
||
− | :::: - |
+ | :::: - Between two dates |
− | :::: - |
+ | :::: - A minimum / maximum speed value |
− | :: - |
+ | :: - Synthetic data tab : |
+ | ::: - The user can make parameterized analyses choosing the option “historic”, or a distribution choosing the option “distribution. The parameters are : |
||
− | ::: - L'utilisateur peut obtenir des analyses paramétrées des données élaborées en choisissant l'option "historique" en fontion de : |
||
− | :::: - |
+ | :::: - Selection of the type of data : |
− | ::::: - |
+ | ::::: - Number of moves |
− | ::::: - |
+ | ::::: - Average speed |
− | ::::: - |
+ | ::::: - Maximum speed |
− | :::: - |
+ | :::: - Selection of a date range : |
− | ::::: - |
+ | ::::: - Start date (DD/MM/YYYY) |
− | ::::: - |
+ | ::::: - End date (DD/MM/YYYY) |
− | :::: - |
+ | :::: - Selection of time slot : |
− | ::::: - |
+ | ::::: - Start hour (HH/MM) |
− | ::::: - |
+ | ::::: - End hour (HH/MM) |
+ | :: - Administration tab : |
||
− | ::: - L'utilisateur peut également obtenir une répartition des vitesses de passage en choisissant l'option "répartition" en fonction de : |
||
+ | ::: - The system displays events related to the selected sensor in a table (sorted in descending order of date) : |
||
− | :: - onglet administrateur : |
||
+ | :::: - Selection of a date range : |
||
− | ::: - le système affiche un tableau des événements relatifs au capteur sélectionné (trié par date décroissante) : |
||
− | :::: - |
+ | ::::: - Start date (DD/MM/YYYY) |
− | ::::: - |
+ | ::::: - End date (DD/MM/YYYY) |
− | + | :::: - Selection of time slot : |
|
− | :::: - |
+ | ::::: - Start hour (HH/MM) |
− | ::::: - |
+ | ::::: - End hour (HH/MM) |
− | + | :::: - Date of event (HH/MM/DD/MM/YYYY) |
|
− | :::: - |
+ | :::: - State of the sensor (connected / disconnected) |
+ | : - The user can disconnect |
||
− | :::: - l’état (connecté, déconnecté) |
||
− | : - L’utilisateur peut se déconnecter |
||
== Interaction du technicien avec le capteur == |
== Interaction du technicien avec le capteur == |
||
Line 136: | Line 131: | ||
: - Le technicien démarre le capteur |
: - Le technicien démarre le capteur |
||
− | == Interaction |
+ | == Interaction between the technician and the sensor == |
+ | : - The technician connects the sensor to the client’s internet network |
||
− | : - Le technicien ouvre la page d’administration du capteur |
||
+ | : - The technician fill a form on the Raspberry : |
||
− | : - Le technicien remplit un formulaire : |
||
− | :: - |
+ | :: - Identifier of the sensor |
− | :: - |
+ | :: - GPS coordinates of the sensor (latitude, longitude, altitude) |
= Appendicies = |
= Appendicies = |
Latest revision as of 14:53, 30 March 2016
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, …).
Use case
Interaction between user and web interface
- - The user connects to the website and authenticate with his loin and password
- - The user can choose to click on “all” to display all the data from every sensors (sorted in descending order of date)
- Data displayed : date, average speed, maximum speed, direction, sensor
- - The user choose a sensor in the sensor list (green : connected, red : disconnected)
- - Processed data tab :
- - The system displays the processed data in a table (sorted in descending order of date)
- Data displayed : date, average speed, maximum speed, direction, sensor
- - The user can click on pagination links to browse the data.
- - The user can filtrate the data with two types of parameters :
- - Between two dates
- - A minimum / maximum speed value
- - The system displays the processed data in a table (sorted in descending order of date)
- - Synthetic data tab :
- - The user can make parameterized analyses choosing the option “historic”, or a distribution choosing the option “distribution. The parameters are :
- - Selection of the type of data :
- - Number of moves
- - Average speed
- - Maximum speed
- - Selection of a date range :
- - Start date (DD/MM/YYYY)
- - End date (DD/MM/YYYY)
- - Selection of time slot :
- - Start hour (HH/MM)
- - End hour (HH/MM)
- - Selection of the type of data :
- - The user can make parameterized analyses choosing the option “historic”, or a distribution choosing the option “distribution. The parameters are :
- - Administration tab :
- - The system displays events related to the selected sensor in a table (sorted in descending order of date) :
- - Selection of a date range :
- - Start date (DD/MM/YYYY)
- - End date (DD/MM/YYYY)
- - Selection of time slot :
- - Start hour (HH/MM)
- - End hour (HH/MM)
- - Date of event (HH/MM/DD/MM/YYYY)
- - State of the sensor (connected / disconnected)
- - Selection of a date range :
- - The system displays events related to the selected sensor in a table (sorted in descending order of date) :
- - Processed data tab :
- - The user can disconnect
Interaction du technicien avec le capteur
- - Le technicien branche le capteur au réseau internet du client
- - Le technicien démarre le capteur
Interaction between the technician and the sensor
- - The technician connects the sensor to the client’s internet network
- - The technician fill a form on the Raspberry :
- - Identifier of the sensor
- - GPS coordinates of the sensor (latitude, longitude, altitude)
Appendicies
Read first:
- http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
- http://en.wikipedia.org/wiki/Software_requirements_specification
- IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998
Cohorte
- cohorte.github.io
Microwave Motion Sensor
- https://www.openimpulse.com/blog/wp-content/uploads/wpsc/downloadables/HB100_Microwave_Sensor_Module_Datasheet.pdf
- https://www.openimpulse.com/blog/wp-content/uploads/wpsc/downloadables/HB100_Microwave_Sensor_Application_Note.pdf
Making the electronics for $7 USD doppler motion sensor
- http://ch.linkedin.com/in/mathieustephan
- http://www.limpkin.fr/index.php?post/2013/08/09/Making-the-electronics-for-a-%247-USD-doppler-motion-sensor
- https://docs.google.com/document/d/1CVdH3UVTROaJ4_Bgsx_-hyg5_LvoNxYiB13pPRN9gzU/edit
Raspberry Frequency measurment
- http://raspberrypi.stackexchange.com/questions/26166/count-rpm-frequency-pulses-on-gpio-ports-maximum
- http://blog.durablescope.com/2015/03/build-speed-camera-and-traffic-logger.html
- http://abyz.co.uk/rpi/pigpio/examples.html#C_code
- https://www.raspberrypi.org/forums/viewtopic.php?f=37&t=97795
- http://raspberrypi.stackexchange.com/questions/24812/measuring-frequency-via-gpio
- http://hacker.instanet.net/forums/viewtopic.php?f=4&t=104