1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7...

44
Expanded “Cookbook” Instructions for the Teradyne Integra J750 Test System Project Plan Team May 07-12 Client ECpE Department Faculty Advisor Dr. Weber Team Members Murwan Abdelbasir, EE. Brent Hewitt-Borde, EE. Jonathan Brown, EE. Robert Stolpman, EE. DISCLAIMER: This document was developed as a part of the requirements of an electrical and computer engineering course at Iowa State University, Ames, Iowa. This document does not constitute a professional engineering design or a professional land surveying document. Although the information is intended to be accurate, the associated students, faculty, and Iowa State University make no claims, promises, or guarantees about the accuracy, completeness, quality, or adequacy of the information. The user of this document shall ensure that any such use does not violate any laws with regard to professional licensing and certification 1

Transcript of 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7...

Page 1: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Expanded “Cookbook” Instructions for the Teradyne Integra J750 Test System

Project Plan

TeamMay 07-12

ClientECpE Department

Faculty AdvisorDr. Weber

Team MembersMurwan Abdelbasir, EE.Brent Hewitt-Borde, EE.

Jonathan Brown, EE.Robert Stolpman, EE.

DISCLAIMER: This document was developed as a part of the requirements of an electrical and computer engineering course at Iowa State University, Ames, Iowa.This document does not constitute a professional engineering design or a professional land surveying document. Although the information is intended to be accurate, the associated students, faculty, and Iowa State University make no claims, promises, or guarantees about the accuracy, completeness, quality, or adequacy of the information. The user of this document shall ensure that any such use does not violate any laws with regard to professional licensing and certification requirements. This use includes any work resulting from this student prepared document that is required to be under the responsible charge of a licensed engineer or surveyor. This document is copyrighted by the students who produced this document and the associated faculty advisors. No part may be reproduced without the written permission of the senior design course coordinator.

Date Submitted10/10/2006

1

Page 2: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

List of Figures...................................................................................................................................2

List of Tables...................................................................................................................................3

Definitions........................................................................................................................................4

1. Introductory Material................................................................................................................5

1.1 Abstract..................................................................................................................................51.2 Acknowledgement..................................................................................................................61.3 Problem Statement and Solution............................................................................................6

1.3.1 Problem Statement..........................................................................................................61.3.2 Problem Solution.............................................................................................................6

1.4 Operational Environment.......................................................................................................71.5 Intended User and Intended Use.............................................................................................7

1.5.1 Intended User..................................................................................................................71.5.2 Intended Use...................................................................................................................7

1.6 Assumptions and Limitations.................................................................................................81.6.1 Assumptions....................................................................................................................81.6.2 Limitations......................................................................................................................8

1.7 Expected End-Product and Other Deliverables......................................................................9

2. Proposed Approach and Statement of Work...........................................................................9

1.7 Expected End-Product and Other Deliverables......................................................................92.1.1 Functional Requirements..............................................................................................102.1.2 Constraint Considerations.............................................................................................102.1.3 Technology Considerations...........................................................................................102.1.4 Technical Approach Considerations.............................................................................112.1.5 Testing Requirements Considerations..........................................................................112.1.6 Security Considerations................................................................................................112.1.7 Safety Considerations...................................................................................................122.1.8 Intellectual Property Considerations.............................................................................122.1.9 Commercialization Considerations...............................................................................122.1.10 Possible Risks and Risk Management........................................................................122.1.11 Proposed Project Milestones and Evaluation Criteria.................................................13

2.2 Statement of Work................................................................................................................16

3. Estimated Resources and Schedule.........................................................................................20

3.1 Personal Effort Requirements..............................................................................................203.2 Other Resource Requirements..............................................................................................213.3 Financial Requirements........................................................................................................223.4 Project Schedule...................................................................................................................22

4. Closure Material.......................................................................................................................24

4.1 Project Team Information.....................................................................................................244.1.1 Client Information.........................................................................................................244.1.2 Faculty Advisor Information.........................................................................................244.1.3 Team Members’ Information........................................................................................25

4.2 Closing Statement.................................................................................................................254.3 References............................................................................................................................25

List of Figures

2

Page 3: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Figure 1. Teradyne J750 tester......................................................................................................5

Figure 2. ESD strip.......................................................................................................................13

Figure 3. Gantt Chart for Accoplishments.................................................................................25

Figure 4. Gantt Chart for Deliverables...........................................................................................25

List of Tables

Table 1. Milestone Completion Scoring Rationale....................................................................15

