Iowa State University
Mobile DAQ
PROJECT PLAN
Project number: May05-30
Client
National Instruments
Marius Ghercioiu
Faculty Advisor
Dr. Morris J Chang.
Team Members
Matthew D. Goedken, CprE
Daniel J. Hyndman, EE
Amber T. Vo, EE
Duc H. Vu, EE
EE491/Fall2004
Oct-4-2004
TABLE OF CONTENTS
List of Figures iii
List of Tables iv
List of definitions v
Introduction 1
Abstract 1
Acknowledgement 1
Problem Statement 1
Operating Environment 2
Intended User(s) and Intended Use(s) 2
Assumptions and Limitations 2
Assumptions 2
Limitations 2
Expected End Product and Other Deliverables 3
Proposed Approach and Statement of Work 3
Proposed Approach 3
Functional requirements: 3
Constraints considerations: 3
Technology considerations: 4
Technical approach considerations: 4
Testing requirements considerations: 4
Security considerations: 5
Safety considerations: 5
Intellectual property considerations: 5
Commercialization considerations: 5
Possible risks and risk management: 5
Project proposed milestones and evaluation criteria: 6
Project tracking procedures: 6
Statement of Work 8
Problem definition: 8
Technology considerations and selection: 8
End-product design: 8
End-product testing: 8
End-product documentation: 8
End-product demonstration: 8
resources and schedules 9
Resources 9
Tasks Definitions 9
Other Resources: 11
Estimated Project Cost 11
Schedules 12
Tasks List 12
Gantt Chart: 12
Project Team Information - Summary 13
Project Team Information 13
Client: 13
Faculty Advisor: 13
Team Members: 13
SUMMARY 14
List of Figures
Figure 1. Gantt Chart of Tasks 12
List of Tables
Table 1. Estimated Effort in Hours 9
Table 2. Other Resources 11
Table 3. Estimated Cost of Project 11
Table 4. Scheduled Tasks 12
List of definitions
PDA: Personal Digital Assistant, a lightweight consumer electronic device that looks like a hand-held computer but instead performs specific tasks; can serve as a diary or a personal database or a telephone or an alarm clock etc
Mobile DAQ: The Mobile Data Acquisition is designed exclusively for computers and PDAs that support Bluetooth wireless communication.
LabVIEW: Laboratory Virtual Instrument Engineering Workbench (graphically programmed computer language for real-time instrumentation LabVIEW is the host application development environment for MobileDAQ applications.
Bluetooth: A specification for short-range radio links between mobile computers, mobile phones, digital cameras, and other portable devices.
EKG sensor: Electrocardiogram or ECG sensor, measures cardiac electrical potential waveforms(voltages produced during the contraction of the heart).
VI: Virtual Instrument
NI: National Instruments.
i
Introduction
Abstract
The goal of this project is to develop a method of using Vernier’s EKG sensor with the NI Mobile DAQ. The Mobile DAQ must then communicate with a PDA using the Bluetooth protocol. The output of the sensor will be displayed in a LabVIEW module.
The devices must all be researched and studied to find out how they will work together. LabVIEW must be learned so that the module can be built. A manual must be provided to instruct users on how to use the module and devices.
The end result will be the creation of a system that can be useful in teaching as well as being a cheaper alternative to normal EKG machines. It could possibly be a useful monitoring tool in a veterinary hospital or a nursing home. This is important because it offers a cheap EKG monitoring device to places that would otherwise not have them.
Acknowledgement
Thank you to National Instruments for supplying the Mobile DAQ, electronic copies of the Mobile DAQ manual, two Bluetooth enabled PDA’s, and the software that is necessary to design the module.
Thank you to Vernier for supplying the EKG sensor and information on how it functions.
Problem Statement
The goal of this project is to design system using the NI Mobile DAQ, a Vernier EKG sensor, and a Bluetooth enabled PDA. The sensor must be connected to the Mobile DAQ in such a way that the Mobile DAQ can send information from the sensor to the PDA or Laptop, which will then be displayed in a LabVIEW module.
This goal will be realized studying how the equipment works and learning how to use LabVIEW and the Bluetooth protocol. After the research phase, the LabVIEW module will be written and the devices will be connected.
Operating Environment
The risks in the expected environment for this module are relatively few. If used in an ambulance, it would be probably that it would be dropped or shook around. However, if used in a nursing home or a classroom, it is unlikely that any seriously damaging situations would occur on a regular basis.
Intended User(s) and Intended Use(s)
This module has several different applications and could be used by many people. Some possible users are paramedics, lifeguards, or even teachers. It should be able to be used by high school students or any adult with a high school education. A user will need to have some knowledge of how to use a computer.
This module will be used in a variety of situations. Its main application will be in situations where it is useful to monitor heart rate, but the bulky machines used in hospitals are not available. This could include use in an ambulance or at a nursing home. The Mobile DAQs could be used to monitor many heart rates on a single machine to allow doctors to respond more quickly when there is an emergency.
Assumptions and Limitations
There are many assumptions and limitation the product needs to adhere in order to operate safely and correctly.
Assumptions
The list below is not all inclusive; it states the necessary condition that ensure proper working conditions for the Mobile EKG sensor.
· The PDA interface will be clear and easy to use.
· All necessary EKG data will be displayed in the PDA interface.
· The manual will explain the proper use of the sensor and the PDA interface.
· The Mobile DAQ is powered by two AA batteries.
Limitations
The list below is not all inclusive; it states the physical limitation of the Mobile EKG sensor.
· The Mobile DAQ must stay within Bluetooth range of the PDA.
· Device is not reliable for use in serious medical operations.
· User must be able to run LabVIEW module on their PDA.
· Devices cannot operate underwater.
· Devices cannot operate outside of the temperature range 0˚ to 50˚ C.
· Devices cannot operate above altitude of 2000 meters.
Expected End Product and Other Deliverables
The final product that will be presented to NI will include the LabVIEW module as well as the EKG sensor and Mobile DAQ. Also included will be an in-depth manual on how to use the sensor and the LabVIEW module.
Proposed Approach and Statement of Work
The following section entails the propose approach of building the Mobile EKG sensor using the National Instrument MobileDAQ and the Vernier’s EKG sensor. It will also state the necessary steps that will be taken to perform the task.
Proposed Approach
This section will discuss all the requirements and considerations that is necessary to perform the task. It will also address risks and goal settings.
Functional requirements:
1. Display Data:
The data taken by the EKG sensor should have the capabilities of being displayed graphically on either a Bluetooth enabled PDA or a Bluetooth enabled laptop.
2. Portable:
The collective end product including the EKG sensor, MobileDAQ, PDA, and laptop should all be portable and functional in any location.
3. Accurate:
The end product should be able to take data which is accurate when measuring someone’s heart rate.
4. Communicate Wirelessly:
The MobileDAQ should be able to communicate wirelessly (through Bluetooth) with the Bluetooth enable PDA or laptop.
Constraints considerations:
1. Distance:
A Bluetooth equipped device can only communicate wirelessly with another Bluetooth equipped device if the 2 devices are within a certain range of each other. The end product demonstration maximum range between the MobileDAQ and the PDA will be 10 feet.
2. Connection to Host:
The EKG sensor will not take any data if not connected to a host (something with a heart beat).
2. Operating Conditions
The MobileDAQ setup can only be used in certain physical conditions, see the list of limitations in the above section for a general description of the operating conditions.
Technology considerations:The section below discusses the available technologies and technology selection.
1. LabVIEW:
LabVIEW is to be used for the algorithms used in processing the data. There are several different versions of LabVIEW, which may have a small effect on the programming section.
Technical approach considerations:The section below discusses the available physical implementation and physical implementation selection.
PDA vs. Laptop:
The MobileDAQ can connect wirelessly to either a Bluetooth enabled PDA or a Bluetooth enable laptop. The team will look at which is readily available for us to use and test with, which is cheaper, and if either has any certain limiting capabilities.
Testing requirements considerations:The section below discusses the conditions require for testing of the final product.
1. Location:
The placement of the EKG sensors on the body while doing the testing could effect how the EKG sensor reads out the data. As long as the location is kept constant through the testing process, this should not be a problem.
2. Consistency:
The data results from the EKG sensor may work with the algorithms written in LabVIEW for the Bluetooth enabled laptop, but will the program work when loaded into the PDA.
3. Length of test:
The team must decide how long it wish to record the data being taken by the EKG sensor. The team must also decide what length of time is appropriate.
Security considerations:
The team are working with already developed and released equipment which have no foreseen security considerations.
Safety considerations:
This project does not require us to manufacture or dispose of any materials. There are no foreseen safety considerations.
Intellectual property considerations:The below section discuss possible intellectual property issues, and ways to deal with such situation.
1. MobileDAQ:
National Instruments has donated a MobileDAQ unit to the group for this project. MobileDAQ will be returned to NI at the completion of the project.
2. EKG Sensor:
National Instruments has worked with Vernier to have the EKG sensor to be used with the MobileDAQ donated to the group for this project. The EKG sensor will be returned at the completion of this project.
3. PDA:
National Instruments has donated a Bluetooth enabled PDA with the necessary software for the group to use for this project. The PDA will be returned to National Instruments at the completion of this project.
Commercialization considerations:The section below discusses possible commercialization issues that may arise from the completion of the task.
Product use awareness:
The project involves products which are already available to the public and instantiates them into real life situations. End product demonstration will show how and why it is useful in various environments.
Possible risks and risk management:The section below discusses the possible risks and its solution when accomplishing this task.
1. Loss of a team member:
In the event that the team loses a member, the man hours lost will be divided between the remaining members to ensure we stay on track.
2. No experience with LabVIEW:
If the group discovers that it cannot understand the LabVIEW program, it will make an effort to contact either someone at Iowa State University who has experience with it, or someone at National Instruments who is familiar with the program.
Project proposed milestones and evaluation criteria:
1. EKG sensor testing:
The first milestone will be to get the EKG sensor operating correctly. The evaluation criteria consists of checking whether the EKG sensor connects correctly to the MobileDAQ, if it begins taking data from the source, and if it sends data to the MobileDAQ.
2. MobileDAQ testing:
The next milestone is getting the MobileDAQ to operate correctly. To evaluate the successfulness of this milestone, the team needs to examine if the MobileDAQ is correctly connected to the EKG sensor and the Bluetooth enabled PDA or laptop. Next the team needs to check if the MobileDAQ is sending the data taken from the EKG sensor to the PDA or laptop. Finally the team needs to make sure the data is not altered during transmission.
3. Pocket PC module:
Getting the pocket PC module to work is a milestone because it is essential for being able to view the data results from the EKG sensor. The team will evaluate whether the pocket PC is correctly communicating with the MobileDAQ, whether it is receiving all the data taken from the EKG sensor, and if the data is correctly being put into easy-to-read graphs for the user to see and analyze.
4. PalmOS module:
This is another essential milestone because it is an alternative option for the user to use to view the data results rather than the pocket PC. The team will evaluate if the palmOS is communicating the MobileDAQ correctly, if it is receiving all the data taken from the EKG sensor, and if the data is being put into easy-to-read graphs correctly so the user can view and analyze them.
5. User manual:
The user manual is the team’s final milestone. The criteria to be used to evaluate this milestone will be based on completeness and readability. Does the manual contain all the necessary information to run the end product, does it contain helpful hints and/or trouble shooting sections, and finally if it is easy to read through so the average person can understand how to use it.
Project tracking procedures:
1. Budget:
This project has been lucky enough to have all the materials needed to complete the end product donated by National Instruments. The only budget constraint is the poster the team will create. The team should have no problems staying under budget, but should some unforeseen expense arise the team will contact Nation Instruments to see if the materials can be donated.
2. Requirements:
The requirements are project team must meet are listed as follows:
· Ensure the EKG sensor can take complete and accurate data
· Ensure the MobileDAQ can read in the EKG sensor’s data
· Ensure the MobileDAQ can communicate with the PDA
· Ensure the MobileDAQ can communicate with the PalmOS
· Ensure the PDA and PalmOS can receive the data