Différences

Ci-dessous, les différences entre deux révisions de la page.

--- projets:ocs:20152016:gr5 [2015/11/16 20:30] – strobbe
+++ projets:ocs:20152016:gr5 [2016/02/16 18:38] (Version actuelle) – [Object Shape :] strobbe
@@ Ligne 22: / Ligne 22: @@
 ==== Object Shape : ====
-== Sketch of the Object:  ==
+== Sketch of the Object:  ==
+{{:projets:ocs:20152016:manchon_croquis.png?200|}}
 == Picture of the Object without instruments and electronics :==
+No objet received.
 == Picture of the Object with instruments and electronics outside on the same table (put some circles and arrows on the picture to show where you're going to integrate all of these) : ==
+{{:projets:ocs:20152016:img_20160209_162628.jpg?500|}}
 == Picture of the finished Object (all is integrated):  ==
+Because we did not received any box to integrate our component in it, there is no picture available.
 == Demonstration Video : ==
+[[https://www.youtube.com/playlist?list=PLx6M7kd5OPX0XGF4ifLSZhJuvBNykrIi8|Youtube playlist with all the demonstration videos (7 videos)]]
 ==== Hardware specifications : ====
@@ Ligne 65: / Ligne 73: @@
 |flexible + pommeau de douche|http://goo.gl/QpBOjT|
 ==== Specifications and interface of the service on the object  ====
-Our connected object provides information on the showers that have been taken :
+We distinguish two types of services : exposed services that allows to perform actions on the object and exposed services to gather data on the usage of the object.
-- Water temperature
+The services have been exposed through UPnP thanks to the PyUPnP library (https://github.com/fuzeman/PyUPnP)
-- Water consumption
+Here's a list of the services we expose :
-- Date and time spent in the shower, for each shower
+  * Water flow service :
-All of the information will be available through a web service.
+    GetFlowRate : Returns the water flow rate in liters/min
+  * Temperature service :
+    GetTemperature : Returns the temperature in celsius
+  * LCD service :
+    SetBackgroundColor: Set the background color of the lcd
+    SetText : Display information on the lcd
+    SetTextLine1 : Display information on the first row only
+    SetTextLine2 : Display information on the second row only
+  * TouchService
+    GetTouch : Returns a number corresponding to the button that has been pressed
+  * ActuatorService
+    OpenWater : Open or close the valve
 == Specifications ==
 Link to shared drive with Lycée des Eucalyptus : https://drive.google.com/drive/u/0/folders/0B69RH-TLSlXFZlh6d2pybHBGb1E
 ==== Specifications of the interface of high added value service ====
-Note : (including a figure on the orchestration between services on objects and information systems)
-We can imagine using a web service that provides water prices to compute how much money is spent for a shower.
+Implemented high value services :
-Using this service, we could connect to a budget management service of the user to add money spent on showers.
-Just for the sake of using the calendar service, we could after each shower, connect to the user calendar and store the shower as an event.
+- Closing the valve if the temperature goes above a certain threshold
+- Closing the valve after a certain amount of time
+- Sending emails if someone is spending too much time (meaning there could be a problem)
+- Export of a csv file containing : date of the shower, time spent, water consumption and total price
-==== Project Files: ====
-== . wcc of the two containers (embedded and on the remote PC) : ==
+A couple scenarios:
-==  Beans added for the embedded container (for the service on the object) ** (DLL and Source code for each of them) ==
+We can imagine using a web service that provides water prices to compute how much money is spent for a shower.
+Using this service, we could connect to a budget management service of the user to add money spent on showers.
-== Beans added for the remote PC container (for the high added value service on the PC) ** (DLL and Source code for each of them) ==
+Just for the sake of using the calendar service, we could after each shower, connect to the user calendar and store the shower as an event or monitor the time while in the shower to display the amount of time left based on the distance to the user workplace from google maps.
-== Chesklist to install the embedded service on the object  ==
-== Chesklist to install the remote service/application on the PC ==
+Figure on the orchestration between services on objects and information systems:
+{{:projets:ocs:20152016:des_boites_et_des_fleches.png?600|}}
+==== Project Files: ====
+All files are in the zip archive, please read the README.txt
+{{:projets:ocs:20152016:ocs_files.zip|}}
 ==== Results of the relations with Reims (being factual without personal opinion) ====
 ==== Prospects : ====
 == Possible extensions of the object ==
+An actuator to control the water flow.
+An or multiple actuators to control the temperature.
 == Possible extension of the service on the Object ==
+Put the timer as a service on the object instead as higher level service.
 == Possible extension of the high added value Service ==
-== Possible GUI for data visualization ==
+Google calendar services : we could after each shower, connect to the user calendar and store the shower as an event. At the beginning of the shower, we could connect to the calendar, check the next event and display or send a notification if there's not much time left.
+Google Maps services : We could monitor the time spent while in the shower to display the amount of time left based on the distance to the user workplace from google maps.
+Connection to other connected objects of the house
+== Possible GUI for data visualization ==
+Web app to visualize all sorts of graph : temperature, time spent, water consumption etc.