Thanks! Ok, don't worry, I understand concurrency. However, when you use AM protocol, you use AMStandard (not UartStream), and AMStandard doesn't allow send radio and uart packets "at the same time", even when the uart (or radio) is idle (a variable named "state" is checked). This behavior looks intentional... any reason for this?
----- Mensaje original ---- De: Steve McKown <[EMAIL PROTECTED]> Para: tinyos-help@millennium.berkeley.edu CC: jose m <[EMAIL PROTECTED]> Enviado: martes 5 de junio de 2007, 1:20:23 Asunto: Re: [Tinyos-help] Active message protocol On Monday 04 June 2007 13:38, jose m wrote: > Checking out the AMStandard.nc file I see that, if you are transmitting a > radio message, the AMStandard component is occupied until the tx is done, > and you cannot tx to UART until then. Why? any problem tx to radio and UART > at the same time? Assuming the radio and serial UART don't share any common resources, their operations can certainly be interleaved. For example, you can call AMSend.send(...) and then on the very next line call UartStream.send(...). The actual order of execution occurs based upon the TinyOS concurrency model. AMSend.sendDone() and UartStream.sendDone() will be each called as their relevant split-phase operations complete. If you want to learn more about TinyOS concurrency, check out Philip Levis' programming guide @ http://csl.stanford.edu/~pal/pubs/tinyos-programming.pdf All the best, Steve __________________________________________________ Preguntá. Respondé. Descubrí. Todo lo que querías saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas
_______________________________________________ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
