This preview shows page 1. Sign up to view the full content.
Unformatted text preview: ECEL 304 ECE Laboratory IV Summer 2008-2009 Instructor: Dr. Christopher Peters, Electrical and Computer Engineering Office: Bossone 512, Phone: 215-895-6604, Email: firstname.lastname@example.org Prerequisites: ECEl-301, ECEL-302, ECEL-303 Overview Over these ten weeks we will construct and test a digital recording system. Our circuit is similar to a data acquisition system. Its function is to record a portion of an analog signal and then play it back. The circuit consists of an analog to digital converter (ADC) front end, an 128k x 8 RAM chip, and a digital to analog converter (DAC). Associated circuitry includes an on-board timer, address generation, and read/write control. We will supplement the circuit construction with two PSpice simulations which will develop some basic understanding of the circuits involved. This project will take the entire 10 weeks of the term. There are seven steps in the circuit project. Some steps have pre-lab assignments. All steps have tasks and deliverables. A detailed timeline is available on the course web site. Step 1 Review of ADC and DAC Step 2 Building the ADC Circuit Step 3 Build the DAC Circuit Step 4 Introduce Static RAM Step 5 Introduce Control Logic Functionality Step 6 Build the On-Board Clock Step 7 Final Changes Reference Books • The Art of Electronics, Horowitz and Hill, any edition • A Guide to Writing as an Engineer, D. Beer and D. McMurray, Wiley and Sons, 2005, ISBN 0-471-43074-9 Course Web Sites http://www.ece.drexel.edu/courses/ECE-L304 WebCT Vista http:/webct.drexel.edu Course Goals
• • • • • Provide a practical experience in circuit prototyping Integrate analog and digital circuit design concepts Further develop student's OrCAD/PSpice circuit simulation expertise Emphasize the Logic Analyzer as a diagnostic tool Incorporate system-level and scheduling considerations into design Course Format We have a one hour common lecture and a two hour lab period each week of the term. In some cases work will be required outside of the regularly scheduled hours for circuit construction and testing. Lectures will be presented using PowerPoint slides. Copies of the presentations will be placed on the course web site for review. Expectations of Students and Staff What is expected of you? • Mandatory attendance in lab lecture • Mandatory attendance in lab hours o You will work in a group of 2 o You will write one group lab report with the shared data you collected with your lab partner o You will attend the lab section listed on your schedule • Your assignments will be turned in on time • You will maintain a bound lab notebook that will be turned in no later than Monday of finals week. What is expected of us? • We will provide you with the materials and documentation needed to perform the project • We will provide grade feedback on a timely basis. These grades will be available on the course web site. Grading Basis The deliverables for each Step of the project will receive a numerical grade. The grades for steps which involve circuit design and construction will have several parts, including design, functionality (does it work?), quality of construction. Step 5 is a multi-week experiment, and will receive heavier weight. Deliverables are due no later than one week after your scheduled lab meeting. Reports which are late will lose 10% in value per week until four week have gone by, at which time the report will not be accepted. All materials (hardware and reports) must be received by the first day of finals week. After this time, they will not be accepted. Laboratory Notebooks: Your lab notebook will be randomly checked during the term by the lab TA, and examined for completeness. In addition, your lab notebook will be graded at the end of the term for a final grade. Assignment Lab Reports and pre-labs (7) Quizzes (3) Lab Notebook Total Points 750 150 100 1000 Late Policy: All reports are due no later than one week after your scheduled lab meeting. Reports that are late will lose 10% in value per week until four weeks have gone by, at which time the report will not be accepted. All materials(hardware and reports) must be received by the first day of finals week. After this time, they will not be accepted. It is not expected that there will be a grade curve in this course. Grading Matrix: Letter Grade A B C D F Laboratory Notebooks The purpose of a laboratory notebook is to maintain a written record of all your research activities. It is helpful to think of it as a technical diary, in which you record raw data, procedures, questions, descriptions of graphical output, concerns about Grade Points 900 -1000 800 - 899 700 – 799 600 - 699 0 - 599 equipment, etc. The notebook should be a stand-alone document, which means that anyone should be able to pick it up and understand what you did, why, and what you found out. In active research environments, the lab notebook also serves as a legal document to support publications and the patent process, and is therefore a professional document to be maintained in a professional manner. It is unlikely that any new patentable work will be developed in this course; however, it is important to build fundamental lab notebook skills for your future careers. As such, you will keep a lab notebook (a bound notebook allocated specifically for this purpose) containing an outline of each lab, calculations you perform, data you record (or a description of where digital data is stored), and the results and conclusions you draw from a laboratory. Lab Report Submission Lab reports are due by 5:00 PM on Friday the week after you perform a laboratory. You need to submit an electronic copy of the lab report on the course WebCT site in the Assignments section. The files will be uploaded to the Turn-it-in service of WebCT, and are graded electronically. YOU ARE RESPONSIBLE FOR SAVING YOUR SUBMISSION RECEIPT WITH A TRACKING NUMBER. WITHOUT THE TRACKING NUMBER THERE IS NO WAY TO TRACK A MISSING FILE. Students Needing Accommodations Students have the right to receive accommodations if they have registered with the Drexel Office of Disability Services (215 Creese Student Center, 215-895-2506/7) and have submitted an Accommodation Verification letter to their professor. You should arrange a meeting with your professor privately during office hours to discuss your needs. Course Cheating Policy Cheating is taken very seriously in this class. The ECE Department applies the University Policy on Academic Honesty. This policy is published in the Student Handbook. The interpretation for this class is: 1. a first offense will result in zero for the assignment 2. a second offense will result in failure of the course and the inclusion of a letter describing your actions in your permanent Drexel transcript. 3. Any egregious action of cheating will be referred to the Committee on Academic Honesty. Some overall thoughts on cheating: This is the first class where you will be expected to provide individual written reports for work performed in a team. As such, the bounds can be confusing at first, and it is important that you ask questions as they arise so you can learn the proper way to formulate a written technical document. Some specific examples of cheating that were points of confusion in the past include: 1. You and your lab partner write the introduction / theory / conclusions portion together and submit it individually. You may work together with your lab partner, but you should be writing your own report based upon mutual concepts and interpretations. The conclusions you draw may be similar, but the writing itself must be your own. 2. Your lab experiment did not work, so you ‘borrow’ the data/graph/figure from another group and interpret it in your report. Instead, you should see the TA about your issue and see what options are available (e.g using another lab station, rewiring a circuit, getting an extension for hardware failure). 3. You have several friends in the course, and decide to take turns writing the reports and pass them around to each other, then submit them as your own. This sounds unbelievable, but has happened. Do not do this. Please remember that if you are unsure if something is cheating, it probably is cheating. If you are in doubt, see a TA or Prof. Fontecchio and ask if what you are doing is ok. ...
View Full Document
- Summer '09