Smart Objects and Services

Project Presentation

== Name : == CoffeeMe

Group Composition :

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

Name of the contact at Reims :
Sketch of the Object from Reims :

* Sketch : https://drive.google.com/file/d/0B7dNUgETRrTmUncxQ2tNeTJGdHc/edit?usp=sharing

Picture of the Object without instruments and electronics :

* https://drive.google.com/file/d/0B7dNUgETRrTmSFp3MzdKLXh4WGM/edit?usp=sharing

Picture of the Object with instruments and electronics outside on the same table (put some circles and arrows on the picture to show where you're going to integrate all of these) :
Picture of the finished Object (all is integrated):
Demonstration Video :

* Test Video: https://drive.google.com/file/d/0B7dNUgETRrTmWGdTZnU2bUE3c09fRUtjOUxSemVFUkV2NzEw/edit?usp=sharing

Hardware specifications :

Phiget SBC 1073, thin force sensor, temperature sensor, RGB LED

List :

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 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.

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

. wcc of the two containers (embedded and on the remote PC) :

* https://drive.google.com/file/d/0B7dNUgETRrTmWkNQdXNNTWcyMlU/edit?usp=sharing

Beans added for the embedded container (for the service on the object) ** (DLL and Source code for each of them)

Source Code:

DLL :

Beans added for the remote PC container (for the high added value service on the PC) ** (DLL and Source code for each of them)

Source Code:

DLL :

Chesklist to install the embedded service on the object
Chesklist to install the remote service/application on the PC
Other source code

* CS files:

Results of the relations with Reims (being factual without personal opinion)

Prospects :

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

* Acceleration 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…