DIGF 6B21 Ubiquitous Computing

Transcription

1 DIGF 6B21 Ubiquitous Computing NUMBER OF CREDITS: 1.5 Day and Time: Tuesdays 18:30 21:30, beginning October 30th Location: Room 7301, 205 Richmond Professor: Nick Puckett COURSE DESCRIPTION: As the cost of microcontrollers steadily decreases, intelligent devices have become more pervasive and diverse. Computing is no longer relegated to the familiar forms of input and display, and this course seeks to push the limits of this by developing composite systems of material and electronic intelligence. Using current methods of digital fabrication such as 3d printing and laser cutting, students will transform generic electronic components into highly specific computing devices. These devices will be designed for a specific site on campus to ultimately alter the way it is perceived, occupied, or used. Context Life at 16Mhz: computing SansLaptop A typical Arduino has a processor running at 16Mhz and has a memory capacity of 32KB, by contrast a typical laptop operates at around 3200Mhz with KB of memory. This course introduces the methods for designing and prototyping elegant standalone devices that do not rely on the brute force of laptops. Operating in this realm of low cost and low power presents both challenges and potentials. You must think strategically and creatively about the relationship of the digital and material intelligence of your design to maximize its overall impact. More about the course During this course you will be working in teams of 2 to design and produce a standalone computing device for a specific site at OCAD that does not rely on a screen for the display of any information. To achieve this you will conduct parallel strands of research that investigate electronics/hardware and digital manufacturing techniques such as 3d printing, laser cutting, and CNC. Through a series of iterative prototypes beginning on day 1 each team is responsible for producing a device that goes beyond proof of concept. The final devices must consider the integration of electronic systems, material, and form within the overall design. The course will consist of a series of introductions to coding for Arduino, sensor/input typologies, output/actuation typologies, wiring, 3d digital modeling, and 3d printing using the MakerBot

2 Replicator. As the focus in on embedded systems, we will be using the Arduino Pro Mini and Arduino Fio as the development platforms. About the course leader Nick Puckett is the founding director of AltN Research+Design, a design practice focused on creating dynamic links between software, robotics, biological agents, chemical engineering, and material behavior that generate new potentials for the design of intelligent environments. The work of AltN Research has been exhibited in venues including the Venice Architecture Biennale, International Biennial of Contemporary Art of Seville, and the Art Institute of Chicago. The work has also been published in the books including Fabricate: Making Digital Architecture, Hyperlinks, and the forthcoming Inside Smart Geometry. Nick has previously taught within departments of architecture, design, chemical and electrical engineering, and computer science. LEARNING OBJECTIVES AND OUTCOMES: This course uses a hands-on approach to the research and development of your projects. Students are expected to conduct a continuous process of prototyping, documenting, evaluating, and re-prototyping from day1. 1. Iterative Prototyping as as method of design development 2. Successful integration of Electronic and Material systems 3. Development of a computing system that deals with site-specific needs TEACHING METHODS AND DELIVERY: Material in this course will be delivered through lectures, tutorials, presentations, and critiques. COURSE ASSIGNMENTS: Project: Material Computing / Display Each team must develop a finished computing device that alters or augments a site in/around OCAD. The devices should be crafted specifically for the site and the intended use in terms of scale, material, and interaction. The only stipulations are that it cannot rely on a laptop for computing and cannot use a screen for display. Instead, each team must develop both the input and display mechanisms for each device by creating composites of electronics and materials. Depending on your site and needs this can be designed for people to interact with directly or simply monitor and display information pertinent to the place. Though this project has a singular outcome, the development process for this will consist of a series of iterative prototypes and documentation videos. Stage 1 Site/Concepts/Models We will begin this project with a series of introductions to Arduino programming, as well as a survey of various sensing / actuation devices. During this time, each team will be responsible for choosing a site, and producing a series of drawings and a video that describe the aspects that you will be utilizing for your device. Once the site has been chosen, you will also begin testing / documenting your first prototypes. Week 1 (Oct 30) : Introduction to Arduino programming, sensors, and actuators Week 2 (Nov 6) : Presentation of Site Studies, Tutorials

