I have one silly question :
Why Tcl and not X ?
(of course X could be whatever programming language you've heard of, but I'm more specifically thinking about Ruby since I'm doing web-sites and scripts daily with that language !)
Anyway I will probably, one day, try to link your JeeMon stuff with a Ruby on Rails website... When my JeeStuff will work, of course ! ;-)
I will try to learn a bit about Tcl soon, to see if I can help with JeeMon development.
Your kind of auto-configuration of JeeMon looks great !
What I'd like to see, and I'm not sure what is available now, is :
A Node acting as a listener, connected to a computer running JeeMon, telling what it's got on inputs, and what it receive (from who) on RF12.
The listener could also buffer the data on flash when it's not connected to JeeMon.
Some Node(s) sending data to the listener, via RF12, aka senders.
Sender could also act as a relay if another sender can not reach a listener (really basic mesh implementation).
Data traveling in the other way could be useful as well but maybe a bit more tricky, involving keeping track of the connected Nodes, even a kind of "routing table"...
Could that sort of things be implemented in the RF12 driver ?
Or maybe in a dedicated RF12Network class ?
All these things in parallel to sensor reading tasks, etc...
I'd be glad the help with the design of that kind of software stack if you've not thought about it already.
Keep up !
