27 | | LETIBEE network comprises nodes spatially distributed in a 2D area, including anchors with known locations and blind nodes to be positioned. Among anchors, one node generally plays the role of network coordinator and sink, whereas the other references are fixed routers. |
28 | | The application protocol is mainly centralised, giving the sink a central role since it has to collect all data to display them on the PC connected to it. |
| 28 | LETIBEE network comprises nodes spatially distributed in a 2D area, including anchors with known locations and blind nodes to be positioned. |
| 29 | Among anchors, one node generally plays the role of network coordinator and sink, whereas the other references are fixed routers. |
| 30 | The application protocol is mainly centralised, giving the sink a central role since it has to collect all data from the different nodes and to deliver them on the PC connected to it. |
39 | | It was decided to port the RIME stack for Contiki v2.4 from SICS onto the LETIBEE node (CEA-Leti based on the Letibee chip, both of them using a 8051 uC). The RIME stack includes the functions for mesh networking including neighbour discovery (and neighbour table construction), route discovery (and routing tables construction) and multi-hop forwarding using the discovered routes. A view of the stack is shown on Figure 2 : RIME network stack. |
40 | | |
41 | | [[Image(rime.png, 80%, center)]] |
| 41 | It has been decided to port the RIME stack for Contiki v2.4 from SICS onto the LETIBEE node (CEA-Leti based on the Letibee chip, both of them using a 8051 uC). |
| 42 | The RIME stack includes the functions for mesh networking including #neighbour discovery# (and neighbour table construction), #route discovery# (and routing tables construction) and #multi-hop forwarding# using the discovered routes. |
| 43 | A view of the stack is shown on Figure 2. |
| 44 | |
| 45 | [[Image(rime.png, 70%, center)]] |