3 Stage 2 Proof of Concept Based on the series of prototypes and tests developed in the first stage, each group will produce a working proof of concept prototype. This prototype should bring together the concepts and technologies to be used, but it doesn t need to reflect the final materials or form. Week 3 (Nov 13) : Arduino session 2, Introduction to 3d printing with the MakerBot Week 4 (Nov 20) : Presentation of Proof of Concept Prototypes Stage 3 Fabrication In the final stage you will take your proof of concept prototype and develop it into a finished, working device. The final device can be created using both digital prototyping and hand crafting, with concern for the integration of the electronic systems into the overall formal and material goals. Week 5 (Nov 27) : Tutorials, working session. Week 6 (Dec 4) : Tutorials, working session. Week 7 (Dec 4) : Presentation of final devices. EVALUATION CRITERIA: Project Stage Due Date Presentation deliverables Weight Focus Stage 1: Site Analysis Nov 6 30 second site video, analysis drawings, and intial models 20% Hands-on research and presentation of specific design criteria Stage 2: Proof of Concept Nov 20 Demo of the prototype. Drawings and diagrams of its intended use. 30% Working prototype and mockup models for final device Stage 3: Finished Device Dec 11 Live demo of the device. 30 second video explaining the device on site. 50% Final, working device that considers the electronic, material, and formal qualities in relation to its intended use. GRADING SCHEME: The following grades are used at the graduate level: A A A B B C F 0-59 P Pass (Summer Off-Campus Only)* I Incomplete** W Withdrawn without Academic Penalty *A grade of P is not used in grade point average (GPA) calculations. **Incomplete work must be completed no later than the end of the following term.

4 Please note that as per Section 5.3 of the Graduate Studies General Policies, students in graduate programs are required to maintain a cumulative grade point average (CGPA) of at least 75% (B+). RECOMMENDED READING: Banzi, Massimo. Getting Started with Arduino. Sebastopol, CA: Make:, Platt, Charles. Make: Electronics: Learning by Discovery. Sebastopol, CA: O'Reilly, Oxer, Jonathan. Practical Arduino. New York, NY: Springer, Margolis, Michael. Arduino Cookbook. Sebastopol, CA: O'Reilly, Robers, Dustyn. Making Things Move. New York, NY: McGraw Hill, REQUIRED RESOURCES: -Laptop -Arduino Mini or Fio -Soldering equipment -wire cutters / prototyping tools LATE WORK All presentations, projects, and papers should be presented and handed in, in a timely manner, as per the course schedule. If for any reason this is not possible, please anticipate and discuss the matter with your instructor. Medical cases which present problems with deadlines require confirmation in writing from a health care professional. Late work is normally subject to a 10% penalty per week, and will be accepted solely by arrangement, and with the discretion of the instructor. INCOMPLETE GRADES An incomplete grade is considered when students encounter unexpected difficulty completing course work within the semester. Students must discuss their situation with their instructor and request an incomplete grade prior to the end of the semester. Incomplete grades are filed at the discretion of the teaching faculty. Students with incomplete grades must complete all course work no later than the end of the following term. ATTENDANCE The university requires that students attend classes on a regular basis and that they participate fully in them. RELIGIOUS OBLIGATION A student who foresees a conflict between a religious obligation and any scheduled class assignments, including the final examination or critique, must notify his/her instructor in writing and in the case of final examinations and critiques must make a written request to the Office of Graduate Studies within three weeks of the first class. ACADEMIC INTEGRITY Students may not re-submit previously graded work without permission, or submit work produced for other courses for evaluation. Plagiarism, misrepresenting personal performance or status and/or any conduct which damages the integrity of scholarly and artistic activity is unacceptable. Academic penalties will result. See the OCAD U Academic Calendar for details.

5 Academic freedom is a fundamental right in any institution of higher learning. Honesty and integrity are necessary preconditions of this freedom. Academic integrity requires that all academic work be wholly the product of an identified individual or individuals. Ethical conduct is the obligation of every member of the University community and breaches of academic integrity constitute serious offences. RESEARCH INVOLVING HUMAN PARTICIPANTS Graduate students who conduct research that involves human participants may require the approval of the OCAD Research Ethics Board prior to the initiation of any such research. For more information on research involving human participants, please visit the OCAD U website at: DISCLAIMER STATEMENT The syllabus, schedule, and course outline may be amended, altered, or changed as the course proceeds. The weekly schedule is open and will be developed in response to the ongoing concerns of the participants. Guest speakers and student presentations will be organized as the term progresses. The class will be notified and when possible, consulted about developments and changes.