In a mesh network, not all communications are unicast. For example, dissemination is a case in which the source doesn't matter and the destination is broadcast. Following the principle of generality, source id's are not needed by every application, and so was left out of TOS messages. Whether or not this is a good idea in practice is an entirely different question. Sure makes it hard to debug distributed applications when you can't figure out which node sent which packet. The solution, as Michael points out, is to add it to the data portion of your payload.
- Prabal On 3/6/06, Michael Schippling <[EMAIL PROTECTED]> wrote: > Strangely...the source ID is not included in the Msg header. > You need to define and set your own data payload field to get it. > MS > > Chuck Kring wrote: > > Hello, > > > > This seems like a silly question to me because it should be obvious, but > > I can't find the appropriate field > > in TOS_Msg nor any library calls to do this: > > > > If I have a message sent by GenericCommPromiscuous (i.e. not a multihop > > message), how do I determine the mote_id > > of the sender? > > > > Thanks in advance! > > > > Chuck Kring > > > > [EMAIL PROTECTED] > > > > _______________________________________________ > > Tinyos-help mailing list > > [email protected] > > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
