Différences

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

--- projets:oc:oc_2013_2014:coffeeme [2014/02/20 21:36] – [Specifications of the interface of high added value service] etudiant_oc_2013_2014
+++ projets:oc:oc_2013_2014:coffeeme [2014/02/20 22:01] (Version actuelle) – [Project Files:] etudiant_oc_2013_2014
@@ Ligne 11: / Ligne 11: @@
 ==== Scenario :====
-* The user fills the Thermos with hot liquid. It will detect the presence of liquid and the change in volume via the thin force sensor, the temperature sensor will determin if the liquid is in the right temperature, it will send it’s values to the remote PC container which will accordingly light up the right led. The object will store the volumes drunk from the recipient in a file sent to the computer with a time stamp, in order to determine the frequency of consumption and the volume consumed and or if there are any unusual activity(consumption at odd hours)
+* The user fills the Thermos with hot liquid. It will detect the presence of liquid and the change in volume via the thin force sensor, the temperature sensor will determin if the liquid is in the right temperature, it will send its values to the remote PC container which will accordingly light up the right led. The object will store the volumes drunk from the recipient in a file sent to the computer with a time stamp, in order to determine the frequency of consumption and the volume consumed and or if there are any unusual activities(consumption at odd hours)
 ==== Object Shape : ====
  * The object is shaped as a Thermos containing hot liquid. It is black, cylindrical, with a hand grip on the side all along the object height
@@ Ligne 35: / Ligne 35: @@
 ==== Specifications and interface of the service on the object  ====
- * In the board there is a bean just after the thin force sensor that saves the date if the sensor detects an non empty Thermos. This bean is followed by a second one that captures force values every 5 seconds and compares them with the current value and sends it to the UPnP probe with the date and the thermos state (empty or not)
+ * In the board there is a bean just after the thin force sensor that saves the date if the sensor detects a non empty Thermos. This bean is followed by a second one that captures force values every 5 seconds and compares them to the current value and sends it to the UPnP probe with the date and the thermos state (empty or not)
  * The Thermos state and the Temperature are sent to the services in the PC for further treatment.
- * https://drive.google.com/file/d/0B7dNUgETRrTmd0xrUTU4c1Q5N2c/edit?usp=sharing
+ * Pressure Treatment: https://drive.google.com/file/d/0B7dNUgETRrTma2JydWhJZ3p0MmM/edit?usp=sharing
+ * Temperature Treatment: https://drive.google.com/file/d/0B7dNUgETRrTmbEk1NklGUkItVVE/edit?usp=sharing
 ==== Specifications of the interface of high added value service ====
  * The High added value services are mostly represented by the beans on the PC and one in the board.
-Two beans will receive information via an UPnP proxy pointing on the UPnP probes on the board, one will fill the log file with information extracted from the incoming events,the other one will determine which LED color to turn on by sending the port to activate(or deactivate) and the new state.
+Two beans will receive information via an UPnP proxy pointing on the UPnP probes of the board, one will fill the log file with information extracted from the incoming events,the other one will determine which LED color to turn on by sending the port to activate(or deactivate) and the new state.
  * The High added value here resides in the remote processing of any information captured, and the remote control of some actuator. The log file is Date-stamped and the data is parsed.
- * A final bean is the board, it has an UPnP proxy that receives values from the UPnP probes on the PC and changes the output ports in order to get the right color for the right temperature.
+ * A final bean is in the board, it has an UPnP proxy that receives values from the UPnP probes on the PC and changes the output ports' states in order to get the right color for the right temperature.
- * Beans on the computer : https://drive.google.com/file/d/0B7dNUgETRrTmUUN3NEV3azdJaWM/edit?usp=sharing
+ * Beans on the PC : https://drive.google.com/file/d/0B7dNUgETRrTmUUN3NEV3azdJaWM/edit?usp=sharing
+ * Last UPnP proxy: https://drive.google.com/file/d/0B7dNUgETRrTmd3JFbTk0Q0xoRHM/edit?usp=sharing
 ==== Project Files: ====
@@ Ligne 75: / Ligne 79: @@
 == Chesklist to install the remote service/application on the PC ==
+== Other source code ==
+ * CS files:
+   * ProjetPhidget.cs : https://drive.google.com/file/d/0B7dNUgETRrTmSDNRN2NEeC1TU3c/edit?usp=sharing
+   * Traitement UPnP : https://drive.google.com/file/d/0B7dNUgETRrTmbTV6Y1F0SGhaRmc/edit?usp=sharing
 ==== Results of the relations with Reims (being factual without personal opinion) ====
@@ Ligne 80: / Ligne 90: @@
 == Possible extensions of the object ==
 * The object can detect hand shaking via an accelerometer to determine the stress level of the user.
 * It can integrate a GPS module to determine the position of the thermos(home, work, car..) and by doing that it can offer better statistics of the consumption.
 == Possible extension of the service on the Object ==
-* Position Detection Bean
+* Acceleration Detection Bean
-* Location detection Bean
+* Location Detection Bean
 == Possible extension of the high added value Service ==
 * Connection to several web services such as weather services to determine the temperature and compare it to the one of the liquid and offer better consumption statistics.
 * Connection to other communicating objects such as a coffee maker to tell them whether it needs refilling...
 == Possible GUI for data visualization ==
 * A possible GUI would be an interface offering statistics graphs and consumption evolution according to the weather, the season, and the time of day...