Embed Size (px)
Citation preview
A Universal RF Communications LinkProject Plan
Client: Senior Design
Faculty Advisor: Dr. Yao Ma
Senior Design Dec07-06Team Members:
Joseph Beierschmitt, EE Shawn Freese, EEJared Leonard, CprE Matt Raygor, EE
REPORT DISCLAIMER NOTICE
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.
Submitted February 27, 2007
Contents
Figures iv
Tables v
Definitions vi
Section 1 Introductory Materials 11.1 Executive Summary, 11.2 Acknowledgements, 11.3 Problem Statement, 2
1.3.1 General Problem Statement, 21.3.2 General Problem Solution, 2
1.4 Operating Environment, 31.5 Intended Users and Uses, 3
1.5.1 Intended Users, 31.5.2 Intended Uses, 3
1.6 Assumptions and Limitations, 41.6.1 Initial Assumptions List, 41.6.2 Initial Limitations List, 4
1.7 Expected End Product and Other Deliverables, 5
Section 2 Proposed Approach 52.1 Functional Requirements, 52.2 Constraint Considerations, 52.3 Technology Considerations, 52.4 Technical Approach Considerations, 62.5 Testing Requirements Considerations, 62.6 Security Considerations, 62.7 Safety Considerations, 62.8 Intellectual Property Considerations, 72.9 Commercialization Considerations, 72.10 Possible Risks and Risk Management, 72.11 Project Proposed Milestones and Evaluation Criteria, 72.12 Project Tracking Procedure, 8
Section 3 Statement of Work 93.1 Project Definition, 9
3.1.1 Problem Definition, 93.1.2 End-Users and End-Uses, 93.1.3 Limitation Identification, 9
3.2 Technology Considerations, 103.2.1 Technology Identification, 103.2.2 Criteria Identification, 103.2.3 Technology Research, 103.2.4 Technology Selection, 11
3.3 End-Product Design, 113.3.1 Identification Requirements, 11
ii
3.3.2 Design Process, 113.3.3 Design Documentation, 11
3.4 End-Product Implementation, 123.4.1 Identification of Limitations, 123.4.2 Implementation of End-Product Design, 12
3.5 End-Product Testing, 123.5.1 Test Planning, 123.5.2 Test Development, 133.5.3 Test Evaluation, 13
3.6 End-Product Documentation, 133.6.1 Development of End-User Documentation, 133.6.2 Development of Maintenance Support Documents, 14
3.7 End-Product Demonstration, 143.7.1 Demonstration Planning, 143.7.2 Faculty Advisor Demonstration, 143.7.3 Client Demonstration, 143.7.4 Industrial Review Panel Demonstration, 14
3.8 End-Product Reporting, 153.8.1 Weekly Email, 153.8.2 Project Plan Development, 153.8.3 Project Poster Development, 153.8.4 End-Product Design Report, 163.8.5 Project Final Report, 16
Section 4 Estimated Resources 174.1 Personal Effort Requirements, 174.2 Financial Requirements, 184.3 Other Requirements , 18
Section 5 Schedule 205.1 Project Schedule, 205.2 Deliverable Schedule, 21
Section 6 Closure Materials 226.1 Closing Summary, 226.2 Project Team Information, 23
6.2.1 Client Information, 236.2.2 Faculty Advisor Information, 236.2.3 Team Members Information, 23
6.3 References, 23
iii
FiguresFigure 1- Projected Schedule, 20Figure 2- Project Deliverable Schedule, 21
iv
TablesTable 1- Project Milestones and Overall Importance, 7Table 2- Milestone Evaluation Criteria, 8Table 3- Personal Effort Requirements, 17Table 4- Financial Requirements, 18Table 5- Other Requirements, 19
v
DefinitionsA Analog-to-Digital Converter (ADC)
A device which converts an analog signal to a digital signal
B Bit rate (bps)A term which specifics the number of bits per second a digital signal operates at
C
D Dec07-06The unique identification code designated for the team working on the universal RF communications link project. The first alpha-numeric code indicates when the project will be completed. The second numeric code indicates the project number.
Digital-to-Analog Converter (DAC)A device which converts a digital signal to an analog signal
E Electrical and Computer Engineering (ECE)A department of Iowa State University
F Federal Communications Commission (FCC)An independent United State government agency which regulates interstate and international communications by radio, television, wire, satellite and cable [1]
Frequency Shift Keying (FSK)A common form of modulation used by communication systems
G – H – I – J – K
L Liquid Crystal Display (LCD)A low power digital device which uses liquid crystals to display alphanumeric characters
M Microcontroller (MCU)A self-contained computer-on-a-chip consisting of a central processing unit, non-volatile program memory, random access memory for data storage, and various input-output capabilities [3]
N – O
P Printed Circuit Board (PCB)A structure which mechanically supports and electrically connects electrical devices
Q
R Restriction of Hazardous Substances (RoHS)A directive which restricts the use of certain hazardous substances in electrical and electronic equipment. These substances include lead, cadmium, mercury, hexavalent chromium, polybrominated biphenyl, and polybrominated diphenyl ether flame retardants [2]
S – T – U – V – W – X – Y – Z
vi
Section 1 Introductory MaterialsThe following section contains the executive summary, acknowledgements, the problem statement, the operating environment the project will be subject to, the intended users and uses, the assumptions and limitations that were imparted upon this project, and the expected end product from the project team.
1.1 Executive SummaryMany times senior design projects require an embedded RF communications link to accomplish a certain task. This is often a problem for the project teams as they do not have the time or expertise to have one specifically designed. To facilitate teams’ needs this project will design and build a universal RF communications link. Two previous senior design teams have attempted this project but with limited success.
The basic functional requirements will include one input/output for both analog and digital signals. The analog will have a bandwidth of less than 4 kHz and the digital will have a bandwidth of less than 5 kbps. The transceiver of the module will be controlled by an embedded microcontroller. The module must follow FCC regulations due to operation in the United States; however, this module will not meet new product industry design standards because it will not be RoHS compliant. This product will utilize components which are available in RoHS compliant packages; therefore, this product could be made to meet RoHS if so desired.
The envisioned project is a device that has a physical size of 9cm by 13cm by 4cm (3”x5”x1.5”). This module will have “functional” full-duplex capability, meaning it can transmit and receive practically simultaneously. It shall operate such that any analog or digital signal meeting the requirements will pass to another module which will output the original signal. The input bandwidth will be about 4 kHz, and should work at a distance of 30m line-of-sight. The batteries should be rechargeable and capable of supporting the module for five hours. Individual modules shall not exceed $100. For testing purposes there will be a need for two modules. Tests will include range, data integrity, battery life, reliability, and duplex functionality. Finally, modules will come with a “cookbook” manual or a tutorial that allows quick and easy implementation into future projects. Since this module is being design for other senior design projects commercialization isn’t a factor; however, this product may support additional features thus making it better than available commercial units.
If time permits the module will have increased functionality which may include one or several of the following: frequency hopping, a LCD screen to indicate to the user the frequency and power/battery life of the module, a sleep/standby mode to save power, a remote on/off mode, multiple inputs/outputs, error checking, RF power regulation to adjust module’s range, master/slave operation, computer interface, and enclosed in a case. The specific details which are still in consideration include frequency band, RF modulation, power/batteries, and individual components of the module.
1
1.2 AcknowledgementsThe senior design team Dec07-06 would like to thank Iowa State University for providing a positive learning community. The team would also like to thank Professor Lamont and Professor Patterson for providing us with a project which has the potential to greatly impact the success of future design projects. The team would also like to thank our faculty advisor Dr. Yao Ma, without a supportive advisor this project could not be successful.
1.3 Problem StatementWhen a senior design team is provided with a project, the only details given about project are the name of the project and a one paragraph proposal. Listed below is the proposal received by the Dec07-06 team.
An embedded radio frequency (RF) link is often required in many electrical and computer engineering senior design projects. However, the design teams usually do not have the time and expertise to design such a link specifically for each project. To meet this need, several basic, microprocessor-controlled RF links have been designed and tested by two previous design teams but with limited success. This project team will review the previous teams’ results but will also conduct a comprehensive search for more recently developed technologies in order to produce an optimum RF link for use in future senior design projects. To enhance the usability of this link, a companion development board, similar to the microcontroller development board used in CprE 211, is also required. The project will involve the design, fabrication, testing, and documentation of the complete RF link package. This will include the selection and integration of the optimum component parts, the layout of the appropriate printed circuit board, the provision of various antenna systems, the addition of various data and signal processing capabilities such as analog-to-digital and digital-to-analog conversion, the addition of various output transducers and capabilities such as pulse-width modulation, the development of alternative power supplies and packaging, and comprehensive testing of the complete system. Full documentation will include tutorials and design guides for using the RF link. Multiple sets will be constructed for use by senior design teams in the future.
1.3.1 General Problem StatementPrevious senior design projects were unsuccessful due to insufficient time, money, or other resources they needed to build a short range 2-way wireless communications link. This project must provide a cost effective solution for error-free bi-directional transmission of analog and digital signals over a specified range. The module will be self supporting through use of onboard batteries and provide continuous transmission over a specified duration.
1.3.2 General Problem SolutionThe solution is to build a universal RF link that can easily be integrated into senior design projects. For the given project, universal implies that input/output features must encompass analog and digital signal. This RF link will consist of standalone modules which will allow for a variety of signals to be transmitted and received amongst each other. A microcontroller will be necessary to buffer sampled data to the RF transceiver. In addition
2
an LCD and control switches may be implemented to allow the user to set parameters such as frequency and range.
1.4 Operating EnvironmentThis product will be designed to operate in an indoor and outdoor environment, depending upon the enclosure used. Without an enclosure the module must be kept in a relatively clean environment where the temperature can be maintained between -20 to 60 degrees Celsius and humidity will be less than 90 percent. The product will perform under moderate vibration but will not be used in situations where a drop of more than 60 centimeters (case dependant) may occur. The module will be used in environments with little RF interference in the 2.4 GHz band.
1.5 Intended Users and UsesThis section has been divided into two separate sections. The first being discusses who the intended users will be and the second discusses how this product will be used.
1.5.1 Intended UsersThe intended users will mainly consist of senior design students within the ECE department at Iowa State University; however, it may also be used by anyone needing an analog or digital communications link.
1.5.2 Intended UsesThe device is expected to be used within a senior design project as a data communications link. It is intended to be used for relatively short range communication with relatively low data rate transmissions within the user’s chosen application.
1.6 Assumptions and LimitationsAs a project undergoes a transformation to an end product there are limitations and assumptions which must be made. Limitations include how the project is physically restricted, as requested by the client, while assumptions are what the project team defines as restrictions.
1.6.1 Initial Assumptions List Battery will be charged to a minimum of 75% of its rated capacity for module to meet
the battery life requirement. A form of FSK modulation will provide adequate performance for operating in the
2.4GHz unlicensed band. The module will provide a means of error correction to maintain data integrity. A microcontroller will be used to provide error correction and radio control. A LCD panel will provide the user with channel and radio power configuration
information. The final product will operate correctly when used in the specified environment.
1.6.2 Initial Limitations List The module will be used in the United States; therefore, FCC regulation will apply and
it will operate in unlicensed frequency bands.
3
The module will have a small form-factor. The maximum size shall be 4cm by 9cm by 13cm, and weigh less than 0.5kg.
The module must support full duplex communication at a minimum range of 30m (line-of-sight).
The module will support a minimum of one analog and one digital input and output. The analog input/ output will have a minimum bandwidth of 4 kHz.
The module must perform under battery power for a minimum of five hours. An individual module’s cost will not exceed $100 ($200 per pair).
1.7 Expected End Product and Other DeliverablesThe end product will include multiple inexpensive communications modules all of which will meet the minimal operation requirements. A user manual, service manual, and tutorials will accompany the fully functional communications link. These deliverables should be completed by December 2007. The tutorials will walk the user through connecting the communications link to their system and sending data. The user manual will include a more detailed description of the tutorials and will also include a troubleshooting section, so users know what to do if the communications link becomes unreliable. The service manual will include schematics, datasheets, and part replacement options for future service needs.
4
Section 2 Proposed ApproachTo ensure a high probability of project success a proposed approach is crucial. The proposed approach is broken down into several sections and defines not only what the end product will do but also includes how the team will accomplish this.
2.1 Functional RequirementsThe following functions will be implemented into this project and are necessary to complete the primary requirements of the client.
o Transmit analog input to analog output via RFo Each analog channel supports 4kHz bandwidtho Transmit digital input to digital output via RFo Each digital channel supports 5kbpso Transmit and receive practically simultaneously (“functional” full-duplex)o Transmit/receive range of 30m (line-of-sight)o Self supporting for 5 hours
NOTE: These are the primary goals of this project. Additional functionality may occur once the primary goals have been satisfied.
2.2 Constraint Considerations The following constraints will be imposed upon this project. The constraints where formed from the assumptions and limitations.
o Size must not exceed 9cm by 13cm by 4cmo Weight must not exceed 0.5 kgo Batteries must be removable or rechargeableo RF transmissions must be FCC complianto Cost must not exceed $100 per module ($200 per pair)o Temperature range must not exceed -20 to 60°Co Batteries must be charged to a state of greater than 75% capacity before useo Only 1 operating communications link per channelo Limited traffic on the 2.4GHz frequencyo Low power consumption
2.3 Technology ConsiderationsThis project consists of several systems and requires additional research to determine which systems are best suited for this project. At minimum the project will need: o Central processing unit- This converts sampled inputs into a format usable by RF
technology, and converts RF technology data output to usable signal outputs.o Signal processing- This may be necessary if the central processing unit is not sufficient
5
o RF technology- This is responsible for sending data from one unit to another. It may consist of a transceiver which combines transmit and receive into a single unit, an amplifier to increase output power, and an antenna to radiate the RF.
o Power technology- This is responsible for providing power to the other systems
NOTE: The central processing unit will most likely take the form of an embedded microcontroller because of the low-current draw and sufficient data processing capabilities.
NOTE: The RF technology may consist of a purchased module which encompasses all required necessary RF components.
2.4 Technical Approach ConsiderationsA major part of technical approach is to choose parts that contribute greatly to the overall success of the project. The project team will research RF links that previous senior design teams have worked on and will decide whether it more practical to revise one of the previous design projects or initiate a new design. If a new design is necessary, research of components will be necessary. The component research will emphasize price, power consumption, and features that make the module easily adaptable to any improvements added after basic system functions of the device have been met. Once the components have been researched, a side-by-side comparison will be formulated which will allow for an optimal design.
The development of the project will consist of the team choosing suitable components, then creating schematics and software as soon as possible. In addition, once hardware and software are in place the approach will consist of testing, and once the basic link has been established, implementing additional features as time and resources permit. Once the prototype modules are completely tested the project team will produce 2 end product modules.
2.5 Testing Requirements ConsiderationsTesting for the device will include four main areas: range, data integrity, reliability, and duplex communication. To test the range, the project team plans to input signal from a function generator to the module and use an oscilloscope to check the output for various distances. Reliability will be tested by requiring a single 24 hour continuous operation of the module. Also, a mixed signal will be applied to the input to test the dependability of analog and digital data transmission. The strategy for testing the duplex functionality of the device is to use multiple function generators and oscilloscopes. This way the project team will visually confirm data integrity while the module is transmitting and receiving simultaneously. A test will be considered a success if and only if the test meets the predefined specifications.
2.6 Security ConsiderationsAt present, there isn’t any expected security needed in the design due to the product’s intended use and users. This being the case the data will not be encrypted, but will have a custom binary header. If at any point during the construction, the project team realizes that
6
data security is available and easily achievable (and offers practical value) the team and faculty advisor will determine as to whether or not it is to be integrated into the link’s design.
2.7 Safety ConsiderationsSince this product uses RF and more than likely will consist of a new design, the follow
safety issues are concerns:
o This module is designed to operate in the United States; therefore, it must conform to FCC regulations in regards to output power, frequency band, and electrical interference.
o The module will not meet RoHS requirements; however, components used are available in RoHS compliant packages.
o Batteries used in this design should not be exposed to excessive heat and must be disposed of properly.
2.8 Intellectual Property ConsiderationsAlthough there are existing designs for RF communications links, this design will remain unique; however, it may utilize previously designed RF transceiver modules. All PCB designs and software constructed during this project will be the property of Dec07-06 team members.
2.9 Commercialization ConsiderationsThere are existing products on the market similar to this product but with minimal functionality. For example, a previous design team used a Honeywell transceiver which supported analog and digital inputs. If this product is considered for commercial purposes, new and innovative features must be implemented at a competitive cost compared to the existing products.
2.10 Possible Risks and Risk ManagementPossible risks that could occur with the success of this project are few but important. One such risk includes the components not arriving in time to implement into the PCB. This can be avoided by ordering parts well in advance of any prototype deadline, and recognizing that it will take a week or so for the parts to arrive. There is also a risk with the parts working appropriately with accordance with their data sheets. Buying from a reliable and respected vendor should eliminate this problem. The final and most important risk is death/loss to team members who are knowledgeable in specific areas of the project. This can be alleviated by having multiple members working together so that no one person is solely informed about one aspect of the project.
2.11 Project Proposed Milestones and Evaluation CriteriaListed below are the project milestones created by the team members based upon there analysis of the problem. Each milestone will be followed in order before working on the next one. With the completion of each task team members will evaluate the success of each milestone.
7
Table 1: Project Milestones and Overall ImportanceMilestone Importance
Relative Percentage (%)
End-Product Problem Definition High 16Technology Considerations High 20End-Product Design High 17End-Product Implementation Medium 12End-Product Testing High 18End-Product Documentation Medium 11End-Product Demonstration Low 4
Table 2: Milestone Evaluation CriteriaEvaluated Result Numerical
ScoreExceeded/Met 90-100%Partially Met 1-89%Did not Meet Standard 0%
Successful criteria will be determined as each milestone is completed, marginally complete, or not completed by the project advisor and project members. A list will be kept on the status of each milestone.
2.12 Project Tracking ProcedureTo keep the project on time and within the budget project tracking is needed. This will be done for the project plan, poster, design report, final project report, and user/service/tutorial manuals, as well as personal logbooks, and the weekly e-mail. Logbooks will record team members’ daily activities on the project. The weekly e-mails will be complied by the communications coordinator from the teams meeting discussions and progress.
The project schedule made with the help of Microsoft Excel will be used to monitor the groups’ progress in completing the milestones and smaller tasks within.
8
Section 3 Statement of WorkThe following statement of work breaks the project into sections which are identified as critical tasks. Each task may be further broken into subtasks which are necessary for the main task to be completed. The statement of work is critical to how successful the project will be. This section contains the statement of work for Dec07-06’s project.
3.1 Project DefinitionObjective: This task will define the project and all requirements. The
subtasks include the problem definition, end-users and end-uses, and limitation identification.
Approach: The project team will look at previous project attempts and review their documentation. Other information sources will include present market designs, as well as the project advisor and previous project team members.
Expected Results: The end product for the project will clearly define the end-users, end-uses, and limitations.
3.1.1 Problem DefinitionObjective: This subtask will define the expectations for this project.
Approach: Team members and the project advisor will sit down and discuss the problem. Topics to be considered are what transceiver, microprocessor, and batteries should be included in the end-product.
Expected Results: The problem will be clearly laid out and understood and it shall be written out.
3.1.2 End-Users and End-UsesObjective: This subtask will tell who the end product will be designed for and
what applications this project will entail.
Approach: The team will meet with the project clients and discuss the projects’ intended uses as well as the plans they have for the project end product. The team will also consult with the project advisor, this will give the team the knowledge needed to establish and document who this project is being design for and what their plans are for it.
Expected Results: The team will document who the project product is intended for and what they’re going to do with said product.
3.1.3 Limitation IdentificationObjective: This subtask will recognize what this project has for limitations.
Approach: The project team will discuss what components will be used in the end product and the limitations are for these components.
9
Expected Results: The team will have documented the project limitations.
3.2 Technology ConsiderationObjective: This task will seek out the best components appropriate for the
projects’ end product.
Approach: The team will research desired parts for the end product. These will include a transceiver and microprocessor chips as well as rechargeable batteries. The team will consider functionality, implementation, and price that are best suited for the components.
Expected Results: Team will have understanding and documentation of desired project parts.
3.2.1 Technology IdentificationObjective: The project team will identify suitable technologies that are to be
incorporated into the project.
Approach: The team will consult with the project advisor and the past project attempts to determine the best and most appropriate technologies to be put in the project.
Expected Results: The project team will have identified the best technologies to implement in their designs.
3.2.2 Criteria IdentificationObjective: For the team to identify what criteria is expected for the project.
Approach: The team will consult with the advisor to make clear what the documented criteria are for a successful project.
Expected Results: The team has identified and documented all of the projects’ required criteria.
3.2.3 Technology ResearchObjective: To gather information pertaining to appropriate technologies that
will help with the projects end product.
Approach: Once technologies have been identified by the technology identification subtask team members will meet with advisor for their past experience with certain technologies and vendors. The team will make use of this knowledge as well as other resources to see what would be the most beneficial.
Expected Results: The team will have enough information to obtain a suitable decision for the project technology.
3.2.4 Technology SelectionObjective: The team will determine the best course of action to take that will
best meet the requirements of the project.
10
Approach: The team will compare available components and discuss the advantages and disadvantages of each. The most favorable component will be implemented for the project.
Expected Results: The technology deemed best will be used in the end product of this project.
3.3 End-Product DesignObjective: This task will combine the technology considerations into a
complete system which will meet the end products’ functionality requirements.
Approach: The team will research datasheets and previous designs to form suitable designs. The design which appears to be most promising will be taking to the next step of implementation.
Expected Results: Team will have a design which utilizes the technology researched.
3.3.1 Identification RequirementsObjective: The project team will identify the end products’ ideal functionality
and implement several of these functions.
Approach: The team will consult with the project advisor and the past project attempts to determine which functions are the most vital.
Expected Results: The project team will have a feasible list of functions which will allow for the project’s success.
3.3.2 Design ProcessObjective: The project team will construct multiple design alternatives from
the technology researched.
Approach: The project team will design and model several schematics to determine which design will provide the most flexibility and reliability
Expected Results: The project team will have a robust design which will allow for future functionality to be added.
3.3.3 Design DocumentationObjective: The project team will document all of their designs and state which
design is preferred and why.
Approach: The project team will include schematics, pictures, and test results which show which design is preferred.
Expected Results: The project team will have documentation which will allow for the end product to be implemented and may remove doubt as to why this design was implemented.
11
3.4 End-Product ImplementationObjective: This task will construct the several fully functional end products.
Approach: The project team will build several prototype of the design.
Expected Results: The project team will have working prototype.
3.4.1 Identification of LimitationsObjective: The project team will identify the design’s limitation and will
document how this will affect the product
Approach: The team will compare the prototype to existing designs and determine the differences/limitations.
Expected Results: The project team will have fewer limitations than previous/existing designs
3.4.2 Implementation of End-Product DesignObjective: The project will construct up to five communications link
Approach: Once the prototype design has been perfected, a low volume production will be issued and assembly/testing will occur.
Expected Results: The project team will have up to four fully functional communication modules.
3.5 End-Product TestingObjective: The project team will ensure that the communication link’s
functions work as expected and to be certain all design criteria have been met and are in order.
Approach: The team will be to focusing the testing on the major analog and digital functions of the device first with the aid of oscilloscopes, a power supply, a function generator, and a multimeter. The team will systematically go through the modules’ main functions down to minor functions as time permits, with the intention of being quite thorough.
Expected Result: The team will have a module that has been tested with desirable results.
3.5.1 Test PlanningObjective: To come up with a plan that can be easily implemented which will
test the features of the link.
Approach: The team will investigate different methods of testing RF links and make decisions based on time constraints and overall effectiveness and reliability of the method.
Expected Result: The project team will have a plan for testing the module.
3.5.2 Test Development
12
Objective: To develop tests from the test planning document that will analyze the different operations of the link.
Approach: The team will incorporate the use of function generators and oscilloscopes into testing for signal integrity. This will be done as these tools are readily available, easy to use, and to a good degree can be expected to provide accurate testing.
Expected Result: Develop test that are relatively easy to execute and provide varied test of link functions (analog and digital, duplex) using scopes and function generators.
3.5.3 Test EvaluationObjective: The project team will gauge the effectiveness of the module.
Approach: Notes will be taken on the results of the function generator and scope experiments as well as (earlier on in the process) bugs in software. Software testing will be done with the help of debugging software such as Bugzilla.
Expected Result: The test evaluations determined successful by the project team.
3.6 End-Product DocumentationObjective: The project team will provide an owner’s manual, service manual,
and a “cookbook” or tutorial document.
Approach: The owners manual will detail how to use the communications link, the service manual detail any maintenance that may be needed to service the link over time. The tutorial or “cookbook” will allow anyone to use the device as it was made
Expected Result: Produced documents that allow the client to use, maintain, or reproduce the communications link
3.6.1 Development of End-User DocumentationObjective: The project team will develop an overall plan of what will go in
the manuals.
Approach: The team will research other tutorials and owner manuals do finalize a format and style
Expected Result: Documents that provide the client support.
3.6.2 Development of Maintenance Support DocumentsObjective: The project team will create a service manual
Approach: The team will research other service manuals do finalize a format and style
Expected Result: Document which is user friendly and supportive.
3.7 End-Product Demonstration
13
Objective: The project team will present the finished product to the client, faculty advisor, and industrial review panel.
Approach: The team will present the problem, solution, and the final product. They will describe the particulars of the project to some extent as well as features and how to use the communication link.
Expected Result: Successful demonstration of the end product to client, advisor, and the industrial review panel.
3.7.1 Demonstration PlanningObjective: The project team will develop a plan for their various
demonstrations.
Approach: The team will make a PowerPoint presentation for each of the three viewers. The presentation may be adjusted slightly to center on each different one as they may be more or less interested in different things.
Expected Result: Demonstration plans ready for the various audiences.
3.7.2 Faculty Advisor DemonstrationObjective: To present a finished product to the project teams faculty advisor
Approach: The team will tailor the presentation to add or delete what he is interested or not interested in seeing.
Expected Result: A successful demonstration approved by the advisor.
3.7.3 Client DemonstrationObjective: To present the communications link to the team’s client: ECE
senior design.
Approach: The team will present the end product to the client with the focus on the modules’ features and how to incorporate it into future senior design projects.
Expected Result: To satisfy the needs of the clients while letting them become familiar with link.
3.7.4 Industrial Review Panel DemonstrationObjective: For the project team to present the completed project to the
industrial review panel.
Approach: To adjust the presentation to the industrial review panel as the team is so advised by those that have experience presenting to the panel.
Expected Result: The industrial review panel to come away from the demonstration feeling that the project was a success.
3.8 Project Reporting
14
Objective: The project team will document the project progress through the project plan, project poster, design report, final report, and weekly e-mail.
Approach: Throughout the course of the project the team will meet regularly to maintain a careful documented recording to help develop the project plan, project poster, design report, final report, and weekly e-mails.
Expected Results: The team will have the necessary documentation for the project completed.
3.8.1 Weekly E-mailObjective: To keep the projects’ clients and faculty advisor informed through
a weekly e-mail.
Approach: The project team’s communications coordinator will gather the information that the team has produced for each weeks’ progress as well as any problems the team is currently facing.
Expected Results: A weekly e-mail is sent to the projects’ clients and faculty advisor outlining the team’s weekly progress.
3.8.2 Project Plan DevelopmentObjective: The project team will create the project plan documentation.
Approach: The team will divide the reports’ sections up evenly and work on their respective segment. The team will gather the parts that each has worked on into a cohesive document.
Expected Results: The project plan will be completed.
3.8.3 Project Poster DevelopmentObjective: The project team will create and present a project poster.
Approach: The team will work together to come up with a proper layout as well as discuss what information should be included for the poster. The team will then divide the work up among themselves and later combine these into the poster.
Expected Results: The team’s project poster will have been printed and displayed.
3.8.4 End-Product Design ReportObjective: The project team will create a document for the end-product design
report.
Approach: The team will work on sections that are divided up as appropriate. Individual members will then work on their sections and later the team will meet to assemble everyone’s documented sections into a seamless report. Guidelines for the report will follow the senior design handbook.
15
Expected Results: The team will have the end-product completed.
3.8.5 Project Final ReportObjective: The project team will document a final report for the project.
Approach: The team will divide the report into sections corresponding to the work the completed on the project. Team members will then work on their sections individually and come together later to combine them into a report that is consistent in all sections.
Expected Results: The team will have the final report completed.
16
Section 4 Estimated ResourcesFor every project that is proposed, several items are necessary for success. These items include personal effort, financial support, and additional resources. This section includes all the resources which are necessary for the completion of this project
4.1 Personal Effort RequirementsThe personal effort requirements include the amount of time each task outlined in the statement of work will require. These numbers are based upon personal experience and will serve as an estimate for this project. This is shown in Table 3 below.
Table 3: Personal Effort Requirements
17
4.2 Financial RequirementsThe financial requirements are all the monetary cost associated with the project. This includes costs for components, services, equipment, or printing costs. A requirement of this project was for each module to cost less than $100. The numbers below are estimates and may not reflect the actual cost. This is due to the availability of free samples and/or student discounts on project components. The labor cost was figured to be twice the new minimum wage which equals $14.50.
Table 4: Financial Requirements
18
4.3 Other RequirementsTable 5 shown below displays the items needed to accomplish the project. Many of these materials are available at Iowa State University, and they are all considered donated to the project with no added cost. The oscilloscope and power supply will come from Coover’s labs. As for the computers, they constitute campus computers as well as individual project members’ computers and the programs installed within them.
Table 5: Other Requirements
19
20
Section 5 ScheduleThis section includes a detailed project schedule along with a schedule with deliverables such as various reports and presentations.
5.1 Project ScheduleThe figure below portrays the projected schedule for this project. The subtasks have been included below each main task to create a detailed schedule which tracks the project from the beginning.
Figure 1: Projected Schedule
21
5.1 Deliverable ScheduleThe figure below includes a timeline of project deliverables. These deliverables not only include written reports but also presentations.
Figure 2: Project Deliverable Schedule
22
Section 6 Closure MaterialsThe following section contains a closing summary, contact information for the client, faculty advisor, and team members along with references which were utilized by this report.
6.1 Closing SummarySenior design projects that are in need of a RF communications links often times do not have the time or expertise to implement one. This can be avoided if they have access to a universal communications link that is programmable to suit their projects needs. Previous senior design teams have tried to execute such a project but with very limited success. Integrated chips today allow RF issues to be solved much easier and faster than the past. A microcontroller will add data integrity and allow for future expansion. This project will use this advantage to construct such a device and have it companioned with a “cookbook” manual guide. Follow through of this plan will ensure that future senior design teams will then not have to expend as much time on wireless implementation in their projects.
6.2 Project Team Information
6.2.1 Client InformationSenior DesignDepartment of Electrical and Computer EngineeringIowa State UniversityAmes, IA 50011http://www.ece.iastate.edu
6.2.2 Faculty Advisor InformationDr. Yao Ma3107 Coover HallAmes, IA [email protected]
6.2.3 Team Members InformationJoseph Beierschmitt Shawn FreeseElectrical Engineering Electrical Engineering7321 Frederiksen Court 644 Squaw Creek Drive Apt. #4Ames, IA 50010 Ames, IA 50010319-231-2608 [email protected] [email protected]
Jared Leonard Matt RaygorComputer Engineering Electrical Engineering218 Stanton Avenue #20B 1147 65th
Ames, IA 50014 Windsor Heights, IA 50311605-517-0052 [email protected] [email protected]
23
6.3 References[1] “About the FCC.” Federal Communications Commission. 16 Nov. 2006
<http://www.fcc.gov/aboutus.html>
[2] “The RoHS Directive.” National Weights and Measures Laboratory. 2005 <http://www.rohs.gov.uk/Default.aspx>
[3] Peatman, John B. Embedded Design with the PIC18F452 Microcontroller. New Jersey: Princeton Hall, 2003
24
