Hello again, I did some more investigations on the ACK error I described in my previous mail. It seems like I had quite the same error about a year ago but since then I used tossim quite a lot and the error did not show up there.
I have written a small example application that shows the error I have. The application has a fixed message_t variable and a pool from which it gets another message_t. It then sends the fixed message_t and the message_t from the pool alternately over and over again. Upon reception the receiving node lights the received message on its LED. The nodes print some debugging information out on the screen showing which kind of message_t they are actually sending and if it is acknowledged. Depending on the size of the pool used I get different behavior when it comes to acknowledgements. For me the configuration of the program appended yields no ack for packets that come from the pool but the packets not coming from the pool all get acknowledgements. Other pool sizes yield other results. In several (maybe all?) configurations the first two packets never get acknowledged independent of whether they come from the pool or not. Another thing to notice is that although the packets are not acknowledged, they have been properly received, which is signaled by the blinking LEDs. In some configurations the behaviour of ACKs changes between resets of the node. I am really searching for some advice on this. The actual program I am working on is using at least two pools, which I suspect are the reason why I never get an ack there although all the messages sent are received and everything is working flawless in tossim. Thanks, David.
Makefile
Description: Binary data
poolTestAppC.nc
Description: Binary data
poolTestC.nc
Description: Binary data
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
