| The purpose of the System Schematics is to
summarize the complete paper-based design of your project.
Should someone choose to construct your project's hardware
at this stage of development, they should be able to do so directly
from these schematics without any other sources of information.
These schematics are a living document
in that they will very likely require modification throughout the design
process. At the point of the design proposal submission, the schematics are a "snapshot" of the
the design as it stands after the paper-based design process.
Use Eagle 4.16R2
Please use Eagle version 4.16R2. Although this is not the most recent version, it is the one for which the lab is equipped with a corresponding professional version. The professional version allows, among other things, the design of larger PCBs than the free version of the same. Additionally, when boards are produced using the in-house milling machine, the instruction team is able to use the 4.16R2 files directly, and not the more current versions. Multi-Page Schematics Note that with Eagle Light (the free version of Eagle), a single schematic page corresponds to a single PCB. i.e. If you have more than one schematic page, you will end up with more than one PCB. However, it is possible to use a large page size for a large schematic. You are encouraged to use a page size that will allow for schematics to be clearly presented. Unless your design requires multiple (perhaps modular) PCBs, please use a single schematic. If it turns out that there is not enough room on the PCB for all hardware on the schematic, it is a relatively straight-forward task to divide a large schematic into several that are smaller by appropriate use of cabling and associated connectors. Please be sure to make provision for passing signals between boards, if necessary. This will likely involve the use of (clearly labeled) connectors. The prior discussion notwithstanding, for the purposes of including the schematic in the design proposal (and further documents), you may find that document flow improves if you present portions of the schematic in-text. Doing so will require you to clearly annotate the smaller diagrams such that interconnection is obvious. Grading In the current academic year, schematics are evaluated as part of the evaluation of of the design proposal. However, in prior years, these schematics have been separately submitted and graded. To communicate the expectations with respect to the schematics, the following rubric is provided: Prior Years' Schematic Evaluation Rubric. Please ensure that you review this rubric prior to submission of the system schematics as part of the design proposal. The language used to describe levels of performance for a given criterion was meant to allow the evaluator to take into account the portion of scope covered by the project schematics. Evaluation of each criterion was relative to the performance of the rest of the class. |