Difference between revisions of "xAP Home Automation protocol"
From XAP Automation
Line 3: | Line 3: | ||
The primary design objectives are: | The primary design objectives are: | ||
− | + | *Simple, easy to implement/retrofit | |
− | + | *Suitable for use with a wide range of processing capabilities, from embedded controllers to fully fledged PC's | |
− | + | *Operating system agnostic | |
− | + | *Programming language agnostic | |
− | + | *Network agnostic | |
These are lofty design goals, and initial implementation is currently focussed on IP based networks, PC's running Linux and Win/32, and Rabbit embedded microcontrollers. | These are lofty design goals, and initial implementation is currently focussed on IP based networks, PC's running Linux and Win/32, and Rabbit embedded microcontrollers. | ||
− | |||
− | |||
== For Users == | == For Users == | ||
[[Getting started]] | [[Getting started]] | ||
Line 18: | Line 16: | ||
[[xAP Websites]] | [[xAP Websites]] | ||
− | |||
== For Developers == | == For Developers == | ||
[[Protocol definition]] | [[Protocol definition]] |
Revision as of 23:23, 30 April 2006
xAP is an open protocol intended to support the integration of telemetry and control devices primarily within the home - it is the glue that supports the interconnectivity of Home Automation devices.
The primary design objectives are:
- Simple, easy to implement/retrofit
- Suitable for use with a wide range of processing capabilities, from embedded controllers to fully fledged PC's
- Operating system agnostic
- Programming language agnostic
- Network agnostic
These are lofty design goals, and initial implementation is currently focussed on IP based networks, PC's running Linux and Win/32, and Rabbit embedded microcontrollers.