JY Tigli Homepages

Cette page est en lecture seule. Vous pouvez afficher le texte source, mais ne pourrez pas le modifier. Contactez votre administrateur si vous pensez qu'il s'agit d'une erreur.
====== Projets Objets Connectés et Services (OCS) ======

==== Title of the Project : Alarm Light ====



==== GROUP GR8 ====

==== MAIN INFORMATIONS about the Project ====

=== MEMBERS ===

    * Rocher
    * Gérald 
    * M2 IFI/IAM 
    * rocher.gerald@gmx.fr
    * Palma
    * Adam 
    * M2 IFI/IAM 
    * palma.adam@etu.unice.fr



==== Scenarios of the Project ====

The //object// exposes a very simple interface allowing to switch on/off a lamp and a buzzer. The interface allows also getting the state of each of them.

Some usage scenarios are depicted here below:

 === 1. AlarmLight application ===
The primary purpose of the //object// is to wake-up user at the right time! So, on top of this simple interface is built an application (using WComp for fast prototyping) permitting the following scenarios:
	
1) Bob fell asleep late yesterday evening and he's got an appointment quite early this morning. However he didn't take care of his alarm clock : the application, from Bob's calendar web service (Google agenda, but it could be any other similar web service), knows at what time Bob need to be waken up.
    
2) Also, the application is connected to a live traffic web service. From Bob's position and the meeting location (metadata added by Bob in his agenda) it will get the expected travel time needed by Bob to reach his appointment. The application dynamically adapts the hour at which Bob need to be waken up (the lamp and the buzzer have to be switched on).
   
3) When it's time to wake-up, the lamp and a buzzer are switched on in order to wake up Bob. Once waked-up, Bob deactivate the light and the buzzer sound emission by touching the object.

4) Of course, Bob can still switch on the lamp embedded in the //object// as soon as he want by touching it (and by touching it again to switch it off). 

=== 2. The object as a service in an orchestration ===

The //object// proposes services that are used in our application but it can also be interesting to make the services available for some other applications. For instance, we could imagine some smoke or temperature sensors located somewhere in Bob's house. We can imagine an application which connect the sensors output to the //object// buzzer and/or lamp through a threshold and switch it on when sensors reaches some unexpected values...

Actually there are plenty of applications that can use our simple buzzer and light and divert from the primary //object// usage. 

==== Connected Object Description (Nice students proposal) ====
== Specification ==
https://drive.google.com/file/d/0B6t-5TDyw60hT0V1VXB4SElKOW8/view?usp=sharing
== Sketch of the object ==

Perspective view:

