Software Defined Radio

By: Jeffrey Chang, Theodore Storms, Dylan Kievit, and Brad Eylander

4/30/2009

Table of Contents
Project Overview ....................................................................................................3 Marketing Plan .......................................................................................................5 Quality Plan ............................................................................................................7 Engineering Plan ...................................................................................................12 Engineering Schedule .................................................................................20 Manufacturing Plan ..............................................................................................18

2|P ag e

Project Overview
Introduction
Software Defined Radio (SDR) is a software program that will be able to transmit and receive data through a communication device. The software that SDR will be based off is the open source code GNU Radio. The GNU Radio software is already designed to be implemented using a Universal Software Radio Peripheral Board (USRP board), so the SDR is going to be an addition to what GNU Radio has already is designed to do. The main feature the SDR offers is Quadrature Phase Shift Keying (QPSK) with 512 kilobits/sec data transmission and phase ambiguity resolution. In addition to the SDR program there will also be a soft output slicer which will give the exact coordinates of the data in each possible quadrant.

Objective
Once the SDR is complete the user will be able to run software based simulations using the SDR program. In addition to software simulations the SDR will also be able to use the USRP board(s) to transmit or receive 4 kilobits data packages. The SDR will result in a completely functional device by December 2009.

Team
The group consists of four members Dylan Kievit, Brad Eylander, Jeffrey Chang, and Theodore Storms. Currently each member of the group has contributed to the writing assignments assigned for the project detail. Each member will be working on specific portions of the project. Kievit and Chang are primarily focusing and developing the software, whereas Eylander and Storms will be focusing on testing and performance. All members will be working together on documentation and each will contribute to multiple parts of the project. The formal role of each member of the group is as follows: Engineers: Jeffrey Chang, Theodore Storms, Dylan Kievit, and Brad Eylander Team Leader and Secretary: Brad Eylander Marketing: Theodore Storms Manufacturing: Jeffrey Chang Quality: Dylan Kievit

Product Specifications
Quadrature Phase Shift Keying (QPSK) o Data transmission rate of 512kb/s Transmits and receives using a 60MHz carrier Phase Ambiguity Resolution Soft Output from Slicer Able to run simulations to ensure data is not corrupted when sending data wirelessly
3|P ag e

Able to steam data from the users' hardware using Fast Data Compression or Forward Error Correction (FEC) Able to calculate the noise ratio for data transmission Customizable o Able to customize the source code software package provided by GNU radio o User has the freedom to add noise o User is able to transmit radio signals

Marketing Analysis
Potential customers include any company that utilizes any sort of signals testing for their communication systems. The market penetration of the SDR is broad and can range from private defense/military contractors, NASA, telecommunications companies, technology development companies, and amateur radio enthusiasts. Our product implements more functionality and allows for customization for other potential future uses with minimal upgrades. Current cost estimates place the entire package with software and fully functional USRP board with peripherals at $788.

Schedule
The engineering schedule was designed primarily around a four month window from August through December 2009 in order to correspond with the Fall 2009 semester. In the preceding three months, team the tasks scheduled are research, giving ample time to become familiar with QPSK and continuous stream data packetizing. Specifically, information regarding implementation of these techniques in software will be especially sought after. Design and implementation will then proceed, iterating through each software module. The modules will be tested as they are written, with more rigorous testing done after major features are completed. Careful attention will be paid to documenting the processes necessary to enable any future teams to replicate the achieved results.

Budget
The cost of production in four months which includes rent, power, insurance and engineering cost is $85,420. The manufacturing cost of materials and labor is $15 per unit. The cost of each SDR unit, including the software and hardware is $788.

4|P ag e

