X-Git-Url: https://oss.titaniummirror.com/gitweb?a=blobdiff_plain;f=apps%2Ftests%2Ftkn154%2FTestData%2FREADME.txt;fp=apps%2Ftests%2Ftkn154%2FTestData%2FREADME.txt;h=0000000000000000000000000000000000000000;hb=e9bfab607e051bae6afb47b44892ce37541d1b44;hp=08d0939e8d4d9e8888215c5a47877172eb7b7fdd;hpb=adf1de6c009d13b7b52e68535c63b28f59c97400;p=tinyos-2.x.git

diff --git a/apps/tests/tkn154/TestData/README.txt b/apps/tests/tkn154/TestData/README.txt
deleted file mode 100644
index 08d0939e..00000000
--- a/apps/tests/tkn154/TestData/README.txt
+++ /dev/null
@@ -1,45 +0,0 @@
-README for TestData
-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
-incoming DATA frames. 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 synchronize to and track all future beacons. It then starts to
-transmit DATA frames to the coordinator as fast as possible (direct
-transmission in the contention access period, CAP).
-
-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 toggled for every 20 received DATA frames. On a
-device the second LED is toggled for every 20 transmitted (and acknowledged)
-DATA frames. The first LED (Telos: red) is used for debugging, it denotes an
-error in the protocol stack and should never be on.
-
-Tools: NONE
-
-Usage: 
-
-1. Install the coordinator:
-
-    $ cd coordinator; make telosb install
-
-2. Install one or more devices
-
-    $ cd device; make telosb install,X
-
-    where X is a pre-assigned short address and should be different 
-    for every device.
-
-You can change some of the configuration parameters in app_profile.h
-
-Known bugs/limitations:
-
-- Currently this application only works on TelosB nodes
-- The MAC timing is not standard compliant, because TelosB lacks a
-  clock with sufficient precision/accuracy
-
-$Id$o
-