If you see LED's waggling on both motes, the test passed.
-To compile for motes with CC2420 radios, you must do:
- env CFLAGS="-DLOW_POWER_LISTENING" make <platform>
-
-
-
RadioCountToLeds maintains a 4Hz counter, broadcasting its value in
an AM packet every time it gets updated. A RadioCountToLeds node that
Description:
-To compile for motes with CC2420 radios, you must do:
- env CFLAGS="-DLOW_POWER_LISTENING" make <platform>
-
Install the application to two nodes with the following ID's:
Node 0 (Receiver node): id = 0
Node 1 (Transmitter node): id = 1 (or.. id > 0)
None.
-$Id$
\ No newline at end of file
+$Id$
+Author/Contact: tinyos-help@millennium.berkeley.edu
+
+Description:
+
This is more of a general demonstration than a test.
Install this application to one node, connected to the computer.
graph, it's scaled by some (possibly non-linear) factor.
-Java Application Usage:
- Linux: java SpecAnalyzer.class [-comm <packetsource>]
- Windows: java SpecAnalyzer [-comm <packetsource>]
+Tools:
+ java SpecAnalyzer [-comm <packetsource>]
- If not specified, the <packetsource> defaults to sf@localhost:9001 or
+ If not specified, the <packetsource> defaults to sf@localhost:9002 or
to your MOTECOM environment variable (if defined).
+
+Known bugs/limitations:
+
+None.
+
+$Id$
-Installing:
+Author/Contact: tinyos-help@millennium.berkeley.edu
+
+Description:
+
Compile and install this application to two motes, both using ID 1
Expectations:
Led1 Toggles on a received ack
Led2 Toggles when a message is received
-In short, Led1 should be toggling the majority of the time, until the other receiver
+In short, Leds 1&2 should be toggling the majority of the time, until the other receiver
stops receiving packets by turning off or moving out of range.
+Tools:
+
+None.
+
+Known bugs/limitations:
+
+None.
+
+$Id$
+Author/Contact: tinyos-help@millennium.berkeley.edu
+
+Description:
+
Test the effectiveness of the PacketLink layer
INSTALL
- Transmitter == 1, 2, 3, 4, or 5 (up to MAX_TRANSMITTERS)
- Receiver == 0, plugged into the computer
+ Transmitter: id == 1, 2, 3, 4, or 5 (up to MAX_TRANSMITTERS)
+ Receiver: id == 0, plugged into the computer
EXPECTATIONS
Transmitter (ID not 0) -
reaction.
-Java Application Usage:
- Linux: java TestPacketLink.class [-comm <packetsource>]
- Windows: java TestPacketLink [-comm <packetsource>]
+Tools:
+
+ java TestPacketLink [-comm <packetsource>]
If not specified, the <packetsource> defaults to sf@localhost:9001 or
to your MOTECOM environment variable (if defined).
This application will report dropped and duplicate packets as seen on
the receiver.
+
+Known bugs/limitations:
+
+None.
+
+$Id$
+Author/Contact: tinyos-help@millennium.berkeley.edu
+
+Description:
+
This application is used more for characterization rather than a test.
It measures the maximum radio throughput using the largest message payload
size, and does not use low power listening.
-
-Install:
+INSTALL
Compile and install this application to one mote. Leave the mote connected
to the computer.
-Expectations:
+EXPECTATIONS
Led1 will toggle as each message is transmitted. Once a second, the mote
-will send a packet through the serial port to the computer. Run the
-TxThroughput java application:
+will send a packet through the serial port to the computer.
+Tools:
+
+Run the TxThroughput java application:
Linux: java TxThroughput.class [-comm <packetsource>]
Windows: java TxThroughput [-comm <packetsource>]
[Packets/s]: 115; [(Payload Bytes)/s]: 3220
[Packets/s]: 124; [(Payload Bytes)/s]: 3472
+Known bugs/limitations:
+
+None.
+
+$Id$