X-Git-Url: https://oss.titaniummirror.com/gitweb/?a=blobdiff_plain;f=apps%2Ftosthreads%2Fcapps%2FTestCollection%2FREADME;h=78ef60037464a80a1408dc934b505084c3faaf5a;hb=0679f08533c8769d7541e0a26610ac8f57fae0b6;hp=1d30676788a1ad5dd81c7e9cb7d4613a64206698;hpb=8b847722be7f26618416942bb57b425391e5e555;p=tinyos-2.x.git diff --git a/apps/tosthreads/capps/TestCollection/README b/apps/tosthreads/capps/TestCollection/README index 1d306767..78ef6003 100644 --- a/apps/tosthreads/capps/TestCollection/README +++ b/apps/tosthreads/capps/TestCollection/README @@ -13,16 +13,16 @@ application. You can install TestCollection on a mote via the following command: make cthreads install - -Valid platforms are currently: tmote, telosb, mica2, and micaz + +Valid platforms are currently: tmote, telosb, mica2, micaz and iris At least two motes must be used by this application, with one of them installed as a base station. Base station motes can be created by installing them with -NODE_ID % 500 == 0. +NODE_ID % 500 == 0. i.e. make cthreads install.0 make cthreads install.500 make cthreads install.1000 - + All other nodes can be installed with arbitrary NODE_IDs. make threads install.123 @@ -50,14 +50,14 @@ change the color used to display a mote by clicking on its color in the mote table. Notes: - By default, the Makefile for TestCollection is setup to run CTP as the + By default, the Makefile for TestCollection is setup to run CTP as the underlying collection protocol. The makefile can be modified to work with MultihopLQI by changing the appropriate include directories. Known bugs/limitations: Warnings are issued about fan out on the 'Snoop.receive' and 'Receive.receive' events. These warnings are harmless and are the result of providing a C based - API in which all events for receiving and snooping must be handled even if not - used by a particular application. The warnings occur because the underlying - CTP or MultihopLQI stacks wire up to particular AM ids, which are also wired - into the C API for handling message reception. + API in which all events for receiving and snooping must be handled even if not + used by a particular application. The warnings occur because the underlying + CTP or MultihopLQI stacks wire up to particular AM ids, which are also wired + into the C API for handling message reception.