Updated all READMEs with an extra section that describes how a successful test is...

[tinyos-2.x.git] / apps / tests / tkn154 / beacon-enabled / TestAssociate / README.txt

diff --git a/apps/tests/tkn154/beacon-enabled/TestAssociate/README.txt b/apps/tests/tkn154/beacon-enabled/TestAssociate/README.txt
index 94ad58ab4a4c1c68638af946ba5bb335b09fd4c6..83cb0e6839ee8f7c471126b4e185fcb45db44d83 100644 (file)
--- a/apps/tests/tkn154/beacon-enabled/TestAssociate/README.txt
+++ b/apps/tests/tkn154/beacon-enabled/TestAssociate/README.txt
@@ -4,25 +4,21 @@ Author/Contact: tinyos-help@millennium.berkeley.edu
 Description:
 
 In this application one node takes the role of a PAN coordinator in a
-beacon-enabled 802.15.4 PAN; it transmits periodic beacons and waits for
+beacon-enabled 802.15.4 PAN, it transmits periodic beacons and waits for
 devices to request association to its PAN. Whenever a device tries to
-associate, the PAN coordinator allows association and assigns to the device a
-unique short address (starting from zero, incremented for every device
-requesting association). 
-
-A second node acts as a device; it first scans the pre-defined channel for
-beacons from the coordinator and once it finds a beacon it tries to associate
-to the PAN and synchronize to and track all future beacons. A short time after
-association the device then disassociates from the PAN. 
-
-The third LED (Telos: blue) is toggled whenever the coordinator has transmitted
-a beacon or whenever a device has received a beacon. On the coordinator the
-second LED (Telos: green) is switched on whenever an association request was
-successful and it is switched off, whenever a disassociation request was
-received. On a device the second LED is switched on while the device is
-associated to the PAN, i.e. it is switched off after disassociation. The first
-LED (Telos: red) is used for debugging, it denotes an error in the protocol
-stack and should never be on.
+associate, the PAN coordinator accepts the association and assigns to the
+device a unique short address (starting from zero, incremented for every device
+new association). A second node acts as a device, it first scans the
+pre-defined channel for beacons from the coordinator and once it finds a beacon
+it tries to associate to the PAN and synchronize to and track all future
+beacons. A short time after association the device then disassociates from the
+PAN. 
+
+Criteria for a successful test:
+
+Assuming one coordinator and one device has been installed, both should
+simultaneously toggle (only) the second LED, about once every 5 seconds.
+
 
 Tools: NONE