Table 2. Milestones & Grading Weights.....................................................................................17

Table 3. Estimated Personal Efforts...........................................................................................23

Table 4. Estimated additional resources.....................................................................................24

Table 5. Estimated Project Costs.................................................................................................24

Table 6. Schedule of Deliverables...............................................................................................25

Table 7. Team Members contact information............................................................................26

Definitions

ADC - Analog to digital converter

DAC - Digital to analog converter

DIB - Device interface board

DUT - Device under test

ESD - Electrostatic discharge

ECpE - Electrical and computer engineering

IG-XL - A windows based software that utilizes Microsoft Excel and Visual Basic to develop programs for the Teradyne J750

ISU - Iowa State University

I/O - Input and output

Mixed- Signal Testing - testing that uses analog and digital simultaneously PSI - Pounds per square inch, a unit of measurement for pressure exerted on a known surface area

Teradyne J750 - A tester donated to ISU that is used for testing printed circuit boards and integrated circuits as shown in the figure below.

3

Page 4: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Figure 1: Teradyne J750 tester

TDR - Time domain Reflectometry

4

Page 5: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

1. Introductory Material

This section introduces the project, abstract, acknowledgements, problem statement and solution, operating environment, intended users and uses, limitations and assumptions, expected end product and other deliverables.

1.1 Executive Summary The scope of this project is to expand upon previous Teradyne J750 cookbooks of instructions which are in a manual format for the ISU Department of Electrical and Computer Engineering. At present the current cookbook instruction set is missing a mixed-signal volume section and the present project team members fills this gap by reviewing, citing previous cookbooks to meet the mixed-signal testing requirements requested by the ECpE department to create an extended cookbook. The team will setup and test (2) two (10) ten to (12) twelve bit ADC’s, (2) two (10) ten to (12) twelve bit DAC’s, and a (10) ten MHz or faster op-amp using the Teradyne J750. The test scenarios and documentation will be used to create this mixed-signal cookbook.

1.2 Acknowledgement

The team members extend great appreciation and would like to this opportunity to thank Dr. Robert Weber for the advisory role and being very committed to the team and this project through out its duration. The team also likes to acknowledge and thank Jason Boyd for the training and on site supervision for the first scheduled month after the initial meeting with Dr. Weber of the project as well as the department of Electrical and computer engineering at Iowa State for use of the Teradyne J750 and the Teradyne Company for the J750 tester. Lastly the team would like to acknowledge the previous senior design teams for the documentation that is left in the lab to be used as a source of reference on this project.

1.3 Problem Statement and Solution

This section gives a general outline and an overview of the proposed problem solution.

1.3.1 Problem Statement

The success of any product for the market after the planning and fabrication phases relies heavily on some form of testing and experimentation. The product must undergo some form of rigorous tests for different scenarios before release to ensure that is functions according to specifications and the client expectations. Universities and colleges which are research oriented provide a cost effective way of testing such products for companies and investors. Iowa State is no exception and with the donation of the Teradyne Integra J750 tester from the Teradyne co-

5

Page 6: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

operation, it gives Iowa State department of Electrical and computer engineering this opportunity to achieve this cost effective way of testing and building devices.

6

Page 7: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

This is important because the research conducted can create new methods of testing and also increase or build upon the productivity of the equipment donated and the devices under test. The associated cost of obtaining a fully functional tester is beyond the university’s operating budget and the present Teradyne J750 does not have the capability at present to perform mixed-signal testing. The two past groups have already designed, tested and implemented digital circuits as well as wireless circuits for testing along with the original function of the J750 to test analog circuits. The present team must design analog to digital converters and configure the Teradyne via hardware configuration and software to have the capability to test these mixed-signal IC circuits.

1.3.2 Problem Solution

The team will devise a way to interface mixed-signal components with the Teradyne J750.  Code will also be written using IG-XL software that will be compatible with three different breeds of devices; a DAC, ADC, and high speed operational amplifier. Once this is setup, methods for testing the devices will be developed and recorded in an orderly fashion.  These records and testing procedures along with the results will then be brought together in one concise package.   This package will be added on to the current Teradyne J750 cookbook and will show users how to setup and test mixed-signal devices using the machine.

1.4 Operational Environment

