ME 462 - Microcomputer Interfacing - Fall 1995 by 5v4CW8


									                                 ME 445 - Microcomputer Interfacing – Fall 2012
Faculty:       H.J. Sommer, 337 Leonhard, 863-8997,,
TA:            Michael Robinson, – hours MWF 3:30 to 5:00, R 9:00 to 11:00, 3:30-5:00
Lecture/Lab:   151 Willard, 2:30-3:20 M W F / 339 Reber, 863-5773, open lab
Text:          none
Grading:       labs 60, homework 70, quiz 50, project 50 (approximate)

M   Aug 27     review, administration, Arduino
W   Aug 29     binary numbers
F   Aug 31     Arduino programming language

M   Sep 3      NO CLASS – Labor Day
W   Sep 5      2’s complement, floating point
F   Sep 7      resistors, capacitors, inductors, transformers

M   Sep 10     diodes, LED, Zeners, regulators
W   Sep 12     transistors                                                   Lab 1 due, Arduino
F   Sep 14     Darlingtons, opto-isolators                                   Quiz 1

M   Sep 17     combinational logic
W   Sep 19     TTL gates                                                     Lab 2 due, safe I/O
F   Sep 21     TTL chips, tri-state, bidirectional

M   Sep 24     sequential logic
W   Sep 26     flip-flops, latches, counters
F   Sep 28     MUX, decoders, shift registers                                Quiz 2

M   Oct 1      Schmitt trigger, comparators, multivibrators
W   Oct 3      op-amps, inverting, non-inverting                             Lab 3 due, TTL A/D
F   Oct 5      AC analysis, frequency content

M   Oct 8      sum, integrate, differentiate, track/hold
W   Oct 10     filters
F   Oct 12     filters                                                       Quiz 3

M   Oct 15     VCVS filters
W   Oct 17     power drivers, FET, SCR, triacs                               Lab 4 due, op-amps
F   Oct 19     motor control

M   Oct 22     stepping motors
W   Oct 24     thermocouples, thermistors
F   Oct 26     strain gages, piezoelectric, Hall effect

M   Oct 29     optical encoders, counter/timers
W   Oct 31     impedance loading, noise, grounding                           Lab 5 due, motors
F   Nov 2      PID control                                                   Quiz 4

M   Nov 5      D/A converters
W   Nov 7      A/D converters
F   Nov 9      digital sampling

M   Nov 12     DFT
W   Nov 14     FFT                                                           Lab 6 due, noise
F   Nov 16     digital filters                                               Quiz 5

M   Nov 26     digital filters
W   Nov 28     V to F, F to V
F   Nov 30     RS-232/422/485

M   Dec 3      USB, IEEE 1394, modems, 4-20 mA
W   Dec 5      Centronics, IEEE-488
F   Dec 7      system architecture

M   Dec 10     bus control
W   Dec 12     assembly language
F   Dec 14     interrupts, DMA

?   ???        project presentations at ??? in 339 Reber
Course Objectives
1. Analyze, design and build analog DC and AC circuits using resistors, capacitors, inductors, diodes, transistors and op-amps
2. Analyze, design and build digital TTL circuits
3. Build and trouble-shoot analog and digital circuits connected to single chip microcontrollers using prototype wiring and
        printed circuit board layout
4. Interface common transducers and actuators to microcontrollers
5. Filter, digitize and analyze electronic signals using analog anti-aliasing filters, A/D converters, FFT and digital filters
6. Understand and connect computer peripherals using standard interfaces (RS-232, USB)
7. Communicate well using verbal, written and electronic methods

Course Policy
1. Attendance at lectures is mandatory.
2. Homework problems and quizzes are strictly individual assignments. No collaboration is allowed. One 8½x11 study sheet
        is permitted during quizzes.
3. Lab work should be done in teams of two. Both partners are expected to participate in, and understand all lab work.
        Breakdown of responsibilities is up to lab partners. A lab report must be submitted for each lab.
4. Students should know and understand these course policies in regard to College of Engineering policy on academic integrity
        available at .

Lab Policy
1. The lab is open whenever Reber Building is open. On average, you will need 8 hours per week to complete the labs. Each
         lab team will be assigned a lab station for the duration of the semester.
2. Each lab group will be required to propose and complete a hardware project. Begin planning your project early in the
         semester so that any required hardware can be ordered.
