| |
ECE65 (Spring 2009)
General Information
This age is being updated. Please review again on Wed.
Description:
ECE65 is a sophomore course in analog/digital circuits. It is designed to built upon
material learned in ECE35 and ECE45 and introduces ECE students to
practical circuits and solving real-world problems. In this course student
will learn to model and design practical circuits using idealized circuit
models, to account for the interactions among various parts of a circuit,
the concept of feedback, and a host of other issues encountered in designing a
practical circuit.
Prerequisites
for this course are ECE35 (ECE45 can be
taken concurrently.)
Material covered in this
course include:
Interaction of sub-circuits
(e.g., Trasnfer function, Input & output resistance)
Frequency Response
Filters
Operational Amplifiers basics
Concept and utility of Feedback
Negative feedback: Linear OpAmp circuits, active filters, etc.
Positive feedback: Comparators, triggers and oscillators
Diodes
BJT transistors
Large signal model, Digital Gates, Biasing, Small-signal models,
Amplifiers
FET transistors
Large signal model, Digital Gates
Circuit Design.
Using PSpice to simulate circuits
(self study)
-
Instructor: Yuan Taur
-
Office: 3801 EBU1.
-
Office hours: MWF 10:00-11:00 at 3801 EBU1 or by Appointment
(Send E-mail).
-
Phone: 858-534-3816
-
E-mail: taur@ece.ucsd.edu
-
I'd like to hear your comments
about the Lab material, my style of teaching, TAs, Lab. Web Site, Lab. report,
and any other subject you want to talk about. Do not hesitate to stop by my
office and/or send me an E-mail.
-
Lab Teaching Assistants
(See also Lab Schedule)
-
Atsushi Ohoka
-
Yu Yuan
-
Lab Report Grader:
-
Yu Yuan
-
Atsushi Ohoka
-
If you want your report to be
regraded, leave the Lab report in the Lab and attach a note explaining the
issue. The grader will review your Lab report. Note that you have only TWO
WEEKS after the return of your report to ask for a regrade.
Text Books:
Lecture Notes:
Lecture notes are distributred on the class Web site (See under "Note" Tab)
Recommended:
"ORCAD PSpice for Windows, Vol. 1: DC and AC circuit," 3rd Edition by
Goody
A detailed primer for using PSpice with the Schematic graphical interface.
Get this book only if you are going to use ORCAD
PSpice. See notes for PSpice for more details.
"Fundamentals of Electrical Engineering," by Bobrow (2nd edition) Oxford
University Press
This is also the text book for ECE53B.
"Student manual for the Art of Electronics" by Hayes & Horowitz
"Microelectronic Circuits," by Sedra and Smith (4th edition) (HRW)
This is also the text book for ECE102.
"Art of Electronics," by Horowitz & Hayes
This book and its companion, "Student Manual for the Art of Electronics"
by the same authors contains a large number of practical considerations
in designing circuits.
The drawback of the book is that it does not include necessary
mathematical analysis. It is best used as a areference.
"Principles & Applications of Electrical Engineering" by Rizzoni
This is text book for ECE20.
Recommended for PSpice programming:
"SPICE for Microelectronic Circuits," by Roberts and Sedra (HRW).
"Spice for circuits and electronics using PSPICE," by Rashid (Prentice
Hall).
"Spice a guide to circuit simulation and analysis using PSPICE,"
by Tuinenga (Prentice Hall)
"The Spice Book," by Vladimirescu (Wiley)
Grades:
The course grade is calculated based on:
| |
 |
Lab reports: |
40% |
| |
 |
Midterm |
20% |
| |
 |
