Hi Stefano, >> Do you know the source of your packet loss? > > Yes, we believe to know the source of the problem. It should be > related to channel access. In fact, we made some experiment with to > identify the source of the problem. The simplest configuration which > shown the packet loss was the following. A network composed by 4 node, > a sink (connected to the PC), a timer node, and two leaves nodes. The > timer node was sending a beacon packet once every second, while the > leaves nodes when received the beacon packet they answered by sending > a packet to the sink. The result of the experiment shown a packet loss > of 50% of the packet sent by the leaves node to the sink, with an > equal distribution between the leaves.
That is very strange. It should have practically no packet loss (at reasonable traffic). Can you post your code? >> Did you try to fiddle with the software collision avoidance algorithm? > > Which "software collision avoidance algorithm" are you referring to? > How can I fiddle with it? Read the chips/rf2xx/README and chips/rf2xx/rf230/README files. I was referring to the slotted collision avoidance algorithm, which you can enable by defining SLOTTED_MAC in your makefile. Also you can change the random backoff periods for the default CA algorithm. > As I mentioned above, please consider that in our scenario we do not > need the ACK. Just because you do not need it, you can still enable it. Do you observe the same behavior with the standard driver which does not do hardware acks? Miklos _______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
