I found the "retraction period" to be significant in my reliability testing that I've previously ref'ed. Things were greatly improved by putting a small delay between the reception of a message and the sending of a new message at the host end. I don't know if this a host effect or slow switching from receive to xmit on the radio end. It was much more pronounced on the mica2's than the 'Z's. I didn't do any extensive testing with the telosb.
MS Maisa Ben Jamaa wrote: > Hi, > Umm, so this can be like a collision that was being happening over the > serial communication channel. > Thank you Faisal > > 2009/7/18 Faisal Aslam <[email protected] > <mailto:[email protected]>> > > Hi, > > I also have this error if I send packet from mote too fast (Usually > in a loop). If you can have a small delay between packets being send > from mote then you will have lesser bad packets errors. > > best regards, > Faisal > > Maisa Ben Jamaa wrote: > > Hi, > > If tinyos reports a lot of bad packet messages during a pc and > sensor mote > communication based on an usb connection, so in your opinion why > this, > is happening? > > Precisely, what causes that the *packet crc* is different from > the computed one? > (more details can be found in Packetizer.java file) > > Best regards, > Maissa Ben Jamaa > _______________________________________________ > Tinyos-help mailing list > [email protected] > <mailto:[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 _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