Marketing Plan
The software defined radio (SDR) has a myriad of potential applications, thereby making the marketing penetration broad. Software Defined Radio can replace any signal testing hardware as long as it is properly programmed and configured while the SDR has the proper hardware to receive the signals whether it be through USB, parallel port, TCP/IP, RF antennas or any other communication devices. Potential customers for the SDR would be any company, large or small, that utilizes any sort of signals to test their communications systems. Governmental agencies such as NASA and the military or private defense contractors can benefit greatly by the SDR since wireless communication is essential for communicating timely and effectively. Telecom companies (AT&T, T-Mobile, Spring, Verizon, etc...) as well as mobile phone companies (Nokia, Motorola, LG, Apple, etc) can benefit from testing reception for phones or antenna signals with towers and satellites. TV and radio stations can also use the SDR to test their broadcasting signals. The potential for the SDR is limitless and is constrained only by processing speed and functionality. The SDR would also appeal to people interested in amateur radio projects. One popular aspect of the SDR is the ability to allow customers to manipulate and implement new source code to suit their needs; which was previously added to GNU Radio. This makes the SDR ideal for the average amateur radio hobbyist to engage themselves in since there is no fear of ruining the device. Our main client, however, is Dr. Brian Banister of Comtech AHA. Eventually, Dr. Banister plans on combining the SDR with Comtech AHAs forward-error correction and fast data compression PCI-E boards in order to transmit and receive data using the SDR, and during the process can implement their own error checking and compression software to ensure it is giving the results desired by the company. The SDR will include (but not limited to) the following key features requested by the main client, Dr. Brian Banister of Comtech AHA. Wireless Communication Testing o Companies that deal with light or heavy communication will be able to run simulations to ensure data is not corrupted when sent wirelessly. Phase Ambiguity Resolution o The SDR will perform a phase check to clarify the signal is aligned properly with the proper phase shift to ensure provide the correct signal for QPSK modulation. Quadrature Phase Shift Keying (QPSK) Modulation o Able to code/decode a signal modulated using QPSK and apply the soft output from slicer to ensure the data is in the right quadrant. Fast Data Transmission o Able to send and receive data at a minimum of 512 kilobits/sec with packet sizes of 32 kilobits with a leading 32 bit unique word identifier. Loop-Back Mode
5|P ag e

GNU Radio software should be able to simulate the system including adding noise to a generated signal to ensure the SDR is working properly. This can be done if there is no transmitter or receiver present. Signal to Noise Testing o Test to make sure the signal to noise ratio is within acceptable levels to ensure correct signal processing and data decoding. Customizable o GNU Radio allows for the addition of new modules so users can customize and create their own features. GNU Radio also comes with a complete HDTV transmitter and receiver, a spectrum analyzer, an oscilloscope, concurrent multichannel receiver and a significant collection of modulators and demodulators. When marketing the final product, the SDR will need be competing with an assortment of testing products. Any product that is customized for testing some sort of signal can be replaced with the SDR as long as there is proper hardware for the SDR to receive input. This is a much cheaper and efficient method of testing rather than buying specifically tailored hardware that could cost the company much more money when the SDR can run on any computer running a Unix-based system. Sales and Distribution of the SDR will be handled by Comtech AHA. Comtech AHA already has competent, talented agents posted around the globe who can be relied on to gather data on possible buyers and company interests. These agents will be able to distribute the products desired by the companies as well. The SDR will be distributed to the customers in a two possible packages. One package will include one modem (with the USRP board inside), one radio frequency (RF) transmitter hardware and/or one RF receiver hardware, cables and a CD of the SDR install disc. The other package is an option if the customer wants to by both the transmitter and receiver package, which will include two modems and both the RF transmitter and receiver. When the SDR is distributed, a minimal amount of instructions will need to be included. The product works directly out of the box. There will be an instruction set included on how to connect and configure the transmitting and receiving ends of the wireless communication simulation. Also included will be a link to the GNU Radio software site so users can download the software to use the SDR for free. Included on the website are frequently asked questions (FAQ) page and instructions about installing and using GNU Radio. Implementation of modules for GNU Radio to work with our hardware will be included.

6|P ag e

Quality Plan
Quality Specifications
Quadrature Phase Shift Keying (QPSK ) o Data will be transmitted at 512 Kb/s Transmits using a 60MHz carrier Phase Ambiguity Resolution Soft output from Slicer Loopback mode o Test a simulated example across a coaxial line Wireless Communication Testing o The modem will be able to run simulations to ensure data is not corrupted when sending data wirelessly. Low End Satellite Modem o Additional hardware will be needed such as a satellite dish, low noise amp, and a down-converter o Able to receive data from a satellite o Low cost method to have a receive client Digital Communication Hardware Testing o Able to steam data from the users hardware using Fast Data Compression or Forward Error Correction (FEC) Able to calculate noise ratio within acceptable levels for data transmission Customizable o Able to customize the source code software package provided by GNU Radio o User has the freedom to add noise o User is able to transmit radio signal