Final: |
40% |
Course Mechanics: The
course material is reviewed in the lecture. Lecture
notes will be distributed (through Class Web site). The description of Lab
exercises for the following week is also posted on the class Web Site. The Lab
exercises are designed to enforce the material covered in the lecture and make
students understand the differences between circuit models and practical
circuits. We analyze many circuits by (1) simple analytical tools, (2) more
detailed PSpice simulations, and (3) Lab measurements. In this way, the
students will understand when various models apply and how to account for
various effects. Each Lab includes a design problem: you are asked to design a
specific circuits, simulate its response with PSpice, built in the Lab and see
if it performs according to design specifications.
An essential part of the course work is PSpice simulation of various circuits.
Lectures will not cover PSpice simulation syntax and students should learn
PSpice on their own. However, Lab exercises are designed to introduce
students to PSpice capabilities gradually. You can purchase commerical versions
of PSpice, download free versions from Web, or use the PSpice Lab (329 EBUII).
(Click here for more info on PSpice)
Lab Teams: Lab work is done by teams of two students. You are free to
choose your own partners, who must be in the same Lab section as you. Teams
should be formed before the first Lab exercise. It is expected that both Lab
partners will contribute equally to the completion of a Lab exercise. Take
turn to be the leader and follower in each exercise. Get together to complete
the Lab report so that both Lab partners fully understand the material.
Lab Preparation:
You have one Lab exercise per week. Student should be throughly familiar with
the Lab exercise before coming to the Lab (or it will take you much
longer to complete the Lab). Each students should bring to the Lab a
complete circuit analysis or PSpice simulation of the Lab exercise i.e.,
you should have calculated all the currents and voltages in the circuit, you
should know which state each nonlinear element is (e.g., if the transistor is
in its active, saturation, or cut-off region), you should know why each element
is in the circuit and why it has the value that it has. If an student does not
bring a complete circuit analysis of the Lab exercise to the Lab, he or she
will not be allowed to do the Lab exercise with all of the ramifications of not
attending the Lab without prior approval.
Lab Reports:
After completeing the Lab exercise, each team should prepare a Lab
report. It is expected that both members of the team cooperate to complete the
Lab report (rather taking turn preapring the Lab reports). The Lab
report should include (for each Lab. experiment):
-
The motivation,
-
Circuit analysis/PSpice
simulations (which you have done before coming to the Lab),
-
Experimental procedure (only if
you had to do something speical to get your data),
-
Data (in tables and plots),
-
Comparison of data with circuit
analysis and simulation,
-
Your Conclusions and
speculations.
Clear presentation of the information is essential. The Lab report should be a
complete description of what you did in the Lab and what you learned from it.
It should be readable and understable by an ECE professional who does not know
about your Lab. Equations and results materializing out of thin air without
explanation are useless even if they were correct. Make sure that you explain
what you are doing. At the same time, do not write long essays. Technical
reports are an essential element of an engineer life. That is how you
communicate with your peers and people working above you. The report should be
coherent and understable so they convey to others that you fully understand
what you are doing at the same time they should not be so long that come across
as boring and stating the obvious.
Lab Reports Page Limit: Lab reports should be maximum of 7 pages
EXCLUDING PSpice simulation results and Plots of experimental data.
More on Lab reports:
a) Lab report should be in order specified in the Web site (i.e., all material
relevant to an experiment should be together).
b) Put your section day/time on the front page of the report.
c) Make sure to draw the circuit and mark curernts and voltages!
d) All numbers should have units. (i=2 is unacceptable, it should be
i=2mA).
e) Don't attach the lab description from the Web site to the lab report.
f) Don't directly copy and paste the PSPICE simulations to a WORD
document. Attach the hard copy print out so the "time stamp" is there and/or
print PSpice simulation to a file and paste the file (with date stamp) to
WORD.
g) Suggestion: Box or clearly mark answers to the questions posed in the Lab
description.
h) Suggestion: If you staple your Lab report together, staple it on the top
left hand corner as it would be much easier to page through and it would not
fall apart easily.
Due Dates and Late Reports:
The Lab. reports are due the following week after each Lab exercise in the
Laboratory. They will be graded and returned to you a week later. Late
reports will not be accepted unless prior premission has been obtained.
Attendance:
Attending the Lab is mandatory. If you cannot attend for any reason,
you must inform the Lab instructor in advance. Failure to attend the Lab
without prior permission will result in a zero grade for that specific Lab.
Missing a Lab is extremely serious since the Labs exercises build upon previous
Labs. No Team will be allowed to start a new Lab exercise until they have
completed and demonstrated a working setup of the current exercise (even if the
student had got a zero for that specific Lab because of the lack of
attendance.) The student(s) who had not attended the
Lab. should complete the exercise in the agreed upon time with the instructor
and submit a separate Lab report (also see, Lab reports, below).
Working in the
Lab, SAFETY FIRST: (click here).
How to work efficiently in the Lab: Click here for some hints.
|
|