Engin 103

Project 3

Developing Virtual Instruments for a Client

As with Project II, developing a Virtual Instrument consists of the following steps: 1) Define the problem you want to solve, specify what will be the inputs and the outputs. 2) Determine the equations or operations needed to produce the outputs from the inputs 3) Implement the controls and indicators and graphs in the Control Panel and the operations in the Block Diagram 4) Fix any error and implement modifications as needed 5) Test the final results against expected theoretical values.

In this project, the client defines the problem, which you can choose from the list below. You are required to work with your team to develop one Virtual Instrument to be presented during Day 1 and Day 2 (check e-syllabus for dates). After the first presentation, the client may suggest one or more modifications on your VI, which you and your team need to work on and present the revised version in Day 2. Working with your team is required for receiving credits from the projects, observing timelines set by the team leader assures successful completion of the project. The choice of topic will need to be submitted on April 22.

Project	Description
A	Predict the max. temp. for the next day using previous days’ temperatures, using polynomial and other models
B	Predict the oil price for next week using previous weeks’ prices, using polynomial and other models
C	Detect the frequency spectrum of a given signal using Fourier Transforms
D	Say the decimal number for a four-digit binary number
E	Make a 8 keys piano
F	Solve the quadratic equation with distinction of cases for the discriminant
G	A VI that can calculate the areas of 4 different geometrical shapes
H	A VI that produces interesting sounds from the combination of 2 or more sine waves with different frequencies
I	A VI that produces a chirp sound, that is a sound whose frequency is changing with time

Each team will do a 5 minute presentation on their VI’s in each of the two presentation days. The webpage on the project, along with the project report will be due the class after the second day of the presentations (please check the e-syllabus for exact dates). The team leader will meet with the instructor to discuss team progress on the project on a weekly basis. The project report is expected to be a good written document (see Good Writing Practices), and graded under three categories: correct grammar and neat presentation; logical arguments and structure; accurate report of the team project, completeness, and no plagiarism. Project report will be submitted in hardcopies with member signatures and also in electronic form (Word files) to the team folder. A complete report should include the following sections:

-Introduction: brief description of project objectives in your own words, background information needed for the design of the VI, work distribution among the team members, and timelines for the different parts of the project: research, design, coding, testing/debugging.

-Design and building: this section should the Front Panel and Block Diagram with explanation on why different elements have been used and placed that way.

-User Manual and Trouble Shooting: should explain in details how to use the VI, with specific examples, and how to trouble shooting common errors

-Conclusion: overview of the team achievement and lections learned for the future.

Team leaders: please copy the table below, fill it out and submit with the team report for Project 3

Engin 103 Project # 3 Report for team # ____ Submitted by ____________________ (team leader) Today’s date is ______________
Team leader: Please comment on these teamwork elements: communication, organization, and participation while you and your team were completing Project 2. In one paragraph, make a self- evaluation for your team as compared to other teams in the class, and to the team performance in the previous Project. Describe any recommendation you would like to make for your team.
Members	Signatures
Leader:
Member:
Member:
Member:

Team leaders will upload the Word file pr3_XX.doc to the team folder and submit a signed hard copy on or before the report due date. There will be no individual report required for this Project. Grades will be computed as follows:

Items			Points
Project completed and presented			70
Project performance (perform tasks specified)			50
Good design			30
Project presentation and webpage			50
Written reports	Report submitted		70
	Project report: will not accepted without all member’s signatures on percentage of participation	Grammar and presentation	10
		Logical arguments; structure	10
		Accurate and complete	10
Total project grade			300