Testing procedure
To ensure the product functions according to the specifications provided a series of tests will be performed. The testing procedure will be run in the following order: Test the GNU Radio program o Determine actual bit-error rate o Spectrogram being used 2 MHz of Bandwidth allocated o Able to pass data o Able to handle phase change or a frequency offset o Ensure the data throughput of 512 Kb/s Test the Universal Software Radio Peripheral (USRP) board o Ensure that GNU Radio is able to communicate to the USRP board o Ensure it is able to run from a USB cable o Ensure the USRP board is using QSPK
7|P ag e

o Ensure the USRP board can transmit at the frequency specified Test the effect of noise added to the data being transmitted Test the environment the modem is able to run in o Humidity, temperature, impact, and vibration The anticipated final product, Software Defined Radio (SDR), will be a software based off the open source GNU Radio project; therefore, the production of the project is going to be small. The main buyers for the product will be advanced and knowledgeable users such as, amateur radio operators, corporations interested in testing their hardware data compression and forward error correction hardware, and low end satellite modems. Due to the small scale of buyers, testing will primarily be verification that the pre-purchased USRP board is functional. The testing process will take 1-2 days of running software and RF based simulations to make sure the USRP board works. The GNU Radio program will be tested prior to sales for about 2 weeks of run time to make sure the GNU Radio is working correctly. Once it has been determined that the program works with the USRP board, testing per client will consist of 1-2 days on running the program on the USRP board. Further, a minor environmental test can be run to ensure the product will still function in desired working areas of indoors with standard indoor temperatures of 60-80 degrees Fahrenheit. Also, the product will be tested for overshoot and undershoot in temperature to ensure it works properly in the desired environment.

Verifying Prototype
Software: To ensure that the GNU radio program written for the SDR transmits data correctly, data will be tested using a software loop-back mode across a 60MHz carrier. In the software loop-back mode, known data will be transmitted in the simulation and if the known data corresponds with the received data than that will confirm the SDR program theoretically can transmit data. To test data transmission using the USRP Board, known data will be transmitted across a 60MHz carrier to a receiving USRP board. If the data received is the same as the known data, it will confirm that the SDR program is able to transmit data correctly. Hardware: To test the efficiency of the data being transmitted, noise will be added during data transmission to find which noise level has the most effect on the desired signal. By adding multiple interference noises to the desired signal, a table will be able to show the noise that caused the most problems, allowing a better implemented SDR radio error correction to be adjusted. Finished Product: Once the SDR can function to its desired functionality, additional power consumption tests and environmental tests will be performed. The environmental test procedures include vibration tests, humidity tests, impact tests, and temperature tests. During the environmental test, basic functionality will be tested for the SDR to ensure that the product runs correctly. Basic
8|P ag e

functionality tests include streaming and receiving data and power consumption of the USRP board. Documentation: A major deliverable associated with this project is documentation to ease further expansion of the Software Defined Radio (SDR) by future teams. Before the current stage of the project can be considered complete, this documentation will need to be thoroughly tested in order to ensure a minimal learning curve. Testing of the documentation will consist of several stages: Stage 1: After getting a software module functioning, the required steps should be retraced to ensure general replication is possible. Stage 2: Once the software is at a finished stage, all steps should be retraced, as specified in the documentation, by each group member in order to demonstrate the finished product is reproducible by those familiar with the project. Stage 3: When the documentation is sufficient for reproduction by those familiar with it, third parties should be brought in and observed while following the provided instructions. Any points of confusion should be clarified in writing and retested before a final draft of the documentation is produced. By completing these three stages of testing, there can be reasonable assurance that the team to follow up on this project will only need to spend minimal time reaching the current state. The continuance of this rigorous documentation strategy will ensure that each project team can accomplish as much as possible.

Reliability
The following reliability tests shall be performed for the purpose of identifying deficiencies in product design and/or manufacture. 1. 2. 3. 4. 5. The product will be operated in a cooled environment (0-45 degrees Fahrenheit). The product will be running in a heated environment (100-160 degrees Fahrenheit). The product will be shook with a vibrating force equal to that of a jackhammer. The product will be running for two-to-three weeks nonstop. The product will be exposed to different levels of moisture and humidity.