Operation of the circuits has to occur indoors within a temperature range of 27°C to 33°C because of the sensitivity to temperature the Teradyne J750 own circuitry possesses and the fact that the equipment itself is worth over 500,000 US dollars, maintains why a preventative process needs to be followed before operating the machine. Thus the Department of Electrical and Computer engineering will only operate and test the various circuits for mixed-signal in a temperature regulated room. The presence of a human body presents the opportunity for the distribution of charge and voltage to any form of circuitry .i.e. (ESD – Electrostatic Discharge) and which can have an adverse affect on the equipment similar to temperature. It is required that every person and team member that is present in the room who is in direct contact with the Teradyne J750 wear ESD wrist bands when using the tester. The vacuum pump and the “on” portion of the on/off switch are to be activated before any form of testing can be done after the first two instructions above are done. The purpose of the vacuum pump is to allow the DIB and the tester surface to be held together safety with approximately (4) four psi of pressure so that the both interfaces are locked together so the other devices that needs to be mounted can be done and held in a stable position for the process of testing.

7

Page 8: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

1.5 Intended User and Intended Use

Section defines who are the intended users and the intended uses of the project.

1.5.1 Intended User

The potential audience for this project will be any student or faculty member of the Department of Electrical and Computer engineering that requires testing of the mixed-signal option devices. The user must possess some form of knowledge of IC circuits; digital logic, signals and digital communication, and an understanding of the operation the Teradyne J750 for conducting tests. The user must be able to synchronize the frequency that controls clock cycle along with the rest of setup and be able to follow the reference manual developed by the design team.

1.5.2 Intended Use

The intended use of the project is to allow mixed-signal testing using the Teradyne J750 tester and to develop and test various scenarios for (2) different (10) ten to (12) twelve bit ADC’s as well as DAC’s and for a (10) ten MHz or greater op-amp. This mixed-signal option provides an innovative approach to these microcontroller mixed-signal devices similar to the present industry testing capabilities and using the IG-LX software provided is able to efficiently record the results from the tests so as to achieve the goals of the Department of Electrical and Computer engineering.

1.6 Assumptions and Limitations This section outlines the expected assumptions and limitations for the end-product where any additional assumptions and limitations to be included prior to team or advisor consultations about specifics of the project.

1.6.1 Assumptions This section provides the relevant details of the user and system assumptions.

1.6.1.1 User Assumptions This section outlines the assumptions about the intended user:

Willing and can follow basic instructions during training to use the equipment so as to follow all necessary safety precautions.

User has read and understood the Teradyne J750 instructional manual. Some form of electrical and/or computer engineering background. Previous experience in circuit testing with the Teradyne J750

8

Page 9: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

User is knowledgeable of the electrical hazards the equipment can distribute and what the user is at risk of transferring to the machine.

User treats and operates all equipment in a timely and professional manner.

User is familiar with technical English as all documentation at present is/will be written in English.

User is knowledge about mixed-signal operation and concepts. User is able to tolerate the noise caused by the vacuum pumps.

1.6.1.2 System Assumptions

This section outlines the assumptions about the overall system:

All instruments are operational and calibrated. No expired licenses or copyright material that the team does not have

permission to use. The vacuum pumps are always operational. Testing of DUT’s are limited to one at a time. Teradyne J750 can interface with the IC devices to be tested.

1.6.2 Limitations

This section will provide details of the limitations identified with the project:

The Teradyne J750 is sensitive to temperature fluctuations and must operate within of the calibrated temperature. The current system is set for .

The Teradyne J750 is only capable of testing digital I/O. Because of this, all chips tested with the wireless interface must have digital I/O.

The maximum rate at which user can send data is at 115.2 Kbps The existing transmitter and receiver communicate at 916.5 MHz.

Therefore, nearby wireless signals at similar frequencies may disrupt the setup.

The communication link shall be limited to one frequency. The IG-XL software shall be used in writing the test code for the Teradyne

J750. The distance between the wireless interface and the Teradyne system will

be limited to five feet.

9

Page 10: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

1.7 Expected End-Product and Other Deliverables

This section outlines the details of the expected end-product and other deliverables.

At the conclusion of the Fall 2006 semester this project will bring into being: The five different IC interfaces constructed for review by Dr. Weber. IG-XL code written for each of the five IC interfaces for review by Dr. Weber.

At the conclusion of the Spring 2007 semester this project will bring into being: A complete Teradyne J750 cookbook which documents mixed-signal IC circuits. A demo test of the five different IC interfaces as instructed using the Teradyne

J750. These include the (2) two different (10) ten to (12) twelve bit ADC’s and DAC’s and a 10 MHz or greater operational amplifier.

10

Page 11: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

