IIRC, Xmesh handles messages just like regular old TOS in respect to message type dispatch. You need to have a receive method configured, and may have to address the message to the specific nodeID, rather than BCAST. I think most messages are just re-broadcast to the base station rather than processed locally.
Xmesh uses the Tos_Msg type field for it's own purposes so I wouldn't mess with it. There is a second user-type filed (I think) in the Xmesh header for what used to be considered the user's payload AM type. MS Atslands Rocha wrote: > Hi, all, > I am using TinyOS-1.x running on MICAZ motes. I have an application > where i have a node which receives multiple packets with different > payloads from neighbors. I am wondering how the destiny node is able to > handler each message depending on AM type. I am using the MhopSend and > Receive interfaces. > > Can I update the type field of Tos_Msg? I read before that this field is > reserved by Xmesh protocol. > > Thanks in advance. > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Tinyos-help mailing list > Tinyos-help@millennium.berkeley.edu > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help _______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
