That is not my experience with the mica{2,z}, although I have not tried
immediate sequential sends as you show. In my 'reliability testing' that
I've reported over the last couple months I fire off messages to a re-Mote
which tries to reply immediately. In that case I can get around 12
request/response pairs per sec on the '2 and 50 on the 'z. Throttling
to those speeds seems to be necessary to minimize lost messages, but
not to .5 second.
I have not tried tmotes (at all) but I believe their radio is very
similar to the micaz.
I wonder if you are having task contention problems or something?
MS
Andrea Pacini wrote:
I noticed that when you must send , for example, 3 messages, you must
put a timer between a send and the following send;
if I don't do it the following send cannot be executed. That is, the
scheme I used is (for 3 send):
[...]
*call Send(...); * // send
[...]
[...]
*event senddone(..)* {
if (<FIRST SEND> or <SECOND SEND>)
call Timer.start(TIMER_ONE_SHOT,<TIME>);
}
[...]
*Timer.fired()* {
[...]
if (<FIRST SEND> OR <SECOND SEND>))
call Send(...);
[...]
}
If I don't put the timer (scheduled with <TIME> = 0.4 - 0.5 seconds)
send are not executed. Do you confirm this behaviour ?
Thanks
Andre
------------------------------------------------------------------------
_______________________________________________
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