2. Proposed Approach and Statement of Work

The proposed approach and statement of work will entail all of the necessary actions needed to ensure the success of the project.

2.1 Introduction

This section will descried the expected end product and other deliverables by breaking them down into subsections that addresses constraints, functionality, technology, and other important issues.

2.1.1 Functional Requirements

The following describes the functional requirements of the end product:

       The cookbook will be written on a level that the uninformed test engineer can understand

       The testing instructions will address two ADCs, two DAC’s, and an Op-amp faster than 10 ten MHz.

       Only one DUT will be tested at a time.       A test program will be developed for each of the devices using IG-XL and

will allow new devices of similar constraints to be added.        Upon successful testing and mating of the devices a cookbook will be

made to allow future users to test these devices.        If the project fails, proper documentation will be provided such that one

can look over potential problems and issues.

2.1.2 Constraint Considerations

The following will define the constraints considerations of this project:

        30 weeks are allowed for the completion of the project.        The room housing the Teradyne tester is accessible by security code only.        All documentation and users manuals will be in English.        The total allotted budget for the project is $150.        Testing is done by digital I/O.        The software used for project will be developed using IG-XL.       The operating environment has to be kept at a constant. temperature of

30°C ± 3°.        Mixed signal testing is needed to test the devices.

11

Page 12: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

2.1.3 Technology Considerations

    This section covers any technological issues and ideas needed to interface the required devices with the Teradyne J750. Two different DAC's and two different ADCs will need to be tested along with a high speed op-amp.   The devices chosen will need to:

        Meet cost requirements        Proper connection to the DIB        Must be compatible with the Teradyne J750's I/O

Good care should be taken to ensure that the two DAC's differ from each other so that they can create different testing scenarios and the same goes for the ADC's.   The availability of cheap DAC's and ADC's components that are compatible with the Teradyne J750 and that can meet the team’s budget is limited.  The team will also have to take into consideration the DIB's that Iowa State already owns are also compatible and to test to see if it will work with the devices designed by the team.   Thus if a device is not compatible with one of the DIB's then the team will have to design and fabricate its own DIB.

2.1.4 Technical Approach Considerations

This section will detail the methods used for testing the devices. The best approach to testing the devices is to break the project up into smaller stages. This minimizes the overall risk and will help up successfully progress through the project.  It will also aid in troubleshooting and keeping track of where the team is in the scope of the total schedule.  Each stage will include the components of design, simulation, implementation, and testing.  Each stage will also have to be completed before any movement onto the next stage, with the exception of a few being run in parallel if time constraints become an issue. The stages are set up with the statement of work and can be followed easily using the Gantt chart designed for the project.

2.1.5 Testing Requirements Considerations 

This section will cover the testing requirements that need to be met in order to ensure that the device being testing is communicating with the DIB and the DIB is communicating with the tester.

Test one of the previous projects to ensure that the Teradyne J750 is still communicating with its DIB.   The test should meet the results produced by the previous team.

Run possible tests on the devices using instruments other than the Teradyne J750 to ensure that the devices are working to specifications.

Test the total setup by comparing the signal sent by the software to the signal received by the tester.

12

Page 13: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Run a TDR to make sure that all connections are valid so that any component of the Teradyne J750 cannot be damaged by faulty connections.

2.1.6 Security Considerations

Some security issues need to be taking into considerations in the process of developing the product. The major security concern in developing this product is to assure that we are obeying certain frequency bandwidth in order to not violate the FCC regulations. Since possible interference with other signal frequencies used by other communication networks might occur. Documentations are not of prior concern since increasing the knowledge of this product would be beneficial to other users.

2.1.7 Safety Considerations

This product will be operating under low voltage and current conditions. There would be no life-threatening concerns in the use of this product, maintenance or disposal possibilities. Although user of ESD wristband is recommended to avoid possible electric shocks which might damage the equipments and could lead to more financial issues in buying new equipments and extra effort to get the product back to the same stage. A figure of this ESD strap is shown below.

Figure 2: ESD strap

Basic steps in running the tester need to be taking under consideration to avoid device damage and misinterpreted results. in order to maintain device safety and insure data accuracy, turning the pump, switching on the tester, and then turning the computer on are basic steps that need to be performed in the same previous steps order. Also, the pins (I/O channels) need to be treated carefully while placing the test boards on top of the pins to ensure that they will not bend over which would cost money in order to replace them.

13

Page 14: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

2.1.8 Intellectual Property Considerations