The lifetime of the SDR can be estimated by the lifetime of the parts included with the USRP board. Analog-to-digital and digital-to-analog converters have a life expectancy of 60 years. The life expectancy for the FPGA directly corresponds with the number of times the product is used. Input-output ports last until the contacts either break from outside source or corrosion. Both factors depend upon how the ports are treated and if they are used appropriately. Finally the coaxial cable used to connect the receiver and transmitter has a life time of about 20 years. With the amount of human error and natural cause, the indoor environment, along with the numeric life expectancies for the converters and coaxial cable, the

9|P ag e

life expectancy of our product (amount of time until a new piece is required) is about 15 years. However, the overall system will never need to be replaced since it is defined by software. Lifetime of the radio is mainly dependent upon the USRP board because the rest of the SDR is defined by the GNU Radio software. If pieces of the USRP board lose effectiveness then those pieces can and will need to be replaced in order to restore the SDR to proper working condition. For example, if some of the ports stop reading or writing data. The only problem that can stem from the software are updates. Updates are easy to implement and are not so much of a worry for the lifetime of the product. Potential Failure: Looking at the hardware for the SDR, it only consists of USB to coaxial cable and the USRP Board. The USB to coaxial cable may only make mistakes if broken or worn out. However, for the USRP board there are a number of items on the board which can malfunction leaving the Radio in poor operating condition. These possible malfunctioning items are as follows: reprogrammable FPGA, four analog to digital converters, four digital to analog converters, and numerous auxiliary digital and analog inputs and outputs. Therefore, the main problematic part of the SDR comes from the USRP Board. Since the rest of the SDR is the software, the only other error can come from the operator. Below is a FMEA table to represent the SDR:
Part Potential Fail Mode Potential Effect SEV Potential Cause OCC Current Controls DET RPN

USB to Coaxial Short Cable Circuit USB to Coaxial Cable FPGA Open Circuit Power Surge Short Circuit

No output/input 5 to Board No output/input 5 to Board Out of Use 2 Temporarily No 5 output/input to Board No output/input 5 to Board

Manufacturing 3 Process Manufacturing 3 Process Lightning

Manufacturing 1 Tests Manufacturing 1 Tests Surge Protector

15

15

FPGA

Supplier Quality

Manufacturing Tests 1

10

FPGA Analog to Digital /Digital to Analog Converters

Open Circuit

Manufacturing 3 Process

Manufacturing Tests 1

15

Unable to convert Partial 4 certain output/input frequencies

Manufacturing 3 Process

Manufacturing 1 Tests

12

10 | P a g e

Analog to Digital /Digital to Analog Converters Analog to Digital /Digital to Analog Converters

Short Circuit

No output/input 5 to Board

Manufacturing 3 Process

Manufacturing 1 Tests

15

Open Circuit

No 5 output/input to Board

Supplier Quality

Manufacturing 1 Tests

10

Auxillary Digital Some ports and Analog Error in will be Inputs and 3 some Ports unable to Outputs send/receive data Auxillary Digital Open and Analog Circuit Inputs and Outputs Auxillary Digital and Analog Short Inputs and Circuit Outputs

Corrosion

High Quality Components

18

No output/input 5 to Board No output/input 5 to Board

Manufacturing Process 1

Manufacturing 1 Tests

Supplier Quality

Manufacturing 1 Tests

10

Table 1 - FMEA: Scale is from 1-5, 1 being excellent and 5 being severe

Regulatory Certifications
The USRP board should meet the certifications guidelines set forth by the Federal Communications Commission (FCC) under the Federal Code of Regulation (CFG) FCC Part 15 which covers the regulations under which an intentional, unintentional, or incidental radiator can be operated without a license. Testing for compliancy under FCC regulations can be done via laboratories accredited by the National Institute of Standards and Technology (NIST) or other programs approved by the FCC. The USRP board qualifies as a Class B digital device. It should be certified to provide reasonable protection against harmful interferences. Should we decide to expand the USRP board with other peripherals such as an antenna for receiving and broadcast radio waves, further compliance under FCC regulations must be made such that the device does not interfere with other signals. For transmissions, only spurious emissions are permitted on a limited amount of frequency band so we need to ensure our antenna only works within the specified range and not interfere with government-run or commercial frequency bands.

11 | P a g e

