CSC 453 Software for Wireless Sensor Systems Fall

CSC 453 Software for Wireless Sensor Systems Fall 2013, Section 001 Rudra Dutta

Course Objectives l Learn about sensor networks – – – l Sensors Networks of sensors Programming sensors, networking, distributed sensors Architectural issues Introductory knowledge Assume prior knowledge Operating System concepts – Programming familiarity – l Additional helpful base, not assumed prior, but pick up Networking concepts – Virtual environments – Linux / UNIX system – Embedded systems programming – Copyright Fall 2013, Rudra Dutta, NCSU

Background l l l Curriculum and year Operating System (236) Programming familiarity Networking (401, 402, …) Socket programming Embedded devices Arduino – Beagle. Board X – Raspberry Pi – Any other ARM – l Work experience Copyright Fall 2013, Rudra Dutta, NCSU

Instruction Modes, Work Products l Descriptive – lectures Networking, wireless networking – Sensor networking, applications, network control – l Programming – lectures, demo code Network programming – Sensor reading, communication, control – l Homework assignments Repeat labs, extend – Research literature/websites/blogs, answer questions – l Project Extend labs, explore, design, build – Report, demo – l Final test – Descriptive part of homeworks Copyright Fall 2013, Rudra Dutta, NCSU

You will need … l “CSC 453 class kit” Beagle. Bone Black (A 5 A or compatible above) – Compatible Wi. Fi dongle (Edimax known to work) – Breadboard, standard (400 pin or more suggested) – Power supply (at least 2. 0 Amps) – l Student-owned computing – very helpful Virtual Box – Ubuntu 12. 04 VM – OS-appropriate drivers from BB site – Alternatively, EOS lab machines – l Many BBBK add-on options Sensors, display, battery pack, micro. SD card … – Can choose to buy for individual projects – Copyright Fall 2013, Rudra Dutta, NCSU

Grading l Work Products Homeworks (50%) – Project (30%) – Final Test (20%) – l Homework assignments Include programming – Use Wolf. Ware submit – Copyright Fall 2013, Rudra Dutta, NCSU l Final test – – – Open book, open notes (BYON) Open Internet (only static) Three hours Answer on test provided May attach additional sheets for space if needed Take home ?

Project l Written work products Project proposal (with possible required resubmission) (5%) – Interim report (5%) – Final report (5%) – Work products should be competently written – l Code and demo of realized system (15%) Build instructions (strongly prefer makefile) – Minimal documentation – l Slide pack for final system Copyright Fall 2013, Rudra Dutta, NCSU

Project proposal l Required (graded) – – – l Identify team Brief description of functionality of system Clear description of envisioned final demo Preliminary entity-level design Task/timeline/point person decomposition (for teams) Website for project Project name, team, brief description – Update throughout semester, archive work products – Open to instructor, TAs, class (minimum) – l Receive approval from instructor Mandatory changes may be suggested – Requires resubmission (short timeline: 2 – 4 days) – Copyright Fall 2013, Rudra Dutta, NCSU

Interim and Final Reports l Interim report Completed design – Course corrections, changes if any (justification) – Changes may incur small penalty based on reasonableness – (Much larger penalty if undeclared changes in final) – l Final report Reiterate problem statement, design – Description of experiments, results – Self-contained, correctly sized (paper-level) – Copyright Fall 2013, Rudra Dutta, NCSU

Project Topics l Develop a solution/tool for some specific purpose – l Sensor network related – cannot be simple socket app System oriented Typically requires development – Simply testing somebody else’s code is aiming low – Learn by doing l Topics / platform / framework l Delving deeper in some issue raised by labs – Might start with literature, attempt realization – Some samples will be provided – Copyright Fall 2013, Rudra Dutta, NCSU

Project Teams Individual, or teams (2, 3 or 4) l All mails copied to all team members l – l Failure imposes penalty Work product and grade – per team Individual assessments – confidential to instructor/TA – Well-oiled machines produce high grades for all – Malfunctioning teams (rare) pull everybody down – Broken teams (hardly ever) may cause instructor intervention – Copyright Fall 2013, Rudra Dutta, NCSU

Administration and Communication Wolf. Ware website l Wolf. Ware Message board l Not instantaneous, but regular – Primary means of communicating with instructor – Archived after each major work product – l Office hours – In person Email … l Wolf. Ware submit, Grade. Book l Copyright Fall 2013, Rudra Dutta, NCSU

Support l Teaching Assistants Amlakawit Medhin (Quarter-FTE) – Trisha Biswas (Volunteer – specific tasks and time only) – Unity / VCL computing help l Yourself. l BB and associated websites, videos – Non-affiliated websites, blogs – New platform – effort/benefit tradeoff – Copyright Fall 2013, Rudra Dutta, NCSU