From f28a01108f73c6c5e29e3dc68f0f2967268e4f1a Mon Sep 17 00:00:00 2001 From: razvanm Date: Wed, 25 Jun 2008 02:47:03 +0000 Subject: [PATCH] Fix some typos. --- apps/tosthreads/capps/BaseStation/README | 4 ++-- apps/tosthreads/capps/Blink/README | 2 +- apps/tosthreads/capps/Bounce/README | 4 ++-- apps/tosthreads/capps/Null/README | 2 +- apps/tosthreads/capps/RadioStress/README | 4 ++-- apps/tosthreads/capps/SenseAndSend/README | 2 +- apps/tosthreads/capps/SenseStoreAndForward/README | 2 +- apps/tosthreads/capps/TestCollection/README | 4 ++-- apps/tosthreads/capps/TestPrintf/README | 6 +++--- apps/tosthreads/capps/ThreadStress/README | 4 ++-- 10 files changed, 17 insertions(+), 17 deletions(-) diff --git a/apps/tosthreads/capps/BaseStation/README b/apps/tosthreads/capps/BaseStation/README index e9546dee..66ef052f 100644 --- a/apps/tosthreads/capps/BaseStation/README +++ b/apps/tosthreads/capps/BaseStation/README @@ -15,7 +15,7 @@ To run this application install it on a mote via the command: 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 @@ -30,7 +30,7 @@ install RadioStress via the command: 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: diff --git a/apps/tosthreads/capps/Blink/README b/apps/tosthreads/capps/Blink/README index c3ad340d..853f0ce1 100644 --- a/apps/tosthreads/capps/Blink/README +++ b/apps/tosthreads/capps/Blink/README @@ -7,7 +7,7 @@ Description: 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 cthreads install Valid platforms are currently: tmote, telosb, iris, mica2, and micaz diff --git a/apps/tosthreads/capps/Bounce/README b/apps/tosthreads/capps/Bounce/README index 56efdf16..7bedfdec 100644 --- a/apps/tosthreads/capps/Bounce/README +++ b/apps/tosthreads/capps/Bounce/README @@ -11,7 +11,7 @@ This application stresses the operation of the thread based AM commands for 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 cthreads install.0 make cthreads install.1 @@ -33,7 +33,7 @@ reception.. 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. diff --git a/apps/tosthreads/capps/Null/README b/apps/tosthreads/capps/Null/README index 8c058ae0..c568d2dc 100644 --- a/apps/tosthreads/capps/Null/README +++ b/apps/tosthreads/capps/Null/README @@ -5,7 +5,7 @@ Author: Kevin Klues 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. diff --git a/apps/tosthreads/capps/RadioStress/README b/apps/tosthreads/capps/RadioStress/README index 281f7501..a6263dff 100644 --- a/apps/tosthreads/capps/RadioStress/README +++ b/apps/tosthreads/capps/RadioStress/README @@ -8,13 +8,13 @@ This application stresses the operation of the thread based AM commands for 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 cthreads install.0 make 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 diff --git a/apps/tosthreads/capps/SenseAndSend/README b/apps/tosthreads/capps/SenseAndSend/README index 034fd198..bccfef91 100644 --- a/apps/tosthreads/capps/SenseAndSend/README +++ b/apps/tosthreads/capps/SenseAndSend/README @@ -20,7 +20,7 @@ interface in an infinite loop. Upon successful transmission, LED0 is toggled, 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 diff --git a/apps/tosthreads/capps/SenseStoreAndForward/README b/apps/tosthreads/capps/SenseStoreAndForward/README index f2a9f11f..75d1e979 100644 --- a/apps/tosthreads/capps/SenseStoreAndForward/README +++ b/apps/tosthreads/capps/SenseStoreAndForward/README @@ -26,7 +26,7 @@ starts running, the entire contents of the flash drive are erased. 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 diff --git a/apps/tosthreads/capps/TestCollection/README b/apps/tosthreads/capps/TestCollection/README index 8b3e7306..1d306767 100644 --- a/apps/tosthreads/capps/TestCollection/README +++ b/apps/tosthreads/capps/TestCollection/README @@ -11,7 +11,7 @@ the Java "Oscilloscope" application found in the the TestCollection/java 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 cthreads install Valid platforms are currently: tmote, telosb, mica2, and micaz @@ -44,7 +44,7 @@ TestCollection/java subdirectory and type: # 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. diff --git a/apps/tosthreads/capps/TestPrintf/README b/apps/tosthreads/capps/TestPrintf/README index 2c6df51a..46106b08 100644 --- a/apps/tosthreads/capps/TestPrintf/README +++ b/apps/tosthreads/capps/TestPrintf/README @@ -4,11 +4,11 @@ Author: Kevin Klues 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 cthreads install Valid platforms are currently: tmote, telosb, iris, mica2, and micaz diff --git a/apps/tosthreads/capps/ThreadStress/README b/apps/tosthreads/capps/ThreadStress/README index 914818a4..ce519719 100644 --- a/apps/tosthreads/capps/ThreadStress/README +++ b/apps/tosthreads/capps/ThreadStress/README @@ -10,14 +10,14 @@ completion. Three different thread start functions are used, each toggling one 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 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. -- 2.39.2