ECEN 390 - Laser Tag Project

In this milestone you will implement most of the 'C' code that implements the laser-tag system.

Demonstrate the system working with a feedback connection (built into the ECEn Development Board) connecting the output of the transmitter to the input of the ADC. You will demonstrate the ability of your system to:

• detect hits on each of the 10 frequencies,
• no false detects,
• no bouncing of the trigger switch, i.e., register one hit for each push/release of the trigger,
• display the computed power of each of the channels on the TFT with the provided histogram package.

This milestone will be divided into three tasks that will be due and passed off as recorded in Learning Suite.

1. Task 1. Implementation and verification of the FIR and IIR filters (filter.c). Demonstrate all sets of of IIR coefficients.
2. Task 2. Implementation of the transmitter state-machine (transmitter.c), the trigger state-machine (trigger.c), the hitLedTimer state-machine (hitLedTimer.c), the lockoutTimer state-machine (lockoutTimer.c), and the code to compute the power in the output from each IIR band-pass filter.
3. Task 3. Implementation of the detector (detector.c) and integration with all other parts of the project in order to perform the final pass-off for the overall milestone using the feedback provided by the development board.

All of the tasks comprising Milestone 3 are software tasks and must adhere to the coding standard.

Proper adherence to the coding standard contributes 30% to the score of the lab. It might be easiest if you think of your lab as being worth 100 points (pass-off + coding standard adherence):

• Pass-Off: you get 70 points when you pass off a lab that works properly and meets all of the specifications. You can lose points here if you do not implement the lab as required by the specifications.
• Coding Standard: you start with 30 points. You lose 1 point for each infraction of the coding standard. You can only lose up to 30 points for coding-standard infractions. Please read the coding standard for further guidance. Note that I have reduced the points deducted for infractions if you compare this policy with that used in 330.

I have instructed the TAs to mark coding infractions for Task 1 but not to deduct points. Failure to adhere to the coding standard in Tasks 2 and 3 will result in deductions.