I think the T1 doc/tutorial goes over most of this. The one "type" of TOS_Msg is poorly overloaded in that document vis the contained "type" field. What they meant to say is there can be only on kind of TOS_Msg structure in a particular system -- you can't have mica2's and micaz's in the same radio system, even if they used the same frequency, etc. The TOS_Msg.type field contains what is referred to elsewhere as the "AM type" and is used to specify what user data structure is contained in the TOS_Msg.data array.
David Conde wrote: > Hi, > > > > I am looking information about Tinyos 1.X radio model, I mean I would > like to know how the frames are built in Tinyos 1.x , how are the > different messages types for Tinyos 1.X, and where I could get > information about this. I have reading about this but I just found > information about TinyoS 2.x. > > > > I found a document from Massachusetts where it is said that Tinyos-1.x > only allows one radio message type for a platform “TOS_Msg”, by assuming > that a platform will only be using one radio interface. What does it > exactly mean? I read about TOS_Msg in AM.h file and I found a variable > called “type” in that struct, so, why does it need TOS_Msg struct a > “type” parameter if it only allows one radio message?if this document is > wrong, which are the AM types for Tinyos 1.x? > > > > > > Thank you in advance > > > ------------------------------------------------------------------------ > > _______________________________________________ > Tinyos-help mailing list > [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