Both the design and the software for this product will be open to public use but only certain faculty members and students have access to the Teradyne lab which is located in Coover Hall.

2.1.9 Commercialization Considerations

If the team suggested building a new DIB instead of using the ones owned by ISU, This DIB might have a great possibility to be introduced to the market in order for the companies to use it. High volume testing of wireless systems is becoming a necessity for most of the companies and this product would be of a great benefit to achieve that.

2.1.10 Possible Risks and Risk Management

Different design risks may encounter throughout the progress of accomplishing a successful design project. Below are some of these possible risks along with some possible suggestions to avoid these risks.

Risk: Developing the (10) ten to (12) twelve bit ADC’s to be tested might fail to give accurate results.Management: (10) ten to (12) twelve bits ADC are pretty high resolutions. To avoid digital noise on the analog signals, the addition of a separate voltage supply (about +5V) devoted just to the ADC and the photodiodes used as inputs. The ground for all of the above could be tied into one point where the power came into the regulator. With minimal bypass capacitors on the ADC inputs that might easily get stable readings.

Risk: In developing the (10) ten MHz Op amp to be tested, the desired frequency might not be generated accurately due to misinterpreting of the external RC model of the circuit which can cause op-amp instability. Management: Reducing the resistance value that makes up the RC circuit reduces the effect of the capacitance; this effect leads to the rule of thumb that high frequencies and low resistance go together. Input capacitance is easily compensated by adding a feedback capacitor into the circuit. The value of the feedback capacitor should be just large enough to achieve the desired overshoot response, because larger values cause a loss of high-frequency performance.

14

Page 15: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Risk: The team might lose or misplace some of the documentations.Management: Hard disks and hard copies will be used to limit the risks of losing any of the documentations. Also, the team will make sure that every member of the team has a copy of all the documents in case of emergencies where one of the members is not available for any reason.

Risk: Failure to meet the client (Iowa State) expectations.Management: The team agreed on having regular informal meetings to review the requirements and the work accomplished thus far so as to meet these requirements. Also, to discuss any further improvements that could be added even if it was beyond the requirements to maintain high project efficiency.

Risk: Facing possible learning and understanding difficulties.Management: Trying to assign different design aspects to each member of the team to achieve his/her own expertise in that area along with general understanding of all design aspects by the whole team. This way the team can guarantee to extend the limit of coverage of all aspects of the design conflicts.

2.1.11 Proposed Project Milestones and Evaluation Criteria

Success for the project will rely on the ability to meet the goals and milestones of the project plan as shown below. Each milestone will receive a score based on how well the goals for that particular milestone were met.

Table 1: Milestone Completion Scoring Rationale

Progress Numerical Score (%)Greatly Exceeded Criteria 100

Exceeded Criteria 90Met Criteria 80

Partially Met Criteria 70Did Not Meet Criteria 40

Did Not Attempt 0

Once the project is completed, each milestone will receive a final score based on its weight and importance.

15

Page 16: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Milestone: Project DefinitionDescription: Defining the project allows the entire team to work towards a common goal, even if each member is working on a different task.Evaluated by: Client and faculty advisorEvaluation criteria: The evaluators will look at the definition in terms of its understandability, readability, and completeness.Weight: 20%

Milestone: Technology SelectionDescription: Determining which IC devices work best with the Teradyne J750 is an important step as incompatible or inappropriate devices will halt the project and drain the budget. Adequate research is essential to avoiding these pitfalls.Evaluated by: Project TeamEvaluation criteria: The cost, pin layout, type, and specifications of each IC must be evaluated, along with the research documentation. Weight: 15%

Milestone: End-Product DevelopmentDescription: The code must be able to send and receive signals from each type of IC. Evaluated by: Team members and faculty advisorEvaluation criteria: Evaluators will look at the ability of each IG-XL code to interface with its corresponding IC.Weight: 15%

Milestone: End-Product TestingDescription: Testing will specialize the code to one specific device. This is important because it proves the flexibility of the system.Evaluated by: Team membersEvaluation criteria: The approach taken with testing needs to be thorough and systematic so as to provide each device with the same support. Weight: 15%

16

Page 17: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Milestone: End-Product DocumentationDescription: This is the primary goal of the project, as the cookbook will provide a systematic way to implement any device, not just the ones developed during the project.Evaluated by: Faculty advisorEvaluation criteria: This will be evaluated by checking that the modifications are seamlessly integrated into the existing document and that they are easy to read, follow, and are at a level appropriate to the users.Weight: 25%