Engineering Plan
Detailed Specifications
Implementation of QPSK to the GNU Radio software: Quadrature Phase Shift Keying (QPSK) utilizes four phases, equally spaced, represented by 00, 01, 10, 11. This method enables two bits of data to be encoded per symbol sent. This allows quicker data transfer and maintains the initial desired bandwidth. However as the order of phase shift keying increases so does the likelihood of an error occurrence.

Figure 1 QPSK phase graph

512 Kb/s transfer rate: It is desired for the data transfer rate for the SDR to be 512kb/s. This is just a setting within the GNU Radio software that the SDR is based off of. Other data rates may be tried to see what the software may run at efficiently, but the primary specification will ensure peak performance at 512kb/s. Frequency is within 2MHz bandwidth centered about 60MHz: This requires a band-pass filter. The filter will need to encapsulate 2MHz bandwidth at a carrier frequency range of 59MHz to 61MHz. Phase Ambiguity Resolution: Phase Ambiguity Resolution will be implemented in the SDR. Since it is not clear which phase the data is in, it is necessary for the user to do a phase check to clarify the data is in the proper quadrant. This will allow for proper data recognition. Soft Output from Slicer: This specification desires the exact location of the data. It will define exactly where in the region (quadrant) the data is and output the coordinate location. This will be implemented after the phase ambiguity resolution so it is certain the data is in the right quadrant. Ability to run in a loop back mode in software: This specification ensures the software is running properly. The SDR program will be able to simulate the system if there is no transmitter or receiver present.
12 | P a g e

Codeword at the beginning of each data string: This is implemented by the SDR software. The software attaches a codeword to the beginning of each packet of data in order to identify where each packet begins and ends. The unique word will be the same for each packet.

Technical Description
The software defined radio will consist of two Universal Software Radio Peripheral (USRP) boards, a computer, and up to two antennas. The USRP board will be connected to the computer with a USB or coaxial cable. If there are antennas used for either the receiver or the transmitter, the USRP board will be connected to the respected antenna. Figure 2 below is a ruft diagram representing the overall system.

Figure 2: Diagram outline for the Software Define Radio (SDR) system

The USRP Boards consist of a Field Programmable Gate Array (FPGA), 4 high-speed analog to digital converters, 4 high-speed digital to analog converters, and analog and digital I/O ports. The FPGA allows the signal processing of the computer generated or outside received data signals. Analog to digital and digital to analog converters enable the compression of a continuous signal into a discrete signal or transforms a discrete signal back into a continuous signal. This will enable the incoming data to be in binary form. The digital and analog input output ports are there if someone desires to combine the board with other hardware. The SDR software package will be used to modulate the data coming in and out. Within this software package, the transfer rates can be set, the type of modulation will be applied, the phase ambiguity will be implemented, and the exact phase of the data will be determined. SDR and the related software modules are Python and C++ based. Environmentally, the overall radio is designed to work in 0 to 160 degrees Fahrenheit. The product should not be operated under water or in damp areas. The SDR is designed to be used indoors at reasonable temperatures, but in case of sitting in a window or power outage in a winter storm, the system has been designed to sustain itself at a range of temperatures. The USRP should meet the certifications guidelines set forth by the Federal Communications Commission (FCC) under the Federal Code of Regulation (CFG) FCC Part 15 which covers the regulations under which an intentional, unintentional, or incidental radiator can be operated without a license. Testing for compliancy under FCC regulations can be done via laboratories accredited by the National Institute of Standards and Technology (NIST) or other programs approved by the FCC. The USRP board qualifies as a Class B digital device. It should be certified to provide reasonable protection against harmful interferences.
13 | P a g e

Because there is an antenna as well it must satisfy CFG 47 part 17 for the antenna structure regulation rules. Also the antenna must satisfy the obstruction and notification rules found in CFG 14 part 77. These two CFGs give the restrictions for antenna structure and interference rules. For transmissions, only spurious emissions are permitted on a limited amount of frequency band, so it must be ensured that the antenna only works within the specified range and will not interfere with government or commercial frequency bands.

Required Resources
The following is a preliminary categorized list of the physical resources that will be required to complete this project.

Hardware
Oscilloscope, Wire Probes, 2 USRP boards, Band-pass filter

Peripherals
1 online based server, 1 software storage server, 1 printer, 1 printer/scanner,

