60 likes | 163 Views
Dive into the intentionally vague yet coding-heavy Lab 0 of ECE 353. Approach with an abstract design like a finite state machine for project specifications. Remember to check code and wiring thoroughly to avoid frustrations.
E N D
ECE 353Lab 0 MIDI Note Number Display Michael Haines
Lab 0 is: • Intentionally vague; • Mostly coding; • Not the easiest ECE 353 lab.
How to Approach Lab 0and ECE 353 • Start with an abstract design, such as a finite state machine. • Do not forget to include the project specifications in your design. • Bring a pictoral representation of your abstract design, such as a flowchart, to the demo to avoid losing points. • Write code according to the abstract design you create in the previous step. • Check, double-check, triple-check, and keep checking. • Check your code and wiring, as well as your partner’s contributions, until you become intimately familiar with all your team’s work. • This will help you with both debugging and the demo. • Simple mistakes in coding and wiring will be your two greatest sources of frustration in this class.
Make all your power connections with red wire and ground connections with black wire.
Do Not Tie Down Components You may have mistakenly inserted a component upside down, or it may not function properly.
Make Your Wiring Tight • It’s a breadboard, not a spaghetti-board. This is a mess. Note the tight wiring here.