Milestone: Project ReportingDescription: This is the accumulation of all weekly reports and website updates, along with the project plan, design report, poster and final report.Evaluated by: Faculty advisorEvaluation criteria: Reporting should be graded based on professionalism, readability, usefulness, and subject relevance.Weight: 10%

Table 2: Milestones & Grading WeightsMilestone (%)

Project Definition 20Technology Selection 15

End-Product Development 15End-Product Testing 15

End-Product Documentation 25Project Reporting 10

Total 100

Using the rationale in Table 1, the success of each milestone can be evaluated. The weight of each milestone can be seen in Table 2. Based on each milestone’s completion score and weight, a final project score will be given. A successful project will receive a score of no less than 80%.

2.2 Statement of Work

The statement of work outlines the tasks and subtasks needed to complete the project. Each task and subtask will include: the objective which outlines the goal, the approach which presents the team’s intended procedure, and the result which is the predicted outcome upon completion of the task.

17

Page 18: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Objective: Understand the Teradyne system and the previous group’s work. Approach: After doing independent research on the Teradyne J750 and

reading over the documentation from the previous Teradyne groups, there will be an in-depth discussion with Dr. Weber where outstanding questions will be answered or the need for more resources will be identified.

Result: All team members will have a solid understanding of the mission’s definition.

Objective: Set up a weekly meeting with Dr. Weber so that he can explain and clarify the objectives, background, and potential problems of the project. Approach: Schedules will be compared and weekly meetings will be set with Dr. Weber, who will present relevant project information. Results: A weekly meeting time will be selected, and important information will continually reach team members.

Objective: To have a certified Teradyne operator show at least one team member the proper measurement setup and safety considerations when working with the Teradyne J750. Approach: An email will be sent to arrange a demonstration time. After the demonstration of the tester, all team members will meet and run tests as a group to gain a uniform understanding of how to perform tests with the Teradyne J750. Results: The group will have an initial hands-on experience with the Teradyne J750 under a skilled technician.

Objective: To understand the background material necessary for testing mixed signal devices in the Teradyne J750. Approach: The Teradyne J750 senior design cookbook will be read along with the previous groups’ final reports and the J750 manual. Using the information from these sources, the team will perform simple tests to ensure competency with the machine. Results: The group will gain a familiarity with the Teradyne machine which will be essential during the project.

18

Page 19: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Objective: To identify the necessary technological components, narrow the group’s selections based on standardized criteria, and perform a final selection based on further research.

Approach: Consult electronics suppliers, the faculty advisor, and various objective sources (books, internet, etc.) about unfamiliar microelectronic devices and concepts, specifically related to DAC converters, ADC converters, and high frequency Op Amps.

Results: The chosen devices will perform well for the projects intended purposes.

Objective: To understand the operation of analog-digital converters, digital-analog converters, and op-amps capable of operating over 10 MHz. Approach: The internet and course texts will be used to research various types of the mentioned devices. Possible solutions will be discussed with faculty advisor. Results: The group will have a general understanding of the operation of the proposed testing components.

Objective: To come up with a set of guidelines for evaluating similar devices. Approach: A set of criteria including cost and performance will be set for the selection of the DUTs. A suitable cost will be one that is competitive with similar technology and within the allotted budget. The performance criteria is defined by its ability to meet the needs described in the functional and technology considerations found in Sections 2.1.1 and 2.1.3 respectively. Results: A standard for comparing different devices will be established, and from this standard a list of potential devices will be made.

Objective: To make device selections from the potential list based on a deeper comprehension gained from research. Approach: The team will compare different devices and organize them in order of preference based on cost, chip speed, compatibility, and reliability. Results: A selection will be made that features the best possible devices for the project’s purposes.

19

Page 20: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Objective: To create appropriate IG-XL codes that will provide templates for the ADC, DAC, and op-amp circuits.

Approach: By applying the understanding gained in previous tasks, the group will write code for each of the DAC, ADC, and Op Amp scenarios. Team members will experiment with the IG-XL software to develop programs that send out appropriate training signals and read the resulting input signals.

Results: Basic scripts will be available to use as a starting block for further and more advanced testing of the above mentioned devices.

Objective: Test and make the appropriate changes to the end-product to ensure the most reliable IG-XL code is created.

Approach: Team members will create code that specifically tests two different types each of 10 – 12 bit ADC’s and DAC’s, and one type of op-amp capable of operating over 10 MHz. The tests will determine whether the benchmarking information given on the data sheet is accurate for each device.

