make the software ack timeout configurable

[tinyos-2.x.git] / tos / chips / rf2xx / README

diff --git a/tos/chips/rf2xx/README b/tos/chips/rf2xx/README
index 985b79c550021e0fe84f9e5ecc4e834bd67f13a1..35b670702028922a89bfb0a4619e9fce379749fc 100644 (file)
--- a/tos/chips/rf2xx/README
+++ b/tos/chips/rf2xx/README
@@ -43,6 +43,13 @@ If enabled, then the radio driver will print out all received and
 transmitted messages via the DiagMsg interface. This feature is used in the 
 RF230Sniffer appliaction.
 
+TRAFFIC_MONITOR:
+
+If enabled, the TrafficMonitorLayer is included in the stack which keeps
+track of the average number of bytes sent, bytes received, the number of 
+transmission errors, and the number of neighboors. If RADIO_DEBUG is enabled
+then this information is also printed.
+
 typedef TRadio:
 
 The radio stack uses a single hardware alarm/counter. The resolution of 
@@ -59,3 +66,11 @@ RADIO_ALARM_MILLI_EXP:
 The base two logarithm of the number of radio alarm ticks per one 
 millisecond.
 
+SOFTWAREACK_TIMEOUT:
+
+The number of microseconds the driver should wait for a software 
+acknowledgement on the sender side. If your SPI bus is slow, then it will 
+take more time to download and upload the message from/to the radio chip, 
+so you need to increase this wait period. For example, for IRIS->IRIS 
+communication 800 microsec is enough, but for IRIS->TELOS we need 1600 
+because the TELOS in software ack mode is slow to reply with an ack packet.