Office Supplies
Coffee maker, tea, soda, fridge, microwave, microwave oven, printer paper, lab notebooks, writing utensils, and blank CDs

Workstation
1 monitor , 1 laptop with Windows and VMware, 1 surge protector, 1 Chair, 1 Desk, and 1 white board

Software
Commercial: MATLAB and Windows XP Freeware: VMWare, Ubuntu, GNU Radio, Google Docs, and Open Office

Employment
Professional Engineer: Dr. Brian Banister Student Engineers: Jeffrey Chang, Ted Storms, Dylan Kievit, and Brad Eylander

Engineering Budget
Student engineering time: $30/hr Professional engineering time: $100/hr Facilities: 100sq/ft per team Workstation: $1,420
14 | P a g e

o Include: monitor - $200, laptop with windows - $1000, surge protector - $50, Chair - $50, Desk - $100, white board - $20 Peripherals: $5,000 o Include: Online server - $2,000, storage server - $2000, printer - $300, printer/scanner - $700 Software: $100 o Include: MATLAB - $100, Windows (with laptop package), and freeware 100MHz Oscilloscope: $10,000 Prototyping parts and systems: $710 o Include: USRP board - $700, Band-Pass filter - $10 Manufacturing: Replication Plant - $0.10 per CD Tooling/NRE: USRP Board purchase, $700 per order Office and miscellaneous: $1,480 o Include: Coffee Maker - $50, coffee - $20, tea - $10, soda - $10, fridge - $1000, microwave - $70, microwave oven - $40, printer paper - $10, lab notebooks $100, writing utensils - $20, blank CD's - $50, large whiteboard - $100

Risk Factors
The following risk factors must be taken into account during the planning, design and implementation stages of this project. Potential extensive C++ programming required The SDR is coded in mainly C++. The project may require modifications to certain modules or even go so far as to create additional modules in order to complete our objective. Thus, extensive C++ programming experience of knowledge may be required to accomplish this task. Potential python programming required The graphical user aspect of SDR is coded in python. In order to change the layout and other various features of the graphical interface, some knowledge of the python programming language will be required. Potential VHDL programming for the USRP board The USRP board comes with an on-board FPGA that is pre-programmed for use with software defined radio. However, being a FPGA, it is possible to customize it to suit project requirements should the need arise. Hardware Failure Hardware failure can delay our project especially if it is the USRP board that breaks. If the USRP should break, it could potentially set the group back weeks since a new order would have to be placed for a replacement USRP and it could take awhile for the vendor to fill that order. Other hardware failures will only be minor inconveniences.

15 | P a g e

Software Updates Modifications to the original GNU Radio software could potentially cause the SDR software to stop working as intended. Not only that, but GNU Radio itself could get updated or a new version could be released such that it could interfere with the SDR software. Schedule Conflicts There are no current scheduling conflicts so far for spring semester but for fall semester, it is possible that the group might have scheduling conflicts that limit the group's ability to work together and meet on a regular basis. Summer Break The group has three months off in between fall semester and spring semester and as such, may have other commitments that limit ability to work or keep up with project development. The project may be placed on hiatus should group members be unable to work on it throughout the summer. Knowledge of digital modulation (QPSK) and data signals One of the requirements for the project is to ensure that the software defined radio be able to recognize and modulate/demodulate digital signals, especially QPSK. Group members need to put in extra effort to understand the requirements of QPSK as well as phase ambiguity resolution in order to program the software defined radio to meet specifications. Knowledge of Filters There will be a band-pass filter to isolate the frequency (59 MHz ~ 61 MHz) we use. Group members have in-class experience with filters but refreshing the knowledge of filters may be useful should the need for other filters arise. Knowledge of certain inputs (USB, serial, TCP/IP) The USRP board uses a USB connection to connect to the software defined radio running on a computer while it accepts inputs from any number of sources. Knowledge of different input sources may be useful in configuring the board or the software to receive data from those inputs. Knowledge of transmitting and receiving radio frequency signals It is possible to attach an antenna to the USRP in order to receive and broadcast radio transmissions. Should the need arise, group members will need knowledge of receiving and transmitting data via radio frequency. Data Packet Recognition The SDR needs to recognize data packets received based recognizing the 32-bit unique codeword at the start of each 4 kilobits data packet and subsequently lock onto the signal. Should there be noise introduced to the signal, the software needs to determine if the signal is reliable or not. Thus, research needs to be done in regards to how the software can do this efficiently and report results back to the user.