[[https://www.flickr.com/photos/129285131@N04/15135637334/]]

Front module view:

[[https://www.flickr.com/photos/129285131@N04/15570182078/]]

Back module view:

[[https://www.flickr.com/photos/129285131@N04/15570447477/]]

Electronic components chassis view:

[[https://www.flickr.com/photos/129285131@N04/15771941406/]]
[[https://www.flickr.com/photos/129285131@N04/15610204938/]]


==== Hardware Specifications and Distribution of the connected Object ====

We have decided to embed a 8W LED lamp in //the object// as it doesn't heat-up too much (50dC). Lamp switch on/off control is done using a dual relays board controlled by the phidgets SBC.
User action on the //object// is detected thanks to a sensitive sensor located inside the //object// on the edge of one of its sides.
Sound emission will be achieved by a buzzer wired to one of the digital output of the phidgets SBC (We still have to ensure the current driven by the output (20mA given but it might be much lower...) will be high enough for the selected buzzer (given to work with 20mA current)). 

== Hardware specifications ==

The sensitive sensor will be used by the user to switch on/off the lamp or to acknowledge wake-up.
The Buzzer is used to emit a sound in case the user do not acknowledge wake-up after the lamp has been switched-on. 

== Array of the purchases ==

| Type | reseller| Reference | Quantity | unit price | link on the Web page of the product|  Total price |
|Interface 8/8/8 + hub SBC1073| gotronic | 25445 | 1 | 143.50 € | http://www.gotronic.fr/art-interface-8-8-8-hub-sbc1073-19807.htm | 143.50 € | 
|Capteur sensitif 1129_1| gotronic| 25488 | 1 | 10.45 € | http://www.gotronic.fr/art-capteur-sensitif-1129-1-12103.htm | 10.45 € |
|Adaptateur WiFi 3703_0 | gotronic | 25435 | 1 | 34.90€ | http://www.gotronic.fr/art-adaptateur-wifi-3703-0-pour-sbc1073-12055.htm | 34.90€ |
|Ampoule Led "standard" 8W - 230VAC (E27) | Lextronic | LAL1K3C | 1 | 17.90 € | http://www.lextronic.fr/P30082-ampoule-led-standard-8w---230vac-e27.html | 17.90 € |
|Douille e27 ca noire| lextronic | ACLS5 | 1 |  | http://www.lextronic.fr/P22409-douille-ca-e27-noir.html | |
|Carte 2 relays 3051| gotronic | 25495 | 1 | 17.60 € | http://www.gotronic.fr/art-carte-a-2-relais-3051-12110.htm | 17.60 € |
|Buzzer SVM06| gotronic | 05480 | 1 | 1.80 € | http://www.gotronic.fr/art-buzzer-svm06-3844.htm | 1.80 € |
| Entretoise F/F 5mm BFF05 | gotronic | 11560 | 8 | 0.15 € | http://www.gotronic.fr/art-entretoise-f-f-5mm-bff05-6531.htm | 1.20 € |
| Vis M3 | - | - | 16 | - | Length unknown for the time being... | - |
| Adaptateur USB/Bluetooth | - | - | 1 | - | - |
| TOTAL | | | | | | 227.35€ |


== Excel File of the purchases ==
https://www.dropbox.com/s/f0qqythjyc0sdx4/Commande_AlarmLight.xlsx?dl=1
==== Reims university team designs proposal ====

Here bellow are two designs proposed by Reims university team. 
 
== Light pillow ==
[[https://drive.google.com/file/d/0B6t-5TDyw60hWHNiX0F3TFZQYW8/view?usp=sharing|lightPillow.pdf]]

== Design based on our first proposal ==
[[https://drive.google.com/file/d/0B6t-5TDyw60hVGlPUWtydEgwRVk/view?usp=sharing|AlarmLight.pdf]]

==== Reims university team ** FINAL ** design ====
=== 3D - CAD description of the object ===
== Back module ==
https://flic.kr/p/pMiskb
== Back module with electronics components ==
https://flic.kr/p/qJej6G
== Front module ==
https://flic.kr/p/qG1JaL
== Front + Back modules ==
https://flic.kr/p/qrRzxR

=== Real image of the object ===

Manufacturing has been started on January 08 2015. Pictures to come soon...
==== Software Specifications and Distribution of the connected Object ====

== Overview ==

{{http://image.noelshack.com/fichiers/2015/08/1424249546-16374577289-5827311736-o.png?600x150}}

== Software Specifications of the connected Object ==

** Web Service for Device Specifications **

 The main purpose of the object is to give acces to its services through UPnP protocol. In our case, the UPnP services are :
	- Turning on and off the light.
	- Turning on and off the alarm. 
	- The current State of the light.
	- The current State of the alarm.
 
 In addition of the above, the object owns a physical interface which consists of a touch sensor. This embedded actuator provide the following features:
	- If the alarm is turned off, each pressure alternately switch on and off the light with each pressure.
	- If the alarm and light are on, the next pressure turns off the alarm without switching off the light.
	- If the alarm is on and the light is off, the next pressure turns off the alarm and switch on the light. 


** 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) :
    * Sources distribution of the developed software  and how to build the binary distribution (ex. sources of new beans for WComp):
// including the list and the  links for all prerequired software //

wcc of the embedded software:

 [[https://drive.google.com/open?id=0ByF5Pdi4nQlASDNuVUhGU3k3OUU&authuser=0]]

Beans to install in Bean/ directory in the embedded device

 [[https://drive.google.com/open?id=0ByF5Pdi4nQlAVEVBMEFfS1VRYlU&authuser=0]]

Sources of the embedded Beans:

 [[https://drive.google.com/open?id=0ByF5Pdi4nQlASzdfd1RCcWJaLU0&authuser=0]]


  * 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 ====


== Software Specifications of the High Level Service for the user ==

The high level service orchestrates the three following WebServices :
	* Calendar WebService, in our case, Google Calendar. This service is used to know the time of the first user appointement in the morning.
	* LiveMap WebService, 
 
== 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):

wcc of the orchestration software :

https://drive.google.com/open?id=0ByF5Pdi4nQlAYVExbEZ6RFNUek0&authuser=0

bridge application for the Google Calendar WebService:

https://drive.google.com/file/d/0ByF5Pdi4nQlAb2QwUUM1QTFnQ0k/view?usp=sharing

Beans to add in Bean/ directory: 

https://drive.google.com/file/d/0ByF5Pdi4nQlAcDdjOXZzakVLQnM/view?usp=sharing

Sources of the Beans :

https://drive.google.com/file/d/0ByF5Pdi4nQlAYVBGOGNvU0ppMnM/view?usp=sharing



==== VIDEO PICTURES and SCREENSHOTS ====

// Here put all that can illustrate the results of your project with .. //

// VIDEO for demonstrations //

// PICTURES of the object looking like a finished one //

// SCREENSHOTS of sofware applications and developments // 

==== INSTRUCTIONS AND REMINDERS ====

== INSTRUCTIONS : ==

  - //  Warning : everything must be written in english ....// 
  - // Warning : every added file (ex. figures, picture, sources, binaries, video ...) must be added through a web links on a Web repository. You can use such a syntax to integrate the link in this page :// <code> [[http://example.com|Lien externe]] </code>
  - //For more informations on DokuWiki syntax go to// [[https://www.tigli.fr/doku.php?id=wiki:syntax|syntax dokuwiki]]