Embedded Control Fall 2007 Lab and TA Schedule
| Time | Mon | Tues | Wed | Thurs | Fri | Sun |
| 08:00 AM | JL LZ PG SH | JL LZ PG SH | ||||
| 08:30 AM | ||||||
| 09:00 AM | JL LZ PG ZX SH | JL LZ PG ZX SH | ||||
| 09:30 AM | ||||||
| 10:00 AM | JL LZ PG ZX PJ | JL LZ PG ZX PJ SH | ||||
| 10:30 AM | ||||||
| 11:00 AM | PJ PG SH | PJ PG VP SH | ||||
| 11:30 AM | PJ PG LZ SH | PJ PG LZ VP SH | ||||
| 12:00 PM | BNC RC AD XP | PJ BC LZ PG SH | BNC RC AD XP | PJ BC LZ VP PG | ||
| 12:30 PM | PJ BC LZ SH | PJ BC LZ VP | ||||
| 01:00 PM | ||||||
| 01:30 PM | ||||||
| 02:00 PM | BNC RC GA BA XP | BNC RC GA BA XP | ||||
| 02:30 PM | ||||||
| 03:00 PM | DF ZX GA BA ED | DF ZX LZ BA ED | ||||
| 03:30 PM | ||||||
| 04:00 PM | VP AD | JL DF ED | JL AC | |||
| 04:30 PM | DF ZX LZ GA BA ED | |||||
| 05:00 PM | DF ZX GA ED | VP DF AD | JL DF ED AC | DF ZX GA ED | ||
| 05:30 PM | DF ED AC | ZX GA ED | ||||
| 06:00 PM | DF PJ GA | VP DF | GA AD | JL AC XP | ||
| 06:30 PM | DF PJ | |||||
| 07:00 PM | DF VP AC | JL BA XP | ||||
| 07:30 PM | JL VP AC | |||||
| 08:00 PM | ||||||
| 08:30 PM |
| Jianfang Liu JL | Bow-Nan Cheng BNC | Vipindas Pala VP | Andrew Cremins AC | Section 1 |
| Lei Zhang LZ | Rose Craft RC | Prashant Garg PG | Sean Henley SH | Section 2 |
| Ben Clough BC | Dan Farrow DF | George Ahunov GA | Eric DeFelice ED | Section 3 |
| Piyushee Jha PJ | Zheng Xue ZX | Alex Duff AD | Xavier Perez XP | Section 4 |
| Names in bold are the grading TAs for that section | Brent Abbott BA | Open Shop | ||
Embedded Control - Course Syllabus and Policies
- Staff
- Location
- Objectives
- Textbooks
- Grading
- Late Policy
- Attendance Policy
- Lab Equipment
- Computers
- Questions/Problems
- Academic Dishonesty
- Lab Partner
Staff
- Professor Miki Fukunari, Course Instructor (Sec 1, 3)
- Professor Schoch, Course Instructor (Sec 2)
- Professor Embrechts, Course Instructor (Sec 4)
Course Administration Office Hours: By appointment (send email to Professor Schoch
Location:
JEC (JONSSN) 4201 - Core Engineering Studio Laboratory
Course Objectives
On completion of this course, the student will:
- Be able to design interface hardware and software to sense, display, command, and control simple engineering processes.
- Be able to write software for a real-time embedded control system.
- Be able to prototype, debug, and implement the hardware for an embedded control system.
- Understand the basic operation of microprocessors and their role in embedded control systems.
- Understand the role of sensors and actuators and how they are applied to systems.
- Understand and be able to use the laboratory measurement instruments and tools required to build these systems.
Texts
- Required - Embedded Control Lab Manual v11.3 ($20.00)
- Recommended
- Programming With C, Schaum's Outlines.
- C, The Pocket Reference
Grading
Your grade will be based upon the numerical score you obtain according to the grading criteria listed in the table below.
You must submit ALL of the laboratory reports, to receive a passing grade for the course.
Grading Policy
Late Policy
Homework assignments are due at the beginning of the lab period. Lab reports are due by the date shown on the schedule for your particular section. All late lab reports and technical memos will be discounted 20% per school day for lateness.
Attendance Policy
Attendance is required for all scheduled sections unless you are told otherwise. If for any officially approved reason you cannot make it to lab, you should inform your TA in advance, and make arrangements to work in the lab at another time. You will have to provide documentation of this fact to your TA (e.g., a note from your doctor).
Lab Equipment
A student ID or other identification will be required to sign-out equipment for use during the lab session. Please be considerate of others by taking good care of the lab equipment provided for you. Carelessness that results in equipment damage can affect the grade received in this course.
Computers
When you bring a file into the lab on a disk and wish to edit or compile the file, first copy it from your floppy onto the computer's hard drive before you work on it. There are two very important reasons you should do this:
First, if the editor/compiler program works directly from the floppy disk, you'll waste a lot of time waiting for the computer to read/write to the floppy, especially if you try to compile your C programs directly from there.
If you compile from a floppy disk, since the process of compiling is extremely disk I/O intensive, the floppy disk itself will wear out, probably sometime mid-semester when you've written some of your best C code, and you won't be able to access some or all of your files.
Always make backups of your programs, and save your work frequently. Moreover, since the hard disks in the lab will be erased regularly, after working on one of the lab computers, copy any files that you have developed during the lab session from the hard disk onto your floppy disk or to your RCS account before you leave the lab. Finally, you should not leave any of your program files on the hard disks in order to prevent others from copying them.
Questions / Problems
Teaching assistants are in the lab to guide you in the right direction and to clarify the assignments if necessary. They are NOT a substitute or alternative to completion of the reading assignments, multimedia tutorials, and attendance of the sections. Nor are they to do your lab work for you. If you have a question, first look in the lab and course resource information, and if you still cannot find the answer, then ask the TA. If you have a problem that your TA cannot resolve or have a disagreement with the TA, then you should bring it to the attention of instructors.
Academic Dishonesty
Academic dishonesty is a very serious matter, and we suggest that you read the remainder of this statement carefully:
Student-teacher relationships are built upon trust. For example, students must trust that teachers have made appropriate decisions about the structure and content of the courses they teach, and teachers must trust that the assignments which students turn in are their own. Acts which violate this trust undermine the educational process.
The Rensselaer Handbook defines various forms of Academic Dishonesty and procedures for responding to them. All forms are violations of the trust between students and teachers. Students should familiarize themselves with this portion of the Rensselaer Handbook and should note that the penalties for plagiarism and other forms of cheating can be quite harsh.
Any portion of work handed in that is not your own, should cite the author. Just as you would not write a history paper by copying text from the encyclopedia, you should not take credit for another person’s engineering work.
Collaboration on assignments is both allowed and encouraged between lab partners. However, having one partner always work on hardware aspects and the other on the software will be detrimental to both partners. Both partners should understand and participate in all aspects of the lab exercises in order to learn the necessary topics that will be required for lab check-off and covered on the exams. Collaboration on assignments is not allowed between lab groups, either within or between lab sections. Turning in similar out-of-class assignments (homeworks or lab reports), which suggest that copying (in part or in total) has taken place, will be considered as academic dishonesty.
The material presented in the course and the equipment and components used in the labs may change each semester. If you receive help from another student who previously took this course, make sure that the information is current and applicable to the work that you are required to perform. DO NOT use or copy assignments from previous semesters. Using out-of-date materials will be considered as academic dishonesty, whether you copied it or were told by a previous student. Please consider any help you receive from outside sources critically and check the information against that in this manual. Also, if you are taking this course again, make sure any work you use from the previous semester is updated to reflect changes in the course. It may be mistaken as academic dishonesty.
Cheating on an exam will be considered as academic dishonesty and will result in a failing grade for the course.
At all times, we reserve the right to take formal action against anyone engaging in academic dishonesty. This action may range from failing an assignment to failing the course, or to being reported to the Dean of Students. If you have any questions about these rules or how they apply to any specific assignment or exam, discuss it with one of the instructors or course administrators.
Lab Partner
You are responsible for finding a lab partner in your section. This is a very important choice for you to make in the course. It should be made on the basis of complementary backgrounds, talents and commitment. Failure of a partner to do their share can be harmful to both partners. Unresolvable problems with your partner should be brought to the attention of your TA.