Download presentation
Presentation is loading. Please wait.
Published byAlfred Cobb Modified over 9 years ago
1
Prof. Kristofer S.J. Pister’s team Berkeley Sensor and Actuator Center University of California, Berkeley
2
Part VII Integrated Demonstrations Dr. Thomas Watteyne
3
3 wsn.eecs.berkeley.edu
4
4
5
5 AppUdpGina wsn.eecs.berkeley.edu
6
6 AppUdpGina wsn.eecs.berkeley.edu
7
7 AppUdpGina wsn.eecs.berkeley.edu
8
8 AppUdpGina wsn.eecs.berkeley.edu
9
9 AppUdpGina wsn.eecs.berkeley.edu
10
10 AppUdpGina request from port 8080 to port 2190 take one measurement wsn.eecs.berkeley.edu
11
11 AppUdpGina reply (headers) from port 2190 to port 8080 wsn.eecs.berkeley.edu
12
12 AppUdpGina reply (data) sensitive_accel_x sensitive_accel_y sensitive_accel_z3 sensitive_accel_z1 temperature magnetometer_x Magnetometer_y magnetometer_z large_range_accel_x large_range_accel_y gyro_temperature large_range_accel_z gyro_x gyro_y gyro_z
13
13 AppUdpGina wsn.eecs.berkeley.edu
14
14 wsn.eecs.berkeley.edu
15
15 ICMPv6
16
16 wsn.eecs.berkeley.edu
17
17 AppUdpLed wsn.eecs.berkeley.edu
18
18 AppUdpLed to port 2193 0x0e = 0b00001110 red on blue on green on red off wsn.eecs.berkeley.edu
19
19 wsn.eecs.berkeley.edu
20
20 TCP implementation [1/2] Stream-oriented transport protocol – No concept of “packets” – Session establishment between a client and a server – Once established, sessions is bidirectional – Sender has a stream of bytes to send (may be empty) – Receiver announces how many bytes are free in reception buffer – TCP Handles re-ordering/re-transmission if necessary – TCP session can be ended by any end in of the session Needed for HTTP support Corners cut in OpenWSN – Only a single session at a given time (all others refused) – Motes announces windows size depending on packet size, not buffer size: Layer violation But no 6LoWPAN fragmentation needed
21
21 TCP implementation [2/2] wsn.eecs.berkeley.edu
22
22 HTTP-to-the-mote Sits on top of TCP – RESTful architecture dlient/server model Server does not maintain any state Single request/response TCP sessions – Server listens for incoming TCP session requests – Client initiates the connection – Client sends request (text based) – Server sends reply (e.g. HTML page) – Server closes the connection Corners cut in OpenWSN – Server does not parse the GET request, just looks for \r\n\r\n – Server only returns a single static page – Extensions: Trivial if payload <48 bytes Modifying the TCP implementation if more 80 lines of C-code in Linux implements static HTML page server
23
23 HTTP-to-the-mote
24
24 HTTP-to-the-mote wsn.eecs.berkeley.edu
25
25 HTTP-to-the-mote
26
26 wsn.eecs.berkeley.edu
27
27 AppUdpHeli Motor 1 Motor 2 wsn.eecs.berkeley.edu
28
28 AppUdpHeli 100 100 tics @ 32kHz = 3ms 0 programmable threshold counter value time wsn.eecs.berkeley.edu
29
29 AppUdpHeli to port 2192 0x001e=30% on motor 1 0x0029=41% on motor 2 wsn.eecs.berkeley.edu
30
30 AppUdpHeli Preset take- off speed Stop both motors Click to set individual motor Click to set both motors wsn.eecs.berkeley.edu
31
31 OpenHome wsn.eecs.berkeley.edu
32
32
33
Prof. Kristofer S.J. Pister’s team Berkeley Sensor and Actuator Center University of California, Berkeley
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.