3. NO smoking, eating or drinking in the lab.
4. Do not remove any manuals, hardware or software from the lab without explicit permission of the TA.
5. Backup all your work. We assume no responsibility for hard disk failures or viruses.
6. You are responsible for the tools, hardware and manuals at your workstation. They have been marked corresponding to
         stations and will be checked at the end of the semester. Please help us insure that next semester’s class has an equally
         well equipped place to work.
7. Only students registered for ME 445 should be using the lab equipment.

Project Information
The latter half of the semester will be devoted to building, debugging, and demonstrating a project utilizing the concepts learned
in this course. The Internet is an excellent source for ideas and circuits. In addition, many old project reports have been bound
and are available in the lab. Be creative and take some risks. The project does not necessarily have to function perfectly to
receive an A.

Examples of past projects
   Home control system (security, intelligent thermostat, lighting control, stereo control, remote control using telephone)
   Robot interface to computer
   Autonomous vehicle
   Automated test system, or data acquisition system

Project Schedule
1. Preliminary proposal: This will enable us to give you suggestions and assess the potential success or failure of your project.
          One page description.
2. Final proposal: 2-4 pages, word processed, with high quality figures describing:
     a. objectives, justification, description
     b. software required, preliminary flowchart
     c. hardware required, preliminary schematic, parts list, including vendor and price (try to use parts we already have)
     d. schedule
3. Final report: detailed, self-explanatory, high quality, technical report.
4. Seven minute oral presentation during final exam week.

Penn State welcomes students with disabilities into the University's educational programs. If you have a disability-related need
for reasonable academic adjustments in this course, contact the Office for Disability Services (ODS) at 814-863-1807 (V/TTY).
For further information regarding ODS, please visit the Office for Disability Services Web site at

In order to receive consideration for course accommodations, you must contact ODS and provide documentation (see the
documentation guidelines at If the documentation supports the
need for academic adjustments, ODS will provide a letter identifying appropriate academic adjustments. Please share this letter
and discuss the adjustments with your instructor as early in the course as possible. You must contact ODS and request academic
adjustment letters at the beginning of each semester.
General Lab Report Requirements

Basic Report Philosophy
Your report should be a complete, self-standing document which completely describes your work and would enable someone else
to repeat your results.

Basic Format
1. Title Page - Lab title and number, group number and names, date
2. Objective - Describe the purpose of lab in one or two paragraphs
3. Procedure - Step-by-step procedure including flow charts, logic diagrams, circuit diagrams and complete truth tables where
4. Results and Discussion - Discuss your results, answer all questions, refer to figures and tables by number
5. Conclusions and Recommendations -
     a. Summarize your results and what was accomplished
     b. List your recommendations/suggestions for changes to lab
     c. List any hardware or computer problems which might need repaired
6. Appendices - Well-commented program listing, lengthy tables, anything which is too big or boring to put in report body

General Requirements
1. Use word processor and computer graphics wherever possible.
2. Number all pages.
3. Every figure and table must have a caption and a number, and must be referred to in the text.

Program Listing.
1. Header includes: name, program name, revision dates, program objective
2. Place comments before each program block and within all appropriate lines.

Circuit Diagram
1. Must contain enough information for someone to duplicate your circuit.
2. Consult textbook for proper drawing of circuit diagrams.
3. Use CAD.
4. Specify all component numbers.
5. Show pin numbers on chips.
6. Pin #1 should always be in the upper left hand corner.
7. Show all wire connections (see figure to right).
8. Specify values for all resistors and capacitors.                                  no connection              do not
9. Specify A/D converter channel numbers.                                                                       do this
10. Put positive voltage supply on top of diagram. Put negative supply and
          ground on bottom.

Lab Development Tips

Divide and conquer - hardware then software
Draw schematic first - then build
Plan component location
Be neat - use colors
Use bypass capacitors
Turn off protoboard before adding or removing components
Use proper tool to remove ICs
Connect GNDs together
Comment every program line
Use descriptive name for variables and labels

Do Not:
Plug and pray
Use same microprocessor pin as input and output
Connect +15V (or –15V) (or +5V) directly to GND
Connect two +5V supplies together in parallel
Touch pins with fingers (ESD)
Use fingers or screwdriver to remove ICs

To top