I am working with a ICstick Mote, but you're saying that depends on the chip, the ZigBee chip?
Sorry, I did not understand... the NodeID not initialized with the value that the user wants, for example given in the Makefile? How is it guaranteed to be unique across the network? On Sun, Nov 29, 2009 at 6:54 PM, Paul Johnson <[email protected]> wrote: > NodeID can be any value that is guaranteed to be unique across all nodes. > The most convenient (to set/read) is most likely TOS_NODE_ID, but there may > be other values available depending on your hardware platform. > > Depending on your platform, you may/may not have this "SerialID" feature. > For example, the DS2411 chip is used on some of the tmote brand motes for > this purpose. > > -Paul > > > Ricardo . wrote: > > > Thanks for your response. > > What do you mean by NodeID, is obtained by TOS_NODE_ID, right? My problem > is that I can not change this value efficiently. Worse, it is not desirable > for my application to be dependent on this number that is set manually. > > So my idea was to have a unique number that is not manually modified. I > have read here on the mailling-list that I can obtain the EUI, the unique > 8bits of ZigBee module through the interface S2411, or the 64bit unique > identifier through interface SerialId. The problem is that I do not find any > of this interfaces in my TinyOS Souce Tree (I'm using TinyOS-2.0.2-2). I > could not know why these interfaces are not available, or if have been > renamed. > > I'm stuck in this problem, any ideas are welcome! > > On Sat, Nov 28, 2009 at 2:53 AM, Paul Johnson <[email protected]> wrote: > >> Ricardo, >> >> It's very easy to have a unique sequence number. Just similar to what you >> suggested, you can combine the node's ID with the local sequence number. >> However, I wouldn't suggest adding the two numbers together. If you do, >> then you lose the uniqueness of the sequence number. Instead keep them as >> separate fields in the packet. The sequence number is now <K,NodeID>, >> assuming a node doesn't re-use a K value, it will be globally unique because >> no two nodes should have the same NodeID. >> >> Having globally unique sequence numbers is easy, totally ordering each >> sequence number is another matter. >> >> -Paul >> >> Ricardo . wrote: >> >> Please, anyone? >> >> Any suggestions will be welcome.... >> >> Hello everyone, >>> >>> I wonder if there is any way to send a message with a sequence number >>> that is guaranteed to be unique across the network. For >>> example, MacAddress + K, where K is a counter that is incremented each >>> time that a message is sent. >>> >>> My mote has a RF230 radio. >>> >>> This is possible, or something that has a similar behavior? >>> >>> Thanks in advance, >>> >>> -- >>> Ricardo >>> >> >> ------------------------------ >> >> _______________________________________________ >> Tinyos-help mailing >> [email protected]https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> >> >> > ------------------------------ > > _______________________________________________ > Tinyos-help mailing > [email protected]https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > >
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
