The two electronic systems projects are the primary activity of EE 333. They constitute 66% of the total grade for the course. The two projects are set up under the assumption that students have no prior knowledge of printed circuit technology or of many of the details of electronic systems design. The first project is intended to be a "skills building" effort, where the goal is to implement a PCB version of a relatively simple, mostly analog circuit. Once the first project has been successfully completed and some basic PCB skills have been learned, then the second project is intended to push some of the more advanced aspects of electronics systems.
Project documentation and reporting
Both projects have the same proposal and reporting requirements. There are 4 requirements for each — three presentations and a written report.
The descriptions below were written assuming that everyone is working in two-person teams and that the presentations are given during normal lecture times. As discussed in class, you are allowed to work in teams, but it is not required. Also, everyone is invited to give their presentation "live" during class times. However, making a recorded presentation and submitting for on-line viewing is also permissible. The choice of presentation method is up to each individual or group.
The Project Definition presentation serves as the kick-off to the project. The presentation starts with an abstract, which is a one-page outline of the motivation and goals of the project. The abstract should be sent to the instructor as soon as it ready, so that they can know what you have mind for the project and can offer any initial feedback about the scope of the project. In the definition presentation, the team will describe the project goals in general terms, enumerate specific system requirements, lay out a test plan, and provide any preliminary circuits or design details. The test plan is especially important — the team is should think carefully about how the system will be tested to show that works as designed.
The Design Review presentation is given after all of the design and prototyping work is completed, but before the PCBs are sent out for fabrication. The design review presentation should include:
- A complete schematic of the final circuit — you might be able to use the schematic generated during the KiCad layout. (The schematic can be broken into functional pieces and presented on separate slides, if that improves clarity. )
- Design calculations and simulations.
- Results from testing the prototype circuit and comparison with design expectations. (Preface the test results with the test plan given in the first presentation.)
- Discussion of implementation difficulties, existing problems, trade-offs, or modifications from original design.
- A complete Bill of Materials (BOM). The BOM should include costs of the various parts and estimated cost of the PCB.
- Overview of the proposed PCB design. (May need to be presented in "snap shots" that are spread over several slides for better clarity.)
- Photos of prototype circuits. Optional: You can also bring the prototype circuit to "show and tell".
When submitting the DR presentation, the group should also submit their KiCad file with the PCB layout. This presentation will certainly be longer and more detailed that the first presentation.
The Project Completion presentation will be given after system has been built and tested on the PCB. This presentation will be similar to the Design Review, but probably more succinct since the results should be similar to what was previously reported in the DR.
After all project work has been completed, the project team will write up and submit a Final Report, which is essentially a written compilation of the information contained in the three presentations.
GTDT: Presentation 1 (with abstract): pdf | PowerPoint | Keynote
Project 1 requirements
The first project should be mostly analog in nature, and relatively simple in function. An advanced EE 230 project would be about right. (See the project 1 ideas list.)
Every circuit must be powered from a 12-VRMS wall transformer. Thus, the circuit include a peak rectifier to derive a DC voltage from the sinusoid. A battery can also be used as a secondary source, but it not a requirement. If adding a battery, a charging circuit can be included, so that the battery can be charged when the transformer is plugged in.
One or more linear regulators should be included to provide proper DC voltage levels.
The printed circuit board should be made using primarily through-hole parts.
Abstract: Sep 3 (submitted to instructor)
Project description presentation: Sep 10
Design review with PCB files: Oct 8
Final presentation: Oct 22
Final written report: Oct 29
Project 2 Requirements
The goal of project 2 is to make something that is more in line with a modern electronic system using a microcontroller that ties together sensors, actuators, motors, displays, etc. The "requirements" below are all negotiable, but projects should include most of the features listed.
- The system should be based around a microcontroller. The microcontroller — and all supporting circuitry — must be incorporated into the PCB. A recommended microcontroller is the Atmega328 from Atmel / Microchip. This is the controller used in the popular Arduino Uno, and you have a couple of "bare" controller chips in your 333 lab kit. However, depending the computational horsepower needed for the project, you can choose a different controller, either smaller or bigger. Note: You cannot use an Arduino in your final project! You can use an Arduino for prototyping, but the final product must have the microcontroller included.
- Voltage regulation should be done using switched-mode regulators. You can use standard controller chips from the usual suppliers, or you can build your own, if you'd like. As in project 1, power should come from a 12-VRMS wall transformer. (24-V or 6-V transformers could be substituted.) If you want a battery in your system, that can be added as supplemental. Again, this could be a good opportunity to include a battery charging system.
- The PCB should use mostly surface-mount parts. Exceptions are allowed for the microcontroller and the SMPS controller — for those you can use either through-hole or surface mount. During proto-typing, you will probably want to choose through-hole parts for ease of soldering, but the final project should use mostly surface mount.
- You are expected to write your own software to run the microcontroller. Copying some janky code off the internet is not acceptable.
Abstract: Oct 8 (submitted to instructor)
Project description presentation: Oct 15
Design review with PCB files: Nov 19
Final presentation: Dec 10
& Final written report: Dec 10
You choose your projects. Below are some ideas. The list is not all-inclusive. You are welcome to do a project directly from the list. Or you can modify an idea from the list. Or you can come up and idea that is entirely your own. If you are coming up with your own project, be sure to check with Prof. Tuttle before starting on it.
Ideas suitable for project 1 ("Analog" and "easier"):
- Temperature measurement/indicator circuit (from EE 230 project list)
- Active cross-over network (from EE 230).
- Simple function generator (from EE 230)
- Three-color audio frequency color organ. (from EE 230)
- Simple IR remote control. (from EE 230)
- A low-power amplifier for powering desktop speakers. (similar to 230)
- Triple-output adjustable power supply using linear regulators.
- Distortion amplifiers of various types for guitars, etc.
- LED desk lamp with proximity on/off or sonic on/off (clapper).
- Implement a Class-D amplifier, using a through-hole chip from
- Capacitance meter (might require a microcontroller).
- Inductance meter (might require a microcontroller).
- Headphone noise canceling circuit
- ESR (equivalent series resistance) for checking electrolytic capacitors.
- Universal battery tester/charger.
Ideas suitable for project 2 ("Digital" and "harder"):
- Triple-output power supply using SMPS with microcontroller input and display
- Infinity mirror.
- Color organ with digital control.
- A combo R-L-C meter.
- "Simon Says" game (or many other kinds of games)
- Bicycle speedometer
- Synchronized bicycle wheel lights
- Smart thermostat
- Pulse oximeter for measuring heart rate and blood O2 levels.
- Weather station
- In-line power meter for measuring power usage in appliances, etc.
- Any sort of environmental monitoring.
- micro-controller based noise canceling
- Class-D amplifier built from scratch
- Discrete component hig-power audio amp
- total-harmonic distortion measurement device
- transistor tester (poor man's parameter analyzer)