Valid platforms are currently: tmote, telosb, iris, mica2, and micaz
-Installing with NODE_ID 45 (i.e. AM_ADDRESS 45) is jsut to verify that the
+Installing with NODE_ID 45 (i.e. AM_ADDRESS 45) is just to verify that the
application forwards packets with an arbitrarily chosen id, which it should.
To test the correct operation of this application, you need two motes: one with
Don't forget the '.1' when you install, or RadioStress will be configured to
receive rather than send messages. Messages are sent to AM_ADDRESS 0.
-A succssfull test will result in the RadioStress mote constantly flickering all
+A successful test will result in the RadioStress mote constantly flickering all
of its leds very rapidly, and the BaseStation mote flickering its LED0 and LED1
leds rapidly. Additionally, messages should be forwarded over the serial interface
as verified by running the following for the platform of interest:
Blink is a simple application used to test the basic functionality of
TOSThreads.
-You can install Blink on a mote via the following comand:
+You can install Blink on a mote via the following command:
make <platform> cthreads install
Valid platforms are currently: tmote, telosb, iris, mica2, and micaz
packet transmission and reception. To run this application you will need to
burn it on one mote with NODE_ID 0, and a second mote with NODE_ID 1.
-You can install Bounce on a mote via the following comand:
+You can install Bounce on a mote via the following command:
make <platform> cthreads install.0
make <platform> cthreads install.1
Successful running of this application results in each LED bouncing back and
forth between each mote independent of one another. This will continue in an
-finitie loop forever.
+finite loop forever.
Tools:
None.
Description:
Null is an empty skeleton application for testing the basic compilation and
-runtime of a c-based tosthreads aplication. It is useful to test that the build
+runtime of a c-based tosthreads application. It is useful to test that the build
environment is functional in its most minimal sense, i.e., you can correctly
compile an application. It is also useful to test the minimum power consumption
of a node when it has absolutely no interrupts or resources active.
packet transmission and reception. To run this application you will need to
burn it on one mote with NODE_ID 0, and a second mote with NODE_ID 1.
-You can install RadioStress on a mote via the following comand:
+You can install RadioStress on a mote via the following command:
make <platform> cthreads install.0
make <platform> cthreads install.1
Valid platforms are currently: tmote, telosb, iris, mica2, and micaz
-The applicaiton burned with NODE_ID 0 will be programmed as a Receiver and will
+The application burned with NODE_ID 0 will be programmed as a Receiver and will
wait for messages from the sender programmed with NODE_ID 1. In the case of the
sender, messages with three different AM ids are sent from three different
threads in an infinite loop, and one of LED0, LED1, and LED2 are toggled upon
and the process starts over again.
A successful test will result in LED0 toggling periodically at a rate of
-approxiately 220ms (the time it takes to take a humidty + temperature sensor
+approximately 220ms (the time it takes to take a humidity + temperature sensor
reading since they share the same hardware and cannot be taken in parallel).
Additionally, a base station application should be run to verify the reception
A successful test will result in LED0 remaining solid for approximately 6s while
the flash is being erased. After that LED0 will toggle with each successful set
of sensor readings logged to flash, at a rate of approximately 220ms (the time
-it takes to take a humidty + temperature sensor reading since they share the
+it takes to take a humidity + temperature sensor reading since they share the
same hardware and cannot be taken in parallel). Also, LED1 will begin toggling
in rapid succession once every 10000ms as records are successfully read from
flash and sent out over the radio. Once all of the records currently recorded
subdirectory. The sampling rate starts at 4Hz, but can be changed from the Java
application.
-You can install TestCollection on a mote via the following comand:
+You can install TestCollection on a mote via the following command:
make <platform> cthreads install
Valid platforms are currently: tmote, telosb, mica2, and micaz
# or java net.tinyps.sf.SerialForwarder -comm serial@COM2:telosb
./run
-The controls at the bootom of the screen allow yoy to zoom in or out the X
+The controls at the bottom of the screen allow you to zoom in or out the X
axis, change the range of the Y axis, and clear all received data. You can
change the color used to display a mote by clicking on its color in the
mote table.
Description:
-This application tests the operation of the Printf cleint in TOSThreads. It
-continusouly prints the value of a counter starting at 0, increasing as it
+This application tests the operation of the Printf client in TOSThreads. It
+continuously prints the value of a counter starting at 0, increasing as it
prints.
-You can install TestPrintf on a mote via the following comand:
+You can install TestPrintf on a mote via the following command:
make <platform> cthreads install
Valid platforms are currently: tmote, telosb, iris, mica2, and micaz
of LED0, LED1, and LED2 every 256 spawnings. The time at which each LED is
toggled is offset so that the three LEDS do not come on in unison.
-You can install ThreadStress on a mote via the following comand:
+You can install ThreadStress on a mote via the following command:
make <platform> cthreads install
Valid platforms are currently: tmote, telosb, iris, mica2, and micaz
Successful running of this application will result in all three leds flashing at
a rate determined by how long it takes to spawn a thread on a given platform.
-All three LEDs should flash at this rate in an infite loop forever. Given the
+All three LEDs should flash at this rate in an infinite loop forever. Given the
dynamics on the mote the rate may vary over time, but the important thing is
that all three LEDs continue to toggle at a reasonably visible rate.
projects / tinyos-2.x.git / commitdiff