Description:
In this application one node takes the role of a PAN coordinator in a
-nonbeacon-enabled 802.15.4 PAN; it switches its radio to receive mode.
+nonbeacon-enabled 802.15.4 PAN, it switches its radio to receive mode. A
+second node acts as a device, it switches to the pre-defined channel and
+periodically performs active-scans (i.e. sends out beacon request frames) on
+the predefined channel and expects beacon frames in return.
-A second node acts as a device; it switches to the pre-defined channel and
-performs active-scans on the predefined channel.
+Criteria for a successful test:
-A few basic parameters of this example can be adjusted through the
-'app_profile.h' file.
+On the coordinator node (only) the second LED should toggle once every 2
+seconds. On the device the second and third LED should toggle once every 2
+seconds, but with a small offset of half a second. On the device the first
+LED may toggle, but this should happen very rarely.
-Leds Coordinator: The first led (Telos: red) is used for debugging purposes
-only and when switched on indicating an error in the protocol-stack. The
-second led (Telos: green) flashes when an active scan, more exactly a
-beacon-request, is received by the coordinator.
-
-Leds Device: The third led (Telos: blue) is activated for a second whenever an
-active-scan is performed. Shortly after that the second or the first led
-flashes. The second led (Telos: green), indicating that the coordinator
-defined in the 'app_profile.h' where found in that scan. The first led if
-either no devices or only no matching devices where found within the scan.
Tools: NONE
projects / tinyos-2.x.git / blobdiff