Results: A set of IG-XL codes will be created that could be used to test specific devices.

Objective: To modify the existing Teradyne cookbook to include support for mixed signal IC testing.

Approach: The latest version of the testing cookbook will be downloaded and modifications will be added to include how to set up the mixed signal tests. This documentation will be submitted to either Dr. Weber or to another representative proficient in the use of the Teradyne J750 for approval.

Results: Others will be able to utilize the efforts of the team to perform their own tests.

Objective: To accurately log project successes and failures and document full implementation of design so that others can understand the team’s efforts and innovations.

Approach: Maintain communication with the senior design faculty through various mediums. Several reports and presentations will also be prepared throughout the project lifespan.

Results: A thorough and accurate documentation of the life of the design project will be available upon completion.

20

Page 21: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Objective: To update faculty advisor, the client, and senior design faculty on the progress made each week. Approach: One group member will write and send out the weekly emails in a standardized form. Results: All personal concerned with the project will be kept up-to-date.

Objective: To maintain a website with the latest team progress and documentation. Approach: Weekly emails and finalized reports will be linked on the website. Results: All those with interest in the project will be able to see the latest documentation and progress.

Objective: To have a document that will guide the team’s overall process during the project. Approach: A detailed project plan will be written in a formal format. The content of this report will reflect the decisions made during the first advisor meetings. Results: This document will give the team clear goals and tasks that will help to complete the project.

Objective: To have a document that will outline the devices selected and how the devices will be operate in the present system. Approach: A detailed design report will be written in a formal format. The content of this report will reflect the decisions made regarding the devices and the group’s current understanding of the devices. Results: This will be a formal document outlining the devices selected and how the product will be tested.

Objective: To have information on the project in a visually pleasing and easily understandable format. Approach: Microsoft PowerPoint will be used to design the poster. Information presented in the poster will reflect the current state of the project. Results: A poster containing useful information for both professional and casual observers will be created.

21

Page 22: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Objective: To formally document the final results and any unexpected outcome during the project. Approach: At the conclusion of this project, the team will create a document that contains a summary, occurrences, and conclusions obtained during the process. Results: A formal document that describes the end-product.

Objective: To provide an oral summary of the group’s project accomplishments and expected end product to the senior design class. Approach: The team will prepare a PowerPoint slide and accompanying explanation on the project, including any introductory materials, project activities, schedules and opening and closing remarks. Results: The class presentation will provide the group with valuable oral presentation experience which is an essential skill for any engineer.

Objective: To provide an oral summary of the group’s project accomplishments and expected end product to an outside panel of engineers. Approach: The team will prepare a PowerPoint slide and accompanying explanation on the project, including any introductory materials, project activities, schedules and opening and closing remarks. This material must be memorized since notes are not allowed. Results: The IRP presentation will give the group a much better idea of what a real industrial presentation is like, in addition to informing the panel of the group’s activities and expected accomplishments

22

Page 23: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

3. Estimated Resources and Schedule

This section reflects the resource requirements, personal effort requirements, the project schedule and the financial requirements.

3.1 Personal Effort Requirements

The total contribution by each team member, in hours, is listed in the table below.  The hours listed are an estimated amount of time that each member will spend on each aspect of the project.   The table is broken down into problem definition, technology selection, end-product development, end-product testing, end-product documentation, and project reporting. The project will provide plenty of work to keep the whole team involved and will provided enough flexibility for unforeseen circumstances.   The team is made up of four electrical engineers who will each have to put some work into programming on the Teradyne and the webpage.  One team member will be dedicated to the webpage for simplicity reasons. A good deal of time during the first phase of the project will be dedicated to adapting to the Teradyne and setting up tests for the parts purchased.   The latter phase of the project will primarily involve running tests and modifying the cookbook which will require a larger time commitment.  Extra preparation during the first phase will definitely reduce the amount of time spent during the second phase.

Table 3: Estimated Personal Efforts

Personnel

Prob

lem

D

efin

ition

Tech

nolo

gy

Sele

ctio

n

End-

Prod

uct

Dev

elop

men

t

End-

Prod

uct

Test

ing

End-

Prod

uct

Doc

umen

tatio

n

Proj

ect

Rep

ortin

g

Est.

Tota

l

Abdelbasir, Murwan 24 26 55 55 36 27 223

Brown, Jon 23 27 57 58 38 26 229

Hewitt-Borde, Brent 27 25 58 56 37 25 228

