projets:ocs:20142015:gr4
Différences
Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
projets:ocs:20142015:gr4 [2015/01/12 23:41] – [MAIN INFORMATIONS about the Project] akrout | projets:ocs:20142015:gr4 [2015/02/17 00:52] (Version actuelle) – [Software Specifications and Distribution of the connected Object] akrout | ||
---|---|---|---|
Ligne 19: | Ligne 19: | ||
==== Scenario of the Project ==== | ==== Scenario of the Project ==== | ||
- | At the time when the pet is accustomed to eat,the system checks whether the bowl is empty, if it is, it sends a notification to the master that it's time to serve food to her pet. Users get the mail / SMS begins to fill the bowl, the system weighs food and point out to him by an LED that the quantity request has been reached. After the animal has finished eating, the system, connected to the internet by wifi, collects data (hours, weight consumed etc.) and saves them in a database. Then, a classification is presented to the user via our web interface. Our web interface is used to track the diet of the pet and helps the user to better control and avoid excessive problem or lack of food for the animal. | + | At the time when the pet is accustomed to eat,the system checks whether the bowl is empty, if it is, it sends a notification to the master that it's time to serve food to her pet. Users get the Email / SMS begins to fill the bowl, the system weighs food and point out to him by an LED that the quantity request has been reached. After the animal has finished eating, the system, connected to the internet by wifi, collects data (hours, weight consumed etc.) and saves them in a database. Then, a classification is presented to the user via our web interface. Our web interface is used to track the diet of the pet and helps the user to better control and avoid excessive problem or lack of food for the animal. |
Ligne 30: | Ligne 30: | ||
{{http:// | {{http:// | ||
- | ==== 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 | + | == 3D - CAD description of the object == |
+ | |||
+ | == Model (by Alexandre Schneider)== | ||
+ | {{http://s18.postimg.org/ | ||
+ | {{http:// | ||
+ | |||
+ | == Simpfied Model (be Ahmed Ghouili) == | ||
+ | |||
+ | {{http:// | ||
+ | |||
+ | == Real image of the object | ||
+ | |||
+ | {{http:// | ||
+ | |||
+ | ==== Hardware Specifications and Distribution of the connected Object ==== | ||
+ | |||
== Hardware specifications == | == Hardware specifications == | ||
- | // Mainly | + | |
+ | As the heart of our connected object, the //PhidgetSBC3 (1073_0)// is a good solution for our project. It provide enough computing power, input/ | ||
+ | |||
+ | A reflective sensor is needed to detect if the bowl is empty. We would know the dimensions of the bowl and configure | ||
+ | For the weight | ||
+ | I thought about a food reservoir, and an intelligent mechanism that serve the dog if the master is not available and the dog want to eat in a time different than he’s routine. The system could listen to the dog by a // microphone // and if he insist the system allow him some food. It can be totally configurable t the user. | ||
+ | |||
+ | {{http:// | ||
+ | {{http:// | ||
+ | {{http:// | ||
+ | {{http:// | ||
+ | {{http:// | ||
== Array of the purchases == | == Array of the purchases == | ||
| Type | reseller| Reference | Quantity | unit price | link on the Web page of the product| | | Type | reseller| Reference | Quantity | unit price | link on the Web page of the product| | ||
- | | | | | | | | | | + | | iGamelle |
- | | | | | | | | | | + | | iGamelle |
- | | | | | | | | | | + | | iGamelle |
+ | | iGamelle | Lextronic| BOB-09964 | 1 | 5.95€ | http:// | ||
== Excel File of the purchases == | == Excel File of the purchases == | ||
- | // put the excel file here // | + | [[https://www.dropbox.com/s/n1knchrrcdzrkf8/ |
==== Software Specifications and Distribution of the connected Object ==== | ==== 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 == | == Software Specifications of the connected Object == | ||
- | ** Web Service for Device Specifications ** | ||
- | // add the description of the Web Service for Device interface of the connected Object // | ||
- | ** Application Protocol over Bluetooth link of the object | + | The device inteface |
- | // 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 | ||
- | |||
- | // 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 == | == 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 | + | https://www.dropbox.com/sh/ovmkskjjmath4sx/AADVWXqfOwIvmTsEo0Y3IXqEa?dl=0 |
- | * 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 | + | |
- | // including the list and the links for all prerequired software | + | |
- | + | ||
- | * Mobile Phone Software | + | |
- | * The kind of smart phone that you chose (Reference, Android | + | |
- | * Binary distribution of the developed software for the phone and how to install | + | |
- | * Sources distribution of the developed software | + | |
- | // including the list and the links for all prerequired software // | + | |
- | ==== Software Specifications | + | The distance |
+ | The same for the connection Bean. | ||
- | // BE CAREFUL : Here is the main purpose of your project. // | + | the prototype conteiner needs to be exported to a .wcc file and tranfered to the board. |
- | // BE CAREFUL : The connected object is only a part of the composition/ | + | #mono ContainerMonoLinux.exe -r ./Beans -l ./iGamelle/Appli3.wcc -n Application -p 3900 |
- | // 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 ... // | + | == Prerequires == |
- | // BE CAREFUL | + | Mono : http://www.mono-project.com/ (apt-get install mono windows-form*) |
+ | SharpDevelop : http:// | ||
- | == Software Specifications of the High Level Service for the user == | + | Wcomp: http:// |
- | // add the description of Specifications of the High Level Service for the user // | + | Mysql Server : http://www.mysql.com/ |
- | // 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 | |
- | == Software Distribution of the High Level Service | + | |
- | // 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 | ||
+ | The high level service for the user is the ability to follow the pets nutrition. It's can help avoid undernourishment, | ||
==== VIDEO PICTURES and SCREENSHOTS ==== | ==== VIDEO PICTURES and SCREENSHOTS ==== | ||
- | // Here put all that can illustrate the results of your project with .. // | + | VIDEO for demonstrations : https://www.youtube.com/watch? |
+ | |||
+ | https:// | ||
- | // VIDEO for demonstrations // | + | Screenshot : |
- | // PICTURES of the object looking like a finished one // | + | {{http://s1.postimg.org/q9v4q9wlr/Untitled.png? |
- | // SCREENSHOTS of sofware applications and developments | + | {{http://s18.postimg.org/xjvz4jpbd/servicebuilder.png? |
==== INSTRUCTIONS AND REMINDERS ==== | ==== INSTRUCTIONS AND REMINDERS ==== |
projets/ocs/20142015/gr4.1421106111.txt.gz · Dernière modification : 2015/01/12 23:41 de akrout