EE3376 Final Project
EE3376 Final Project
Final Project - Accelerometers and the Nintendo Wii
The final project spans three weeks and includes a pre-lab in week one, an intermediate submission in the week two and a final submission in the week 3. You will need to show up to lab during your regular hours during all three weeks. All three submissions will be during your regularly scheduled lab hours. During the final week and after demonstrating your functional design, you must also check-out with the professor in his office during your lab time.
Student with smallest s1 record of code that works is exempt from the final with an A in EE3376 and EE3176. The code that is turned in for the design competition can be different than the code turned in for extra credit. The deadline for both versions is the same.
Teams will not be allowed.
This is a design project, and you are expected to do the work. So, unlike previous labs, the TA will NOT be able to answer questions related to your project design. The TA is primarily there for safety reasons and to correct any malfunctions in the hardware or software development environment. The professor will be providing advice, suggestions and guidance in class during the three week period.
Don’t cheat on this project... Don’t even discuss possible solutions... We are hyper-sensitive to copying on this lab and will use a variety of techniques to detect plagiarism - including a script that detects similarities (similarities that you are likely not considering - hidden finger prints), professor/TA inspection, and the results of the oral exam (if you can’t describe how your code works, we’ll assume you didn’t write it). This lab is the essence of EE3376 and EE3176 and is where you will really learn. Don’t be a gallina!!! Step up and engineer something!!!! Otherwise, prepare for a date with the Dean of Students...
You will create a accelerometer system that detect motion in the X and Y axis (forward or backward and left or right on a flat table for instance). The Z axis can be ignored (up and down).
If movement is detected, the LCD will display a message for 2 seconds stating “moved up”, “moved down”, “moved left”, or “moved right”. Motion in the Y direction (up or down) will be prioritized over the X axis.
You must select a threshold at which point you will display a message indicating motion.
Intermediate Checkout - week 2
For the Intermediate Checkout, your code should display the A2D reading of one of the accelerometer axes and display the value in real time on the LCD as an 10 bit unsigned number. Once you are done with this, make sure that the TA signs off that you have completed check-out.
Final Checkout - week 3
For the Final Checkout, you will need a give a printout of your code to the TA. You will also need to be signed in to a computer and have your project and source code files open. With the TA present, build your project and then load and run it on the Dragon12. The TA will check that your entire program works OK, and will also ask some questions about your code to make sure that you understand it. Once you are done with this, make sure that the TA signs off that you have completed check-out.
During the final checkout, you will also need to check out to the professor who will be available in his office during the three lab sections.
Also cut and paste your code and email to firstname.lastname@example.org. Put “Final Project” in the subject line. Only email the main c file please. Nothing more. Do not email to professor’s email address. Failure to complete this step will result in a zero on the assignment or a best a late penalty if emailed the following week.
If you are interested in the design competition, email your small code by the Friday of the week three with a screen shot in which CCS reports the download size. This should be done in addition to the full code email requested above which may include the extra credit functionality. The code for the competition may be different than the submitted code but must fulfill all requirements described above.
The following extra credit points will be added to the final grade of the 3 hour credit EE3376 lecture.
A maximum of 5 points are allowable.
Provide multi-threshold detection and distinguish between fast and slow movement. Messages should include “moved up quickly” or “moved up slowly” for all combinations. - 1 point.
Add a one second buzzer if motion is detected - 1 point.
Use interrupts - 1 point.
Provide a real time acceleration vector combining the readings of the two axes - 3 points.
This would show phase and magnitude in polar coordinates. So at rest, the message would be “0 at 0 degrees”. If it moved to the right, the phase and magnitude might change to “1.2 at 0 degrees”. If it moved up, you might get “0.8 at 90 degrees”. If it moved to the right and up simultaneously, the message might be “1.6 at 45 degrees”. This would be calculated by using some trig and both axes measurements.
Turn in the completed lab (with or without extra credit) one week early for 1 point. If you opt for the early turn in, you are ineligible for the other extra credit the following week. Said another way, the only way to get the full points is to turn in the project with blinking lights and sounds with interrupts in week 2.
You can also try to negotiate an alternative extra credit scheme with a total of 5 points max.