Changes

XMPPHWFS

572 bytes added, 20:01, 1 February 2012
added project template and minor corrections
'''hardware IOs made available''' (on a fuse filesystem) '''through xmpp messaging protocol'''. The latest idea is to use fuse only as on option, so the name will definitely change. ''locmon2'' seems like a good candidate to me.
== Description ==
XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way. Any suggestions are welcome, coding has not really started yet anyway.
:I've been dreaming of a 3D GUI where you can walk around and interract with the hardware in a natural fashion. Volunteers?
=== Device description ===
Since XMPPWHFS is aimed towards real-world I/Os, we need lots of useful info that must be made available by each HAL
==== About the HAL ====
* name
* description
* icon? I think we don't really care about the HAL itself, it's just a way to conveniently group I/Os
==== About devices on each HAL ====
* variable name
* variable type and allowed values (int, float, enum..)
* icon? maybe not necessary. one can be chosen from the I/O name or type.
==== Sample session ====
;To HAL:This is to get the simple, human-readable output
<pre>help</pre>
=== Events ===
When an event is detected by a HAL (threshold exceeded for example), the HAL sends the info with the Pub/Sub mechanism. other bots can subscribe to ''event-master'' who will events, and then decide what to do. In this case, the syntax does not much, so  we 'll get something like:(suggestions welcome!)
<pre><device name='temperature' value=11.8>warn_low_value</device></pre>
== Obstacle ==* lack of expertise and motivation to implement a client in a µC* weak programming skills == Components ===== Software ===
Some things can can be handy:
* [http://thp.io/2007/python-jabberbot/ JabberBot] in python
=== Hardware ===
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]
=== Software extensions ===
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD
 
== Schedule ==
=== as soon as possible ===
* design a smart way to handle events (scripting/rules interface)
* implement test HAL client/bot with Pub/Sub
* implement event_master with Pub/Sub
* implement ctrl_bot
 
=== when the above is done... ===
* implement web interface on ctrl_bot
* implement fs_bot
* implement HAL bot on µC ([[SuperCaptor]]!!)
 
== Participant ==
* [[User:Petaflot]]
77
edits