Stolpman, Rob 26 26 60 57 35 26 230

Total 100 104 230 226 146 104 910

23

Page 24: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

3.2 Other Resource Requirements

The Teradyne J750 tester is already in the possession of Iowa State University in the form of a donation and is available to the team free of charge. A project poster needs to be created and printed. A summary of the resources are listed in the table below.

Table 4: Estimated additional resources

ADC IC chip 0 0 $40.00

DAC IC chip 0 0 $40.00

Printing of project poster

15 0 $35.00

Teradyne Integra J750 Test System

0 0 Donated

Operation Amplifier 0 0 $10.00

Total 15 0 $125.00

3.3 Financial Requirements The cost estimate for the project is drafted and can be seen in the Table below. This calculation is based off the hourly wage of $11.50/hr.

Table 5: Estimated Project Costs

a. Printing of project poster $35.00b. Teradyne Integra J750 Test System Donatedc. DAC IC (2x) $40.00d. ADC IC (2x) $40.00e. Operation Amplifier $10.00

Subtotal $125.00Labor at $11.50 per hour:a. Abdelbasir, Murwan $2564.50b. Brown, Jon $2633.50c. Hewitt-Borde, Brent $2622.00d. Stolpman, Rob $2645.00

Subtotal $10,465.00

24

Page 25: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Total $10,590.00

3.4 Project Schedule

A Gantt chart is created to show the predicted schedule throughout the duration of the project. All the tasks and subtasks that are defined earlier in the statement of work are laid out in two separate Gantt charts, one for accomplishments and another for deliverables with the expected dates, the amount of time reflected for each task which accounts for both the difficulty of the task and the relative strengths and weaknesses of the team. The table below, Table 6, shows the schedule of deliverables for the project of fall 2006 semester.

Table 6: Schedule of Deliverables

09/22/06 Project Plans Due10/06/06 Bound Project Plan Due11/03/06 Design Reports Due11/17/06 Bound Design Reports Due

*TBA Project Plan and Design Reports Posted on Website

Figure 3: Gantt chart for Accomplishments

25

Page 26: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Figure 4: Gantt chart for Deliverables

4. Closure Material

This section provides the client, faculty advisor and team member’s information and the closing summary.

4.1 Project Team Information

This section lists the project team, client and faculty advisor contact information.

4.1.1 Client Information

Department of Electrical and Computer EngineeringCollege of EngineeringIowa State University2215 Coover HallAmes, IA 50011

4.1.2 Faculty Advisor Information

Dr. Robert J Weber301 DurhamAmes, IA 50011Office: (515) 294-8723Fax: [email protected]

4.1.3 Team Members’ Information The contact information for the members of the project team is shown in the table below.

Table 7: Team Members contact informationMurwan Abdelbasir3426 Orion Drive,

Jon Brown225 N. Hyland,

Brent Hewitt-Borde3426 Orion Drive,

Rob Stolpman4305 Maricopa

26

Page 27: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

Apt #210 Ames, IA 50010 (515) [email protected]

Apt #4Ames, IA 50014(319)[email protected]

Apt #210 Ames, IA 50010 (515) [email protected]

Apt #3Ames, IA 50014(612) [email protected]

27

Page 28: 1seniord.ece.iastate.edu/projects/archive/may0712/Bound... · Web view1.4 Operational Environment 7 1.5 Intended User and Intended Use 7 1.5.1 Intended User 7 1.5.2 Intended Use 7

4.2 Closing Statement

The Teradyne J50 can be a very powerful device given the right amount of funding and the members of this senior design team would like to present this low cost solution for testing mixed signal devices by utilizing some of the instruments already available at ISU. It is felt that the best way to do this is by expanding the current cookbook for the Teradyne J750 which in turn will allow ISU the ability to use this tester more efficiently. A mixed-signal option will increase their number of avenues for testing these devices and it is the vision of the team and its advisor Dr. Weber that this guide will be beneficial to future students and researches at ISU and that they will be able to follow suit in the future by using this developed guide to keep the tester up to date with expanding technology

4.3 References

Senior Design Team Spring 2005, "Teradyne J750 Tester Cookbook." February 2004.

Senior Design Team May 2005, "Final Report." April 2005. Teradyne, "Teradyne J750 software manual", 2003. Teradyne, “User manual”, 2003. Teradyne, “Mixed-signal option tutorial”, 2003. Teradyne, Teradyne J750, September 22, 2006 www.teradyne.com 

28