Paul Alfille wrote: > Thinking about the "small owserver" some more, this is an interesting > problem. > > owserver is too smart, it knows too much about the devices. > > I've been working on the internal protocol to change to communication to > the adapters to "transactions". That would be the right level to send to > a small device., and would be easy to implement. Probably fit in 9k and > maybe even PICs and the like. > > Paul. > > Alternatively we could emulate the LINK ascii mode, which works in > remote tcp form. Probably should get permission and a quote from Bill > Farmer. > > On 6/3/06, *Paul Alfille* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > I suppose you are right about the config file. > > Small owserver? > 1. We'll need to strip. > 2. Remove (#define out) the debugging messages. > 3. Remove caching > 4. Make non-reentrant. > 5. Remove other adapters, thermocouples, ... > > There are no large buffers or memory pools. Still, are we talking 9k > or 40k? > > Paul >
Paul, The mote has 48KB flash program store, 10KB RAM, and has to fit the bootstrap and TinyOS in as well. Radio runs at 250Kbps zigbee mesh (802.15.4). The remote ascii form with the necessary I2C to 1-wire glue might be the way to go. jerry _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
