[Tinyos-2-commits] CVS: tinyos-2.x/doc/html tep123.html, 1.7,
1.8 tep116.html, 1.6, 1.7 tep124.html, 1.1, 1.2
Phil Levis
scipio at users.sourceforge.net
Wed Feb 28 14:34:24 PST 2007
Update of /cvsroot/tinyos/tinyos-2.x/doc/html
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv15886/html
Modified Files:
tep123.html tep116.html tep124.html
Log Message:
Updated HTML.
Index: tep123.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep123.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** tep123.html 6 Feb 2007 03:45:27 -0000 1.7
--- tep123.html 28 Feb 2007 22:34:19 -0000 1.8
***************
*** 304,310 ****
<tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">3-Aug-2006</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.6</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2007-01-16</td>
</tr>
<tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu></td>
--- 304,310 ----
<tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">3-Aug-2006</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.8</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2007-02-28</td>
</tr>
<tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu></td>
***************
*** 406,410 ****
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
! |C|P| reserved | THL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ETX |
--- 406,410 ----
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
! |P|C| reserved | THL |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ETX |
***************
*** 420,425 ****
<blockquote>
<ul class="simple">
- <li>C: Congestion notification. If a node drops a CTP data frame, it MUST set the C field on the next data frame it transmits.</li>
<li>P: Routing pull. The P bit allows nodes to request routing information from other nodes. If a node with a valid route hears a packet with the P bit set, it SHOULD transmit a routing frame in the near future.</li>
<li>THL: Time Has Lived. When a node generates a CTP data frame, it MUST set THL to 0. When a node receives a CTP data frame, it MUST increment the THL. If a node receives a THL of 255, it increments it to 0.</li>
<li>ETX: The ETX routing metric of the single-hop sender. When a node transmits a CTP data frame, it MUST put the ETX value of its route through the single-hop destination in the ETX field. If a node receives a packet with a lower gradient than its own, then it MUST schedule a routing frame in the near future.</li>
--- 420,425 ----
<blockquote>
<ul class="simple">
<li>P: Routing pull. The P bit allows nodes to request routing information from other nodes. If a node with a valid route hears a packet with the P bit set, it SHOULD transmit a routing frame in the near future.</li>
+ <li>C: Congestion notification. If a node drops a CTP data frame, it MUST set the C field on the next data frame it transmits.</li>
<li>THL: Time Has Lived. When a node generates a CTP data frame, it MUST set THL to 0. When a node receives a CTP data frame, it MUST increment the THL. If a node receives a THL of 255, it increments it to 0.</li>
<li>ETX: The ETX routing metric of the single-hop sender. When a node transmits a CTP data frame, it MUST put the ETX value of its route through the single-hop destination in the ETX field. If a node receives a packet with a lower gradient than its own, then it MUST schedule a routing frame in the near future.</li>
***************
*** 449,453 ****
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
! |C|P| reserved | parent |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| parent | ETX |
--- 449,453 ----
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
! |P|C| reserved | parent |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| parent | ETX |
***************
*** 459,464 ****
<blockquote>
<ul class="simple">
- <li>C: Congestion notification. If a node drops a CTP data frame, it MUST set the C field on the next routing frame it transmits.</li>
<li>P: Same as data frame.</li>
<li>parent: The node's current parent.</li>
<li>metric: The node's current routing metric value.</li>
--- 459,464 ----
<blockquote>
<ul class="simple">
<li>P: Same as data frame.</li>
+ <li>C: Congestion notification. If a node drops a CTP data frame, it MUST set the C field on the next routing frame it transmits.</li>
<li>parent: The node's current parent.</li>
<li>metric: The node's current routing metric value.</li>
Index: tep116.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep116.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** tep116.html 12 Dec 2006 18:22:53 -0000 1.6
--- tep116.html 28 Feb 2007 22:34:19 -0000 1.7
***************
*** 304,310 ****
<tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">10-Dec-2004</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.1.2.11</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2006-06-27</td>
</tr>
<tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu></td>
--- 304,310 ----
<tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">10-Dec-2004</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.6</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2007-02-28</td>
</tr>
<tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu></td>
***************
*** 324,328 ****
TinyOS 2.x as well as the structure and implementation of ActiveMessageC,
the basic data-link HIL component. It also documents the virtualized
! active message interfaces AMSender and AMReceiver.</p>
</div>
<div class="section">
--- 324,328 ----
TinyOS 2.x as well as the structure and implementation of ActiveMessageC,
the basic data-link HIL component. It also documents the virtualized
! active message interfaces AMSenderC and AMReceiverC.</p>
</div>
<div class="section">
***************
*** 507,514 ****
<p>The command address() returns the local AM address of the
node. AMPacket provides accessors for its two fields, destination and
! type. It does not provide commands to set these fields, as they are
! set in the sending call path (see Section 2.3). The <tt class="docutils literal"><span class="pre">setDestination</span></tt>
! and <tt class="docutils literal"><span class="pre">setType</span></tt> commands fulfill a similar purpose to
! <tt class="docutils literal"><span class="pre">Packet.setLength</span></tt>.</p>
</div>
<div class="section">
--- 507,512 ----
<p>The command address() returns the local AM address of the
node. AMPacket provides accessors for its two fields, destination and
! type. It also provides commands to set these fields, for the same
! reason that Packet allows a caller to set the payload length.</p>
</div>
<div class="section">
***************
*** 609,613 ****
//Case 3
! message_t* ptr;
message_t* Receive.receive(message_t* msg, void* payload, uint8_t len) {
message_t* tmp = ptr;
--- 607,612 ----
//Case 3
! message_t buf;
! message_t* ptr = &buf;
message_t* Receive.receive(message_t* msg, void* payload, uint8_t len) {
message_t* tmp = ptr;
***************
*** 813,818 ****
shifting the data payload. This means that the <tt class="docutils literal"><span class="pre">message_header_t</span></tt> must
include all data needed for AM fields, which might introduce headers
! in addition to those of the data link. For example, this is the
! structure of the CC2420 header:</p>
<pre class="literal-block">
typedef nx_struct cc2420_header_t {
--- 812,817 ----
shifting the data payload. This means that the <tt class="docutils literal"><span class="pre">message_header_t</span></tt> must
include all data needed for AM fields, which might introduce headers
! in addition to those of the data link. For example, this is an example
! structure for a CC2420 (802.15.4) header:</p>
<pre class="literal-block">
typedef nx_struct cc2420_header_t {
Index: tep124.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep124.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** tep124.html 9 Feb 2007 21:01:07 -0000 1.1
--- tep124.html 28 Feb 2007 22:34:19 -0000 1.2
***************
*** 304,310 ****
<tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">05-Feb-2006</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.2</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2007-02-09</td>
</tr>
<tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu></td>
--- 304,310 ----
<tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">05-Feb-2006</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.4</td>
</tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2007-02-28</td>
</tr>
<tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu></td>
***************
*** 330,337 ****
compute the routes. Nodes can estimate the quality of the in-bound
link from a neighbor by estimating the ratio of successfully received
! messages and the total transmitted messages. These in-bound link
! qualities are exchanged among the neighbors using LEEP to determine
! the out-bound link qualities. Bi-directional link quality is computed
! using thus learned in-bound and out-bound link qualities.</p>
</div>
<div class="section">
--- 330,337 ----
compute the routes. Nodes can estimate the quality of the in-bound
link from a neighbor by estimating the ratio of successfully received
! messages and the total transmitted messages. LEEP appends in-bound
! packet reception rate (PRR) estimates to packets. Other nodes hearing
! these packets can combine the in-bound PRR values with their own
! in-bound values to compute bi-directional link quality.</p>
</div>
<div class="section">
***************
*** 339,347 ****
<div class="section">
<h2><a id="link-quality" name="link-quality">2.1 Link Quality</a></h2>
! <p>Quality of the link between any two nodes describes the probability
! with which data link layer packets can be received without any
! error. This definition assumes uncorrelated link losses. The link
! between the nodes A and B may have different quality in A to B and B
! to A directions.</p>
</div>
<div class="section">
--- 339,349 ----
<div class="section">
<h2><a id="link-quality" name="link-quality">2.1 Link Quality</a></h2>
! <p>The link quality between a directed node pair (A,B) is the probability
! that a packet transmitted by A will be successfully received by B. The
! bidirectional link quality of an undirected node pair (A,B) is the
! product of the link quality of (A,B) and (B,A). This definition
! assumes independent link losses. It also includes the case when
! the link quality of (A,B) and (B,A) are different; this can occur
! due to local interference or noise.</p>
</div>
<div class="section">
More information about the Tinyos-2-commits
mailing list