OK, I'll take a stab at these...

1) The motes themselves have a two bit integer identifier assigned
when the program is downloaded (make <platform> install.ID).
Since motes require some kind of base-station and usually fan out,
the B-S can be assigned an IP addr and mapped to a number of
individuals. The SerialForwarder demo-program is an example, as
is the MIB600 base-station adapter (I think that's the one) which
is a network node itself.

2) I don't know the 802 details but the claims I have seen say
the micaZ and other 2240 radio motes support, or at least don't
break, the physical layers. As far as I know there is not a full
impl of the standard. Search this list for discussions...

3) Routing is "ad-hoc". Heh. Again I don't know details but
that is one of the main research areas for sensor-nets. I think
the available demo programs are basically broadcast forwarding.
Google and TOS document searching ought to be your friends here.
This might be a good place to start:
    http://www.moteiv.com/community/TinyOS_Information

4) If it's entirely ad-hoc and just re-broadcasts anything it
receives, it's MobileReady(TM)...

MS

Tan Han Chiang wrote:
Hi all,
I am currently new to TinyOS and sensor networks and would like to ask
for your help to clarify some of my questions.
1) How are TinyOS motes addressed?? Saw some of the posting that we
actually fix each mote ID manually when we install the application into
the mote. How long is the address space?? Does it follows the IP format
or is it just a normal integer. Are mote identified only by this ID??
2) Does TinyOS follows 802.15.4 standards?? If not, are we able to
use/implement the standard into the motes?
3) How is the routing of the mote being done in a TinyOS network?? (for
topology like mesh or tree network) Or do we need to fix each route
manually like the mote ID
4) Does the current TinyOS implementation allows mobile motes or just
static motes topology?
Thanks for helping me out.. =)
------------ Institute For Infocomm Research - Disclaimer -------------
This email is confidential and may be privileged.  If you are not the intended 
recipient, please delete it and notify us immediately. Please do not copy or 
use it for any purpose, or disclose its contents to any other person. Thank you.
--------------------------------------------------------
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to