- polished READMEs

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

diff --git a/apps/tests/tkn154/beacon-enabled/TestIndirect/README.txt b/apps/tests/tkn154/beacon-enabled/TestIndirect/README.txt
index e25ab91753dc9013ce744139a8ff312773b544a9..f963b8018606bf6d8cf857f62cdcddde640e98f4 100644 (file)
--- a/apps/tests/tkn154/beacon-enabled/TestIndirect/README.txt
+++ b/apps/tests/tkn154/beacon-enabled/TestIndirect/README.txt
@@ -1,10 +1,10 @@
 README for TestIndirect
-Author/Contact: tinyos-help@millennium.berkeley.edu
+Author/Contact: Jan Hauer <hauer@tkn.tu-berlin.de>
 
 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 additionally in
+beacon-enabled 802.15.4 PAN, it transmits periodic beacons and additionally in
 every beacon interval it tries to transmit one DATA frame to a device using
 indirect tranmission. A second node that takes the role of a device first scans
 the pre-defined channel for beacons from the coordinator and once it finds a
@@ -12,12 +12,11 @@ beacon it tries to synchronize to and track all future beacons. Whenever the
 coordinator has data to send (indicated in the beacon), the device extracts the
 DATA frame from the coordinator.
 
-The third LED (Telos: blue) is toggled whenever the coordinator has transmitted
-a beacon, it is not used on the device. On the coordinator the second LED
-(Telos: green) is toggled for every transmitted DATA frames. On a device the
-second LED is toggled for every received DATA frame. The first LED (Telos: red)
-is used for debugging, it denotes an error in the protocol stack and should
-never be on.
+Criteria for a successful test:
+
+Both nodes should toggle the LED1 in unison, about once every half second. 
+The coordinator should also toggle LED2 with the same frequency.
+
 
 Tools: NONE