Différences

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

--- projets:ocs:20142015:gr3 [2015/01/15 14:06] – [Connected Object Description] farhat
+++ projets:ocs:20142015:gr3 [2015/02/17 11:02] (Version actuelle) – [Software Specifications and Distribution of the high level service for the user] farhat
@@ Ligne 39: / Ligne 39: @@
 [[https://drive.google.com/file/d/0B_PiKJ9bbLNXYWxXRVRua0o3Vmc/view?usp=sharing|Our tender specification proposal (WIP)]]
-Reims Proposal (WIP) this may change:
-[[https://drive.google.com/file/d/0B_PiKJ9bbLNXM3EtSTgtSWdfRTA/view?usp=sharing|Reims Students design proposal (WIP)]]
+== Reims Sketch & CAD ==
+Reims Proposal (DROPPED) :
+{{http://m.rednaks.tn/ubiquitap/sketch_reims.jpg?650x460}}
+Reims CAD (DROPPED):
+{{http://m.rednaks.tn/ubiquitap/cad1.jpg?650x365}}
+{{http://m.rednaks.tn/ubiquitap/cad2.jpg?650x365}}
+{{http://m.rednaks.tn/ubiquitap/cad3.jpg?650x365}}
+{{http://m.rednaks.tn/ubiquitap/cad4.jpg?650x365}}
 == Sketch of the object ==
+{{http://m.rednaks.tn/ubiquitap/vue_face.jpg?650x916}}
+{{http://m.rednaks.tn/ubiquitap/vue_gauche+droite.jpg?650x461}}
 // add an image of your sketch //
@@ Ligne 49: / Ligne 64: @@
 == 3D - CAD description of the object ==
+(WIP)
 // add an image 3D - CAD description (omputer-assisted conception) of the object //
 // add all the other files needed to 3D print the object //
@@ Ligne 54: / Ligne 70: @@
 == Real image of the object ==
-// add pictures of the object //
+{{http://m.rednaks.tn/ubiquitap/obj1.jpg?650x867}}
+{{http://m.rednaks.tn/ubiquitap/obj2.jpg?650x867}}
+{{http://m.rednaks.tn/ubiquitap/obj3.jpg?650x867}}
 ==== Hardware Specifications and Distribution of the connected Object ====
-// Here you must define the list of hardware in your connected Object and above all the array of the corresponding purchases (ex. main board, communication modules but also, the sensors and actuators you need//
+* Phidget
+* IR Reflective sensor
+* Solenoid valve
 == Hardware specifications ==
-// Mainly the purpose of the sensors and actuators you add on the generic hardware plateform of your object  //
+* Phidget : Is the link and the logic between all sensors and actuators.
+* IR Reflective sensor : Will be used to detect the user's hands.
+* Solenoid valve : Will be commanded by the phidget to open or close the tap.
 == Array of the purchases ==
 | Type | reseller| Reference | Quantity | unit price | link on the Web page of the product|  Total price |
-| | | | | | | |
+|Phidget SBC 1073 |gotronic |25445 | 1 |143,50€  | http://www.gotronic.fr/art-interface-8-8-8-hub-sbc1073-19807.htm|143,50€|
-| | | | | | | |
+|Adaptateur WiFi 3703_0 |gotronic |25435 |1 |34,9€ |http://www.gotronic.fr/art-adaptateur-wifi-3703-0-pour-sbc1073-12055.htm |34,9€ |
-| | | | | | | |
+|Electrovanne 12 Vcc droite EV12V | gotronic|1499 |1 |7,95 €|http://www.gotronic.fr/art-electrovanne-12-vcc-droite-ev12v-19587.htm |7,95€ |
+|capteur IR a reflexion 1103 | gotronic| 25468|1 | 10,9€| http://www.gotronic.fr/art-capteur-ir-a-reflexion-1103-12083.htm| 10,9€|
+|Bornier à vis | gotronic |31638 | 1 | 2,15€|http://www.gotronic.fr/art-bornier-a-vis-dfr0055-19305.htm | 2,15€|
 == Excel File of the purchases ==
-// put the excel file here //
+[[https://docs.google.com/spreadsheet/ccc?key=0AvPiKJ9bbLNXdFY4ZGU2c3lSd2xxZkp2WjA4dG1Oemc&usp=sharing|Purchases]]
 ==== Software Specifications and Distribution of the connected Object ====
-// BE CAREFUL : minimal logic must be embedded in the object. The main purpose of the object is to provide access to the its actuators and sensors//
 == Software Specifications of the connected Object ==
-** Web Service for Device Specifications **
+The Tap exposes 6 UPnP services :
-// add the description of the Web Service for Device interface of the connected Object //
+  * Open the Tap
+  * Close the Tap
+  * Get the Tap state
+  * Get the activity data
+  * Get the flow rate
+  * Set the flow rate (for configuration purpose)
-** Application Protocol over Bluetooth link of the object  **
-// Following to the courses of Dino Lopez and Kinan Arnaout, you'll be able this year to add a bluetooth interface for local area communications between the object and a smart phone //
-// This part must be as light as possible and the software  application under smart phone must be only a way to test, without internet,  the object functionnalities //
-// You must thus specify here a few basics instructions in bluetooth messages that you'll be able to exchange between the object and the smart phone //
-// a very simple application will be developed on the smart phone for testing (console for example, or with 4 or five textboxes)  //
 == Software Distribution of the connected Object ==
-// Here, put all the files needed to build, to compile and to deploy all your software developments//
   * Embedded Software in the connected object
     * All the instructions on what must be installed before deployment of the developed software :
-    * Binary distribution of the developed software for the object and how to install (ex. DLL of new beans and wcc of the WComp the assembly) :
+    * We created 3 new beans, contained in 2 dlls
-    * Sources distribution of the developed software  and how to build the binary distribution (ex. sources of new beans for WComp):
+      * TapBeans.dll :
-// including the list and the  links for all prerequired software //
+      * TapServices.dll : contain the UPnP services bean (UPnP.dll and NewtonJson.dll are required).
+    * We also need the container WCC : ubiquitap.wcc
-  * Mobile Phone Software
-    * The kind of  smart phone that you chose (Reference, Android ? IoS ? Windows Phone X.X ?)
-    * Binary distribution of the developed software for the phone and how to install  :
-    * Sources distribution of the developed software  and how to build the binary distribution :
-// including the list and the  links for all prerequired software //
 ==== Software Specifications and Distribution of the high level service for the user ====
-// BE CAREFUL : Here is the main purpose of your project. //
-// BE CAREFUL : The connected object is only a part of the composition/orchestration between other services to build a high level service //
-// BE CAREFUL : Don't forget that the added value and intelligence of the high level service are based on the use of multiple web services like meteo / agenda ... //
-// BE CAREFUL : The use of a user  terminal and any other Man Machine interface in order to use directly the object is not the purpose of this module //
 == Software Specifications of the High Level Service for the user ==
+For the demo we developed a web interface for the data presentation.
-// add the description of Specifications of the High Level Service for the user //
-// including the lsit of the Web Services you use to design new High Level functionalities for the user //
-// Example: use of Meteo Web Service to manage the watering of a plant equiped with a connected object //
 == Software Distribution of the High Level Service for the user ==
-// Here, put all the files needed to build, to compile and to deploy all your software developments for the high level service//
-    * All the instructions on what must be installed before deployment of the developed software (ex. software stack and WComp):
-    * Binary distribution of the developed software for the object and how to install (ex. DLL of new beans and wcc of the WComp the assembly) :
-    * Sources distribution of the developed software  and how to build the binary distribution (ex. sources of new beans in WComp):
 ==== VIDEO PICTURES and SCREENSHOTS ====