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 will 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. It is expected that each team will work on a different project. The choice of project (A to I) will need to be submitted via a post in the Google Group that team leaders for Project 3 will make, if two teams select a same project, the team who posted earlier will get the project. Please post two or three choices indicating an order of preference.

Project	Description
A	Predict the max. temp. for the next day using previous thirty days’ temperatures, using polynomial and other models
B	Predict the oil price for next week using previous thirty weeks’ prices, using polynomial (whose order will be an input) and other models
C	Detect the frequency spectrum of a given signal (in wav format) using Fourier Transforms, output the number of frequency components of the signal
D	Say the decimal number for any four-digit binary number
E	Make a 16 keys piano
F	Solve the quadratic equation with distinction of the three cases for the discriminant. Provide solutions including: double roots, different roots, and complex conjugate roots.
G	A VI that inputs sound via a microphone, when the sound amplitude is above certain limit it will display the waveform, replay the sound, save it into a file, and present results of a tone measurement including amplitude, frequency and phase of the signal
H	A VI that will produce and display an html file containing the front panel (with a description of problem solved, inputs and outputs), block diagram, and notes. The html file will be saved as p2p2a.html
I	A VI that produces two or more chirp sounds, that is, a sound whose frequency is changing with time
J	Make a “sound recording utility” that can record voice from a microphone, display it and its FFT, then save it into a file. When a ‘playback button’ is pressed it will play the recorded sound.

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: the cover sheets to be submitted with the team report for Project 3 will include the “Comments and Signatures” and

The “Meeting Log and Task Distribution”

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:

Project meeting log and tasks distribution

Please fill in the following table every meeting, including the date and attending members’ names. The second form should be filled by the team leader.

Date:	Name		Name	Name	Name		Name
Name		Task Assigned				Percentage of Completion

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

Report for team #
Submitted		On time Late
Uploaded electronic copy		Yes No
Project 1 web page		Yes No
Team participation table		Yes No
Report submitted (80)	Progress Report: p3pr.html (5)
	p3p1.html (5)
	p3p2.html (5)
	Introduction Problem solved, equations (20)
	LabVIEW inputs/outputs, Front Panel (15)
	LabVIEW elements: Block Diagrams, Sub-VI’s; Results Testing (20)
	Conclusions (10)
Good writing practices (20)	Grammar and presentation (5)
	Logical arguments and structures (5)
	Accurate, completeness; non-plagiarism (10)
Deduction
Project report total (100)
Project presentation total (200)		Performance and Design (180):
		Web pages Parts I and II (20):
Project 1 total (300)

Grading criteria in Design and Performance

Design: -Front Panel: ergonomic (is it easy for the user to understand what problem your Virtual Instrument is solving, what are the required inputs, if they are numbers what is the range of possible values, what are the outputs, etc.); correct information (for numeric quantities with units, what units are you using for the inputs and outputs, for example if an input is the speed, in what unit should the user enter, miles/h; km/h; m/s?, if an output is the time, what unit is it in, hours, minutes, months, etc.) -Block Diagram: organization, minimum wiring (no wire crossing unless unavoidable), transparency (is it easy to see which wire is connected to which terminal of an operation or sub-VI, is there any wire crossing an operation or sub-VI although not connected to it, etc.) -Requirements: does it have minimum 4 inputs and 3 outputs (Part I) or 5 inputs and 4 outputs and one of your own sub-VI that includes two or more operations that was called in at least twice in the Block Diagram (Part II).

Performance: -Proficiency: how much of the LabVIEW elements introduced in class, and others are being used in your Virtual Instrument -Utility: how useful or practical is the application you developed -Complexity: length of equation used or number of operations or LabVIEW elements used in the Block diagram