Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentes Révision précédente Prochaine révision | Révision précédente | ||
projets:oc:oc_2013_2014:analyse_ph_express [2014/02/19 03:14] etudiant_oc_2013_2014 [Results of the relations with Reims (being factual without personal opinion)] |
projets:oc:oc_2013_2014:analyse_ph_express [2014/02/20 19:11] (Version actuelle) etudiant_oc_2013_2014 [Object Shape :] |
||
---|---|---|---|
Ligne 38: | Ligne 38: | ||
== Demonstration Video : == | == Demonstration Video : == | ||
+ | * [[https://www.youtube.com/watch?v=cD2fDQk70BU&feature=youtu.be|Watch Demo Online on Youtube]] | ||
+ | * [[https://www.dropbox.com/s/4xeza1thgdsfads/Demo%20Anaylse_pH_Express.wmv|Download Demo]] | ||
==== Hardware specifications: ==== | ==== Hardware specifications: ==== | ||
Ligne 75: | Ligne 77: | ||
== . wcc of the two containers (embedded and on the remote PC) : == | == . wcc of the two containers (embedded and on the remote PC) : == | ||
+ | * [[https://www.dropbox.com/s/clt02xpxq6f0i3l/Analyse_pH_Express_SBC.wcc|Embedded Container]] | ||
+ | * [[https://www.dropbox.com/s/m6ayg0ownac9fpk/Analyse_pH_Express_PC.wcc|Remote Container]] | ||
== Beans added for the embedded container (for the service on the object) ** (DLL and Source code for each of them) == | == Beans added for the embedded container (for the service on the object) ** (DLL and Source code for each of them) == | ||
+ | * [[https://www.dropbox.com/s/zuni0sp4m9dsr2k/Embedded%20Bean%20DLL.zip|Embedded Bean DLL]] | ||
+ | * [[https://www.dropbox.com/s/hd8qgxqeitzv8bb/Embedded%20Bean%20Source%20Code.zip|Embedded Bean Source Code]] | ||
== Beans added for the remote PC container (for the high added value service on the PC) ** (DLL and Source code for each of them) == | == Beans added for the remote PC container (for the high added value service on the PC) ** (DLL and Source code for each of them) == | ||
+ | * [[https://www.dropbox.com/s/k0ge9qa7u3x5ph2/Remote%20Bean%20DLL.zip|Remote Bean DLL]] | ||
+ | * [[https://www.dropbox.com/s/2wh4yqwtyysgri5/Remote%20Bean%20Source%20Code.zip|Remote Bean Source Code]] | ||
== Chesklist to install the embedded service on the object == | == Chesklist to install the embedded service on the object == | ||
+ | * Make sure SharpDevelop (as well as WComp add-on), Phidget Control Pannel, WinSCP, PuTTY and Device Spy are all installed | ||
+ | * Copy all beans (DLL files) into the folder Beans inside the folder where SharpDevelop is installed | ||
+ | * Power on Phidgets and connect it to the Ethernet wire of the PC | ||
+ | * Configure WiFi connection with the help of Phidget Control Pannel then unplug Ethernet Connection (this won’t be needed anymore) | ||
+ | * Open WinSCP and connect to the Phidget by using the IP address and the appropriate username and password. (File protocol: SCP) | ||
+ | * Copy all .wcc and .dll files on the phidget | ||
+ | * Open session in PuTTY then type the appropriate password | ||
+ | * Launch the service : mono Container.exe –r ../Beans –l Analyse_pH_Express_SBC.wcc –n Analyse_pH_Express | ||
+ | * You can now see Analyse_pH_Express in Device Spy with the 2 probes (Threshold & pH sensor values) | ||
== Chesklist to install the remote service/application on the PC == | == Chesklist to install the remote service/application on the PC == | ||
+ | * Open Device Spy and copy the Device URL | ||
+ | * Open SharpDevelop and create a new C# Container | ||
+ | * Import Analyse_pH_Express_PC.wcc | ||
+ | * Modify the UPnP Device URL with the copied with one (should become green now) | ||
+ | * Subscribe to Events if you wish to view pH Values through Device Spy | ||
+ | * Open the generated XML Log named "Analyse_pH_Express_Report.xml" found in the folder where SharpDevelop is installed | ||
==== Results of the relations with Reims (being factual without personal opinion) ==== | ==== Results of the relations with Reims (being factual without personal opinion) ==== | ||
We can't really offer any positive/negative feedback since we were in another country (in Egypt). The only interaction we had was when we were asked to deliver a Description of Work. Then we got a positive feedback from him indicating that the document contains all required information and the object could be manufactured without any problems. | We can't really offer any positive/negative feedback since we were in another country (in Egypt). The only interaction we had was when we were asked to deliver a Description of Work. Then we got a positive feedback from him indicating that the document contains all required information and the object could be manufactured without any problems. | ||
Ligne 89: | Ligne 111: | ||
==== Prospects : ==== | ==== Prospects : ==== | ||
== Possible extensions of the object == | == Possible extensions of the object == | ||
+ | * User's Temperature Detection could also be interesting to analyse for medical purposes. | ||
+ | * Room's Temperature Detection could also be used for activating a seat warmer mechanism. | ||
+ | * Room's Light Detection could also be added for activating light glowing figures on the object to improve user's vision. | ||
== Possible extension of the service on the Object == | == Possible extension of the service on the Object == | ||
+ | * Adding an internal Log that guarantees persistence | ||
+ | * Adding Temperature/Light sensors | ||
+ | * Adding Vibration sensor to enhance the detection of usage | ||
== Possible extension of the high added value Service == | == Possible extension of the high added value Service == | ||
+ | * Using Google Calendar for detecting the holidays which influence the food/drinks consumed by the user. Therefore, it could affect the urine's pH. | ||
+ | * Comparing csv logs with current xml ones to determine which is most suitable. | ||
== Possible GUI for data visualization == | == Possible GUI for data visualization == | ||
+ | * A graph that illustrates the user's pH evolution during the day/week/month. |