X-Git-Url: https://oss.titaniummirror.com/gitweb/?a=blobdiff_plain;f=apps%2Ftests%2Ftkn154%2Fbeacon-enabled%2FTestAssociate%2FREADME.txt;h=f8623dd9864016d4ec4880f6c81dc83b5e8ec7ed;hb=4944808843447cbd5a337e2dc35c26e9ec1fe422;hp=83cb0e6839ee8f7c471126b4e185fcb45db44d83;hpb=2d7854932f7589657e485cfca01a0a6863587967;p=tinyos-2.x.git diff --git a/apps/tests/tkn154/beacon-enabled/TestAssociate/README.txt b/apps/tests/tkn154/beacon-enabled/TestAssociate/README.txt index 83cb0e68..f8623dd9 100644 --- a/apps/tests/tkn154/beacon-enabled/TestAssociate/README.txt +++ b/apps/tests/tkn154/beacon-enabled/TestAssociate/README.txt @@ -1,5 +1,5 @@ README for TestAssociate -Author/Contact: tinyos-help@millennium.berkeley.edu +Author/Contact: Jan Hauer Description: @@ -7,17 +7,16 @@ 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 devices to request association to its PAN. Whenever a device tries to 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 +device a unique short address (starting from zero, incremented for every new +association request). 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. +it tries to associate to the PAN. 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. +Both, coordinator and device, should toggle LED1 in unison about once every 5 +seconds. The coordinator should also toggle LED2 every second. Tools: NONE