Mote Connectivity Daniel Dai Igor Ganichev Valerie Ishida
- Slides: 7
Mote Connectivity Daniel Dai Igor Ganichev Valerie Ishida Ashik Manandhar Peter Martinazzi
Testing • • 3 motes Soda Windows lab Pinged motes from linux/each other ping FF 02: : 1 from 1 mote returned 19/20 pings
• Link local – “fe 80: : /10 — The link-local prefix specifies that the address only is valid in the local physical link. This is analogous to the Autoconfiguration IP address 169. 254. 0. 0/16 in IPv 4. “ – IPv 6, Wikipedia 1/31
Measurements
Distance Avg RSSI Avg Time (10 samples) Touching near router -25 d. Bm 21. 2 ms 1. 3 stick apart -41. 9 d. Bm 20. 4 ms 2. 6 sticks -49. 9 d. Bm 22. 9 ms 10 sticks -52. 2 d. Bm 24. 2 ms Right next to router -13. 7 d. Bm 18. 2 ms Touching across room from router -3. 0 d. Bm 21. 3 ms Touching out in hallway -5. 0 d. Bm 22. 7 ms Windows lab to 310 Soda 1) -7. 4 d. Bm* 2) 69. 7 d. Bm 1) 23. 5 ms* 2) 21. 4 ms * When we tested far away we sometimes got really bad outliers (~1000 ms ping), which we omitted in the average
Extending Connectivity • Test Hypothesis: Use a third mote to propagate the ping between far away motes • Test Result: Failure. Only 1 ping got through in ~8 s
OS Networking API • • Reprogrammed motes with echo client Worked great Web service from existing programs Compiled Linux TCP client to utilize echo service • Added loop for repeated/multiple requests
