woops... sorry, i did a research for this problem in the mailing list before 
posting but maybe i searched the wrong words. 
so as i can see you have the same issue.

yeah, sometimes happens and sometimes not... and when happens it seems to run 
this behavior for a lot of time.
it doesn't seems to follow any particular path that lead to this error. 
I've made many simulation (with dbg statements) and real deployment (with 
printf) and i've seen the problem happens in both ambients (TOSSIM and real 
nodes).
(anyway i must say that my application, and simulation too, are heavily based 
on external random numbers)

however i've just done a search in the mailing list with words "tymo senddone" 
and i've found your previous post. (and that lead me to this question: damn, 
which words i used yesterday to make the search? :D  )

as i can see nobody replied you on this problem. :(
in the mean time have you found hints or something else about that?

On Wednesday 22 October 2008 14:18:53 Andrey Gursky wrote:
> De-MonHell,
>
> I've already posted here this problem. If it would happened only
> periodically/once, it would be OK. But if in my application it once
> occurs, than it happens every time after that till crash. And what is
> about your application?
>
> Best wishes,
> Andrey
>
> De-MonHell wrote:
> > hi all,
> >
> > i know tymo is not considerable as stable yet, but:
> >  is it normal that sometimes sending a tymo packet, in the senddone
> > event, return an error=FAIL also if the packet is correctly trasmitted?
> > (the destination node received the packet for sure)
> > why does  it happens?
> >
> > maybe tymo use a different codification for the error_t's enum?
> >
> > thanks
> > _______________________________________________
> > 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

Reply via email to