X-Git-Url: https://oss.titaniummirror.com/gitweb/?a=blobdiff_plain;f=apps%2Ftests%2FTestNetwork%2FREADME.txt;h=b533acdc7bea27d38a88a6eba93ac102d338ef6d;hb=e9bfab607e051bae6afb47b44892ce37541d1b44;hp=ed52205076f267e36aa3ab6974127e4b7c593c97;hpb=adf1de6c009d13b7b52e68535c63b28f59c97400;p=tinyos-2.x.git

diff --git a/apps/tests/TestNetwork/README.txt b/apps/tests/TestNetwork/README.txt
index ed522050..b533acdc 100644
--- a/apps/tests/TestNetwork/README.txt
+++ b/apps/tests/TestNetwork/README.txt
@@ -14,6 +14,24 @@ Collection Tree Protocol for details.
 There are scripts on net2 website to parse the debug messages sent by
 the nodes.
 
+To test, start with two motes with no program that transmits
+packets. Example., erase the mote or install Blink. Program a mote with
+node id 0. The mote will toggle led1 (green on TelosB) approximately
+every 8s. Then program the second mote with id 1. Once programming is
+complete, the mote with id 0 will toggle led1 twice every 8s. Each
+toggle corresponds to the reception of collection message (once from
+itself, and once from the mote with id 1).
+
+Errors indications:
+
+Motes 0 and 1 will set led0 (red on TelosB) if there are errors while
+sending the packet.
+
+Mote 0 will set led2 (blue on TelosB) if the gap in sequence number on
+consecutive packet reception from node 1 is greater than 1. This is
+expected to be a rare event while doing experiment on a desk.
+
+
 Known bugs/limitations:
 
 None.