Domoverse platform

From Tmplab

(Difference between revisions)
Jump to: navigation, search
m (Resources)
Current revision (02:01, 15 June 2008) (edit) (undo)
m (Project organization)
 
(3 intermediate revisions not shown.)
Line 7: Line 7:
= Project organization =
= Project organization =
-
# State of the art: metaverse platforms and domotics management systems
+
# [Current] State of the art: metaverse platforms and domotics management systems
# Evaluation of metaverse and domotics management systems candidates
# Evaluation of metaverse and domotics management systems candidates
# Implementation of a tmplab server for experimentation
# Implementation of a tmplab server for experimentation
Line 13: Line 13:
# Implementation of XMLRPC-like server for services exposition (X10, ...)
# Implementation of XMLRPC-like server for services exposition (X10, ...)
# Linking virtual objects' actions to XMLRPC calls
# Linking virtual objects' actions to XMLRPC calls
-
# Gluing all together
+
# Gluing all together for first prototype
 +
# Hardware integration on low-consumption devices (WRT?)
= Components =
= Components =
-
* XMLRPC server:
+
* XML-RPC server:
-
** keeps a list of all detected devices and features
+
** keeps a list of all detected automation-related devices
-
** exposes their functionality trough the remote procedure call interface
+
** gives access to underlying features
-
** hosts a 3D modelization of controlled items
+
** serves cross-world 3D models of real-life controlled items (e.g. light bulb, displays, ...)
* device_connectors: protocol-specific plugins
* device_connectors: protocol-specific plugins
-
** X10 devices exploitation
+
** X10
** ZigBee
** ZigBee
** Z-Wave
** Z-Wave
-
* metaverse_connectors: metaverse-specific components (speaks with metaverse server)
+
* cross-world 3D models, scripting templates and coding resources
-
* metaverse objects and scripting codebases and snippets, domoverse-related templates and coding resources
+
* world-specific interfacing modules
 +
 
 +
Ultimately, all device-specific information should reside in the devices themselves and answear to requests directly.
= Resources =
= Resources =
Line 32: Line 35:
* http://del.icio.us/fthiery/domoverse
* http://del.icio.us/fthiery/domoverse
* [http://community.webbricksystems.com/files/folders/manuals/entry15.aspx WebBrickSystems API example]
* [http://community.webbricksystems.com/files/folders/manuals/entry15.aspx WebBrickSystems API example]
-
* [http://www.automatedhome.co.uk/New-Products/LinuxMCE-710-An-Overview.html LinuxMCE] supports various home automation protocols
+
* [http://www.automatedhome.co.uk/New-Products/LinuxMCE-710-An-Overview.html LinuxMCE] supports [http://wiki.linuxmce.org/index.php/Category:Automation various home automation protocols]

Current revision

Contents

Description

This page is intended as placeholder for preparing the Domoverse platform project.

It is a project whose aim is to explore the HMI capabilities of Metaverse-related technologies (OpenSim/OpenLife/OpenCroquet/Solipsis) in a domotics context (X10/Z-Wave, Gumstix, ZigBee...), as home server control and root web house.

Project organization

  1. [Current] State of the art: metaverse platforms and domotics management systems
  2. Evaluation of metaverse and domotics management systems candidates
  3. Implementation of a tmplab server for experimentation
  4. 3D Replication of the lab and it's electronic devices
  5. Implementation of XMLRPC-like server for services exposition (X10, ...)
  6. Linking virtual objects' actions to XMLRPC calls
  7. Gluing all together for first prototype
  8. Hardware integration on low-consumption devices (WRT?)

Components

  • XML-RPC server:
    • keeps a list of all detected automation-related devices
    • gives access to underlying features
    • serves cross-world 3D models of real-life controlled items (e.g. light bulb, displays, ...)
  • device_connectors: protocol-specific plugins
    • X10
    • ZigBee
    • Z-Wave
  • cross-world 3D models, scripting templates and coding resources
  • world-specific interfacing modules

Ultimately, all device-specific information should reside in the devices themselves and answear to requests directly.

Resources

Personal tools