ChiYu Li

1
LAB5 Routing

• ChiYu Li
• 2008/12/15

2
Lab5 Routing

• Build a simple network
• One node is a coordinator that has a node id 0
• Other nodes also have their own node ids
• Ex 1, 2, 3,
• Each node periodically broadcasts a packet with
  its id
• Each node will use neighbors broadcasting
  packets to choose a neighbor to be its parent
• Each nodes parent has the smallest id among its
  neighbors
• Each node regularly transmits a packet with its
  id and parents id to the coordinator
• The coordinator shows its receiving packets
  through HyperTerminal

3
Lab5 Routing

• After finding a parent
• Each node use LEDs to display its parents id
• Packets forwarding
• When each node connects to this simple network
• It will regularly send a packet to the
  coordinator relayed by its parent
• This packet will contain the node id and its
  parent id
• When each node receives a packet
• If it is not the network coordinator, simply
  forward this packet to its parent
• Else, display this packet information on the UART

4
Demo Scenario
Coordinator node 0 (Through HyperTerminal) 1.
The packets broadcasted by node 1 and 2 - node
id 2. The packets from node 1, 2 and 3 - node
id and parent id
Endpoint node 1, 2, 3 1. Each nodes LEDs show
its parent ID
0
0
0
2
1
2
1
1
3
3
3
2
3
70
20
10
5
Demo Scenario

• Bonus (10)
• You can use the coordinator to send information
  to other sensor nodes
• Using the coordinator to control leaf nodes LEDs
  through HyperTerminal

0
0
2
1
2
1
6
Lab5 Routing

• Tips
• Periodical transmission Tick Timer CallBack
  Function
• A node can both associate with others and accept
  association
• Multiple leaf nodes Multi-connection
• Broadcasting address is 0xffff
• Two nodes cannot have the same u16ShortAddress in
  a network

7
Lab5 Demo

• Each group has to share Zigbee nodes with another
  group, but each group demo its work by itself.
• Due date Tuesday 1/6/2009
• Demo 1430 1630
• Please email your source codes to
  lichiyu.cis93g_at_nctu.edu.tw before 1630
• The delayed work isnt allowed