Re: [tuxdroid-user] How tuxes "see" each other?

[David B. <da...@ja...>]

On Mon, 19 Mar 2007 21:02:54 +0100, Florent THIERY <ft...@gm...>  
wrote:

> About standalone features: could you please try describing how far
> these feature could go?

Sorry but that'll take some time to write something clear and I'll add a  
page about this on the wiki but I have other priorities now. I'll tell you  
when it's ready, it'll be there: http://www2.tux-is-alive.com

But in a few words, right now we can only store some small sequences of  
tux commands (sounds, movements, leds, send IR,...). Then you can trigger  
one of these sequences from an event. These events needs to be hardcoded  
in the firmware but we can have them even if we don't use them.

What I planned to do at first is to have:
- configuration registers in flash and eeprom that enable/disable events
- events associated to sequences
- sequence definitions in eeprom

When you press on the head button, I should do:
- detect the head button
- if the configuration register for the head button event is enabled, I  
emmit the head button event
- the head button event will launch the head button sequence which is  
stored in eeprom ans is a blink of the blue led's

I would like to be able to configure that from the computer by:
- enabling or disabling events (registers changed in flash so when you  
switch off, you loose your changes)
- storing configuration registers in eeprom to keep changes permanently
- customizing the sequences in eeprom

Maybe we can also have 2 sets of configuration registers so one is valid  
when tux is connected to the RF and one when tux is really in standalone.

You could do much more with standalone but then you'll have to customize  
the firmware directly and because the memory is limited, you're likely to  
have to remove stuff to add what you want to do. But it should be possible  
to add stuff on the I2C bus like temperature/humidity sensors,  
accelerometers,... you may also have to open tux and alter the circuit if  
you want to connect other things. If you don't do that, you're limited  
anyway by the input of tux which is only a few buttons, light and IR.

HTH,
david