From SOSwiki

(Difference between revisions)
Jump to: navigation, search
(Assignment 1 : Due Friday, March 30, 2012 at 10:30)
(Design of Automatic Control Systems)
Line 6: Line 6:
* Instructor: [[User:Klavins|Eric Klavins]
* Instructor: [[User:Klavins|Eric Klavins]
* Teaching Assistant: Justin Tran
* Teaching Assistant: Justin Tran
 +
 +
== Course Structure ==
 +
 +
Design of Automatica Control Systems (EE/AA 449) is a capstone engineering course in which small groups of students (usually 3) work for 10-11 weeks to build an automatic control system. In the past, students have built robots and robot parts; UAVs (blimps, helicopters); automated biology lab equipment; scientific test equipment; etc. Groups are required to have a ''customer'' -- that is, some entity that to some extent defines the specifications of the project and who will actually use the system when it is built. Students are required to (a) report daily work in online "lab notebooks", present brief progress reports weekly, present completed projects at the end of the quarter and in a written report, and give a demo of the project to the customer and the teaching staff at the end of the quarter. Projects can be funded by any means -- although often the most successful projects are those in which the group has aligned itself with a research lab on campus that needs a new piece of equipment or capability.
== Assignment 1 : Due Friday, March 30, 2012 at 10:30 ==
== Assignment 1 : Due Friday, March 30, 2012 at 10:30 ==

Revision as of 17:14, 26 March 2012

Design of Automatic Control Systems

  • EE/AA 449
  • MWF 10:30-11:20
  • THO 325
  • Instructor: [[User:Klavins|Eric Klavins]
  • Teaching Assistant: Justin Tran

Course Structure

Design of Automatica Control Systems (EE/AA 449) is a capstone engineering course in which small groups of students (usually 3) work for 10-11 weeks to build an automatic control system. In the past, students have built robots and robot parts; UAVs (blimps, helicopters); automated biology lab equipment; scientific test equipment; etc. Groups are required to have a customer -- that is, some entity that to some extent defines the specifications of the project and who will actually use the system when it is built. Students are required to (a) report daily work in online "lab notebooks", present brief progress reports weekly, present completed projects at the end of the quarter and in a written report, and give a demo of the project to the customer and the teaching staff at the end of the quarter. Projects can be funded by any means -- although often the most successful projects are those in which the group has aligned itself with a research lab on campus that needs a new piece of equipment or capability.

Assignment 1 : Due Friday, March 30, 2012 at 10:30

  • Group membership
  • Brief project description including (1-2 Google Docs Slides)
    • Aim of the project
    • Description of the customer
    • Funding and budget
    • Plan / quarter schedule
  • A Google Docs collection with
    • A "lab notebook" for each group member
    • Your project description
    • Eventually all presentations and reports will go here