There appears to be a number of mechanisms built into the version 2 software, including modules/components such as QueueC, AMQueueP, AMQueueImplP, AMQueueEntryP... but all of these seem to create a single message route/queue per each unique AMsenderC created with no obvious way (that I can see so far!) to place multiple message types in a single queue.
Is there a more flexible send component in tinyOS 2 that I have missed that would allow me to specify the [am_id_t id] or type part of the header dynamically at runtime? Or do I need to write in this functionality myself? Many thanks Ben > > There used to be a QueuedSend interface in the T1 lib tree... > MS > > > Murray, Ben wrote: > > Hi > > I need to send multiple types (am_id_t / len) of mesage but > I need to store > > them up in a Queue until the mote has permission to send. > > > > How best can I store multiple messages, of varying types/lenths, and > > subsequently send them - do I still require multiple > AMSend.send functions > > but use the queue to route them correctly, or can I set the > am_id_t type per > > message within the same send interface? It would be much > easier to set the > > am_id_t at runtime so when further message types get added > it does not > > require altering of the underlying control code. > > > > For example, in LPL I can send a number of different > message types but > > surely they all get routed via the same AMSend component as > LPL cannot know > > what am_id_t I wish to set? > > > > Xp/cygwin > > T2 > > micaz > > cc2420 > > > > cheers, > > Ben > > ******************************************************************************* Please consider the environment before printing this email. ******************************************************************************* This email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may not be divulged to any third party without the express permission of the originator. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thales Research & Technology (UK) Limited. ******************************************************************************* _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