16 | P a g e

Engineering Schedule
The engineering schedule was designed primarily around a four month window (August through December 2009) in order to correspond with the Fall 2009 semester. In the preceding three months, team member schedules are currently unknown, so the only tasks scheduled are research, giving ample time to become familiar with QPSK and continuous stream data packetizing. Specifically, information regarding implementation of these techniques in software will be especially sought after. Design and implementation will then proceed, iterating through each software module. The modules will be tested as they are written, with more rigorous testing done after major features are completed. Careful attention will be paid to documenting the processes necessary to enable any future teams to replicate the achieved results. The scheduled tasks are assigned as shown in order to effectively utilize the skill sets of each team member. These skills are outlined below: Team Member Skill communications, controls, power, signals, wave guides & antennas Brad Eylander controls, power, signals, wave guides & antennas Theodore Storms software design, digital systems, wave guides & antennas Jeffrey Chang communications, software design, digital systems, signals Dylan Kievit
Table 2: Team engineering experience

See attachments (pages 20-23) for preliminary engineering schedule. This schedule is based on 3 hours of work per person per business day.

17 | P a g e

Manufacturing Plan
Manufacturing Process
Manufacturing the Software Defined Radio (SDR) will be operated in an available workspace. No assembly will be required for the SDR before being shipped to the buyer. The Universal Software Radio Peripheral (USRP) boards will be purchased from Ettus Research LLC and shipped to the workspace address. When the USRP Board arrives at the workspace, the USRP board(s) and the cables included in the USRP board(s) will be combined with assembly instructions and a 59-61MHz band pass filter. These components will then be placed into a box along with Styrofoam packing and shipped via United States Postal Service to the buyer.

Cost of Production
The initial cost of production consists of rent and utilities for a workspace as well as the labor of four engineering students. These costs assume the initial productions period will be around four months in order to produce a working prototype according to specifications. Further costs will be largely per-unit, as the production volume is expected to be low, so there are no plans for permanent manufacturing facilities. The following table lays out the expected: Production Cost Source Rent Home Office Power Insurance Engineering Total Production Cost
Table 3: Production Cost

Monthly Cost $825 $130 $400 $40/engineer/hour $1,355 + labor

Projected Total Cost (4 mo.) $3,300 $520 $1,600 $80,000 $85,420

Cost of Manufacturing
The cost of manufacturing consists of packing, shipping and labeling costs, as all parts are purchased from third parties. The following table lays out these costs. Process Cost per Unit Packing and Labeling Materials $15 Labor $5 Shipping $15 Total Manufacturing Cost $35
Table 4: Cost of Manufacturing

18 | P a g e

Bill of Materials
All materials are to be purchased as finished products, aside from the instruction manuals and software discs, which will be produced in low volume. The instruction manuals will be produced, as needed, and printed at Cougar Copies or another printing shop. The software discs will be outsourced from Oasis Disc Manufacturing. Part Universal Software Radio Peripheral Board 2x RF Cable USB Cable Power Supply 59-61MHz band pass filter Instruction Manual (printed) Compact Disc Total Cost Manufacturing Total Cost (packed & shipped)
Table 4: Bill of Materials

Supplier Ettus Research Ettus Research Ettus Research Ettus Research Beach Audio Cougar Copies Oasis

Cost $730 Included in USRP cost Included in USRP cost Included in USRP cost $20 $2 ~$1 $753/unit $35/unit $788/unit

With a sale price of $999, $211/unit is made, so $85,420/$211 = 403 units must be sold in order to break even. The sale price can be raised or lowered depending on the results of a more thorough market analysis. The choice to buy the USRP board from Ettus was made by the sponsor, Dr. Brian Banister of Comtech AHA. Dr. Banister decided it would be best to purchase the board rather than make it due to opportunity cost.

Future Considerations
The current resources listed are the resources required to continue the production of the Software Defined Radio. In addition to the SDR program and the USRP Board, the team has plans to expand the company's products by adding more modules to the SDR program and upgrading the USRP Board to USRP Board 2. Adding more modules and having an upgraded USRP board will increase the cost of production and the Bill of Materials.

19 | P a g e