Project Evaluation: DEC 0807
Iowa State Science Center
Team Lead:
Moran, Alex
Team Members:
You, Seung Han
Koo Kang, June
Client:
Iowa State University (Thorland-Oster, Vicky)
Advisor:
Jacobson, Doug
DISCLAIMER: This document was developed as part of the requirements of an electrical and computer engineering
course at Iowa State University, Ames, Iowa. The 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. Document users shall ensure that any such use does not
violate any laws with regard to professional licensing and certification requirements. Such 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 the document and the associated
faculty advisors. No part may be reproduced without the written permission of the senior design course coordinator.
Table of Contents
1.
Figures Reference: .................................................................................................................. 4
2.
Introduction ............................................................................................................................ 5
3.
History & Initial Status ............................................................................................................ 7
4.
Planning................................................................................................................................... 8
4.1.
Functional Requirements ................................................................................................. 8
4.1.1.
4.2.
Non-Functional Requirements ......................................................................................... 9
4.2.1.
5.
Functional Requirement Not Met (FNM) Explanations ............................................ 9
Non-Functional Requirement Not Met (FNM) Explanations .................................. 10
Design.................................................................................................................................... 10
5.1.
Hardware ........................................................................................................................ 10
5.1.1.
NI USB-6008 OEM ................................................................................................... 11
5.1.2.
Sonar Sensor ........................................................................................................... 12
5.1.3.
Thermistor............................................................................................................... 15
5.1.4.
Microphone............................................................................................................. 16
5.1.5.
RFID (Radio Frequency IDentification).................................................................... 16
5.2.
Software ......................................................................................................................... 17
5.2.1.
GUI (Graphic User Interface) .................................................................................. 18
5.2.1.1.
Control ................................................................................................................. 19
5.2.1.2.
DAC Analog Signal Acquisition ............................................................................ 21
5.2.1.3.
Sound Control...................................................................................................... 22
5.2.1.4.
Manual Control ................................................................................................... 23
5.2.1.5.
PWM generation ................................................................................................. 23
5.2.2.
RFID ......................................................................................................................... 25
6.
Testing ................................................................................................................................... 31
7.
Users Manual ........................................................................................................................ 32
8.
Cost Analysis ......................................................................................................................... 32
Hardware Cost Analysis ................................................................... Error! Bookmark not defined.
9.
Appendix 1: Testing and Verification ................................................................................... 38
Testing Information ...................................................................................................................... 40
Non-Functional Test ...................................................................................................................... 41
Sonar Unit Test.............................................................................................................................. 42
Thermistor Unit Test ..................................................................................................................... 43
Microphone/Sound Unit Test ....................................................................................................... 45
LED Unit Test ................................................................................................................................. 46
NI-6008.......................................................................................................................................... 47
STC2............................................................................................................................................... 51
LabView Controller Verification .................................................................................................... 52
RFID and Information button Verification .................................................................................... 54
10.
Appendix 2: Users Manual ................................................................................................ 56
Introduction .................................................................................................................................. 58
1.
Installation ............................................................................................................................ 58
2.
Operation: ............................................................................................................................. 58
3.
RFID tag programming .......................................................................................................... 60
4.
Script Adjustment ................................................................................................................. 60
List of Acronyms:.............................................................................. Error! Bookmark not defined.
1. Figures Reference:
FIGURE 1: NI USB-6008 OEM ........................................................................................................................ 11
FIGURE 2: DAC CONNECTION DIAGRAM ............................................................................................................ 12
FIGURE 3: LV-MAXSONAR-EZ1 ........................................................................................................................ 13
FIGURE 4: SONAR DIMENSIONS......................................................................................................................... 13
FIGURE 5: SONAR CIRCUIT (COMPONENT) .......................................................................................................... 14
FIGURE 6: INA330 .......................................................................................................................................... 16
FIGURE 7: PHIDGETRFID READER ...................................................................................................................... 16
FIGURE 8: LABVIEW VI HIERARCHY .................................................................................................................... 18
FIGURE 9: LABVIEW GUI .................................................................................................................................. 19
FIGURE 10: GUI CONTROL................................................................................................................................ 19
FIGURE 11: GUI CONTROL (LABVIEW) ............................................................................................................... 20
FIGURE 12: DAC ............................................................................................................................................ 21
FIGURE 13: SIGNAL ADDITION .......................................................................................................................... 22
FIGURE 14: DAC PWM VALUE ........................................................................................................................ 22
FIGURE 15: OBTAINING A SOUND SAMPLE .......................................................................................................... 23
FIGURE 16: MANUAL CONTROL ........................................................................................................................ 23
FIGURE 17: PWM GENERATION........................................................................................................................ 24
FIGURE 18: RFID CONTROL (1) ........................................................................................................................ 26
FIGURE 19: RFID CONTROL (2) ........................................................................................................................ 27
FIGURE 20: RFID NAME REPRESENTATION ......................................................................................................... 27
FIGURE 21: RFID IMAGE ................................................................................................................................. 28
(The following sections up to the introduction are an excerpt from the original design
document. The original design document is included as a final addendum)
2. Problem Statement
Each major at Iowa State University uses a series of demonstrations in order to encourage
prospective students to choose a particular field of study in engineering. Despite being the
current leader in technological advances, the Electrical and Computer Engineering (ECpE)
program at Iowa State does not have a demonstration that shows off the knowledge and skills
of an ISU ECpE student in a fashion which would encourage students to choose ECpE as their
field of study. Student services would like to develop a demonstration that encourages people
to go into the field of Electrical and Computer Engineering. The technology surrounding people
such as cell phones, computers, and video games have become commonplace, and they have
therefore lost their potential to create excitement for entering the field of ECpE.
3. Proposed Solution
The Dec08-07 project team proposes to meet the Department’s need by developing an Iowa
State Science Center, an interactive room that will demonstrate principles of ECpE. A laboratory
will be fitted with various sensors capable of feeding back data to a computer. The lab will be
designed to be easily upgraded for future programs, and will be expected to grow in the future.
The initial build will integrate some of the initial hardware, and will be capable of a
demonstration at the end of the second semester. The following list shows the current
expected functionality, and sensors which will be implemented. Planned Devices:
Sonar Distance Sensors
Microphone
Heat Sensing Devices
LED Light Display
Monitor
Audio Out
Light interaction and Bluetooth device recognition are the current focal points of the room.
Each of these will provide interactive demonstrations of multiple areas of ECpE. A simple script
will be developed that explains the correlation between different features within the room and
how they pertain to fields of study within ECpE. With the perception that many people have
that these fields of study are boring, a demonstration that people can see, hear, and interact
with will increase the number of people who apply to and join Iowa State to study Electrical and
Computer Engineering.
4. Project Name
Many projects are given a name to create more association with the project. Officially the title
of the project is the Iowa State Science Center (ISSC). The development team has nicknamed
the project Akiko. Akiko means Bright Light, and is used to associate the project both with the
interaction of colorful lights, and the intelligence the room is capable of displaying.
5. Concept Sketch
Figure 1: Concept Sketch
Figure 1: Concept Sketch shows the proposed layout for the room. The entrance and exit of the
room will contain Radio Frequency Identification (RFID) sensors for detecting when a tour guide
enters, and leaves the room. The RFID sensor will be designed to recognize specific individuals,
and greet the tour guide appropriately. Ability to program the RFID tags will be integrated into
the computer. A sophisticated interface is not planned for this phase of the project, but such an
interface is an option for future development. Each of the 6 colored bars represents a different
LED Light bar. The proposed light bars will use high intensity LEDs that can change in intensity
based upon different factors within the room. Sonar, Thermal, and audio sensors will be the
primary sources for changing the lighting effects. Detailed Information regarding the
functionality of the lights can be found in section 12.4 LED Display. The corner of the room will
also contain a monitor. The monitor will be used to display statistics that the room will be
capable of determining. Some of the proposed information that will be implemented within the
first year will be Bluetooth device count, tour guide name and ambient temperature. The room
is not planned to be finished within one year. The ISSC will be designed to be upgraded easily,
and will gain functionality in future years. Audio output will be included in the initial system, for
welcoming tour guides, but it will not have any additional functionality for the first build.
6. Introduction
The Iowa State Science Center (ISSC) is a continuing design project designed to encourage
new students into the field of Electrical and Computer engineering. The Science Center will
be integrated into room 1318 of Coover, and is expected to be first demonstrated during
Veisha of 2009. The team which developed the initial ISSC build consisted of three Electrical
Engineers: Alex Moran (Team lead), June Koo Kang, and Seung Han Yoo.
The ISSC is, put simply, something students will find “cool and interesting”. This is
accomplished via the interaction between individuals within the room and sensors which
are placed about the room. A series of 5 different LED ropes hang above the room (Amber,
red, blue, green, and white). These different ropes can be brightened and dimmed by
means of interaction with three different sensors (Sonar, thermistor, and microphone).
Functionality of these devices will be discussed later.
Additionally, there is an RFID unit integrated into the room. The RFID unit responds with a
textual greeting, a visual response, and will play a sound file with a recording associated
with the tag. A more detailed explanation will be included later.
Finally, for individuals interested, there are a series of push buttons on the GUI. These
buttons give the individual the ability to learn about different aspects of the system, and of
particular interest to the field of Electrical and Computer Engineering (ECpE).
7. History & Initial Status
There is no baseline which the ISSC is built off of. This is a brand new endeavor for Iowa
State University. Although the goals for this semester were completed to a satisfactory
level, the project is not to be terminated. Future groups will continue developing new
additions to the ISSC, and improve existing functionality to the current ISSC.
8. Planning
The planning phase of the ISSC occurred during the spring semester of 20008. During this
phase, a project plan and design document were created (These can be viewed at
http://seniord.ece.iastate.edu/dec0807/).
The functional and non-functional requirements listed below show the requirements for the
ISSC, and the test in which the requirement is verified in. If a requirement was not met, an
explanation for why the requirement was not met, as well as any action items involved.
Numerous Re-designs were needed, so many requirements have been modified as a result.
Any functional requirement which was not met is labeled FNM-#, with a description given in
section 8.1.1. Any non-functional requirement which is not met is labeled NFNM-#, with a
description given in section
8.1.Functional Requirements
REQ #
F-REQ-1
Definition
The Sonar Array shall be capable of detecting objects from four
different stationary points.
The Sonar Array shall be capable of detecting objects between 3
and 21 feet from the sensor.
The Sonar sensors shall be capable of being interpreted by an
analog to digital converter.
The heat sensor shall be capable of operating between 0 and 100
degrees Fahrenheit.
The Heat sensor shall be capable of being interpreted by an analog
to digital converter.
Recognition distance shall be operational between 0 and 2
meters.
The RFID shall be capable of recognizing no less than 100 different
signals.
The RFID shall be capable of transmitting information via an
Ethernet connection to the main computer.
The RFID shall be capable of connection with the computer via RS232 for RFID software updates.
The RFID shall be capable of writing tags at a distance of at least 6
inches.
The LED display shall be capable of transitioning between different
Verified in test
FNM-1
FNM-2
FNM-3
FNM-4
intensity values.
The LED intensities will be individually dependant on the inputs
from the chosen input signal.
The LED display shall have independent control for each light bar.
The monitor shall be able to output RFID identification
The monitor shall be capable of displaying the current thermistor
heat value.
The monitor shall be capable of displaying the Bluetooth
information
The monitor shall be capable of being read in ambient light.
The Controller shall be capable of switching between at least 3
different devices.
FNM-5
8.1.1. Functional Requirement Not Met (FNM) Explanations
FNM1 – Software for the initial RFID was never obtained. A new RFID was utilized which is only
capable of reading RFID tags at close proximity. This change has not affected the functionality
of the system, and has resulted in no critical changes.
FNM2 – The RFID utilizes a USB connection rather than an Ethernet connection for
communication. This has resulted in no change in functionality for the system.
FNM3 – The RFID software is contained entirely within the computer. No RS-232 connection is
needed as a result. This has resulted in no change in functionality for the system.
FNM4 – The RFID utilized in the system is not capable of writing new tags. However individual
tags can be purchased with different RFID signals at a cheap cost. Additionally, the system is
designed such that old tags can be re-dedicated for use with a new individual. This has resulted
in no change in functionality for the system.
FNM5 – Due to the complexity of interfacing of Bluetooth technology, a computer engineer is
necessary to properly interface with the Bluetooth antenna. A CpE on the SPR0907 team has
developed a Bluetooth device to be implemented during next semester. This software is
expected to be implemented during the beginning of next semester, and is only a minor delay
in the Bluetooth functionality.
8.2.Non-Functional Requirements
REQ #
NFREQ- 1
NFREQ-2
NF-REQ
Definition
The ISSC shall contain 4 sonar sensors.
The Sonar sensor shall be capable of operation between 3.5 and
5.5 Volts
The ISSC shall contain 2 heat sensors.
Verified in test
The heat sensor shall be capable of outputting between 0 and 5
volts.
The ISSC shall contain 1 RFID reader.
The RFID reader shall operate at a range of 860 MHz to 906 MHz
The RFID shall utilize a built in antenna.
The RFID shall operate off of a 120V power supply
The ISSC shall contain 5 different LED color bars.
The ISSC LEDs shall not be degraded by operation at maximum
radiance.
The ISSC LEDs shall operate off of a 12 volt power supply.
The monitor shall be viewable from any point in the room
The monitor shall be color
The monitor shall be able to output RFID identification
The monitor shall be capable of displaying the current thermistor
heat value.
The monitor shall be capable of displaying the Bluetooth
information
The ISSC shall include a Bluetooth antenna.
The controller will be encased in such a way as to protect from
damage.
NFNM-1
NFNM-2
NFNM-3
NFNM-4
8.2.1. Non-Functional Requirement Not Met (FNM) Explanations
NFNM1 – The current RFID reader operates off of a 125kHz - 140kHz frequency. These tags are
cheap and readily available. This has resulted in no change in functionality for the system.
NFNM2 – The current RFID reader is powered off of the 5 volts supplied by the USB connection.
This has resulted in no change in functionality for the system.
NFNM3 – A smaller monitor is currently being utilized than originally anticipated. The SPR0809
team is attempting to acquire a larger monitor for future development. A standard computer
monitor is currently available, so functionality limitation is minimal.
9. Design
The following sections describe the design considerations and implementations used for the
ISSC. The first section is dedicated to the hardware utilized, while the second section describes
the software.
9.1.Hardware
This section describes in detail the hardware used on the system. Each section describes the
hardware, but does not describe the interface with the overall program. Functionality of the
hardware is described in the software section of the design document.
9.1.1. NI USB-6008 OEM
The NI-6008 (Figure 2: NI USB-6008 OEM) is a multipurpose tool that can read and write both
digital and analog formats. Originally, a digital to analog converter (DAC) was to be built and
utilized for the system. For this reason, the NI-6008 is referred to as DAC in all following
sections of the documentation. The NI-6608 has the following specifications:

8 analog inputs (12-bit, 10 kS/s)

2 analog outputs (12-bit, 150 S/s), 12 digital I/O; 32-bit counter

Bus-powered design for convenience; 34-pin connector for easy integration
Figure 2: NI USB-6008 OEM
Not all of the pins are being utilized on this device. The following table lists the connections
being utilized within the NI-6008. Figure 3: DAC Connection Diagram shows the connections
between devices and the NI-6008.
Table 1: NI USB-6008 Connections
Analog Inputs
Analog_In_0
Analog_In_1
Analog_In_2
Analog_In_3
Analog_In_4
Analog_In_5
Connected Device
Sonar Input 1
Sonar Input 2
Sonar input 3
Sonar Input 4
Thermistor input 1 (Heat1)
Thermistor Input 2 (Heat 2)
Digital Outputs
P0.0
P0.1
P0.2
P0.3
P0.4
Connected Device
LED Driver 1
LED Driver 2
LED Driver 3
LED Driver 4
LED Driver 5
Figure 3: DAC Connection Diagram
The analog signals all operate in the voltage range of 0 to 5 volts. Interpretation of the signals
will be discussed within the software section of the documentation.
The digital signals are a 1.8 volt square wave. There is some modulation in the frequency out of
the system, but the standard operating frequency is around 50 Hz. There have been some
issues with the PWM, however this will be discussed in the LED driver section.
9.1.2. Sonar Sensor
The ISSC utilizes four (4) LV-MaxSonar-EZ1 sonar sensors (See Figure 4: LV-MaxSonar-EZ1)
throughout the room. Each of these sonar sensors are capable of operating between 3.5 and
5.5 volts. The ISSC will operate these sensors at 5 volts. This will give the device a measurable
range of 254 inches (21.5 feet). It is recommended that the Sonar operate at closer ranges, due
to noise induced into the system at greater distances. This noise will be discussed within the
testing section of the document.
Figure 4: LV-MaxSonar-EZ1
Figure 5: Sonar Dimensions
They Sonar sensor is extremely small (see Figure 5: Sonar Dimensions), which causes both
advantages and disadvantage for the system. If desired, these sensors could be easily hidden
from view, for a greater ascetic appeal. However, the small size also makes the sensors prone
to damage. Each sensor runs about $25 (24.95), and could create a cost issue of too many are
broken. Caution has been taken to protect the mount, however the sensor cannot be entirely
enclosed.
The internal workings of the Sonar device allow a range of different signals to be analyzed,
including a serial connection, voltage drop, and PWM output (see Figure 6: Sonar Circuit
(Component)). The ISSC will be utilizing the voltage out from the sonar sensor. The voltage out
from the device is the most continuous signal given off by the device. The PWM and serial
inputs require more precise timing for reading in the measurements (these signals are given to
the computer, and stop between readings). However, once a voltage is set from a particular
reading, the signal will remain until the next cycle. Vo is the easiest signal for the ISSC to read
and interpret.
Figure 6: Sonar Circuit (Component)
The sonar sensors can be connected such that each sensor is continually sending out and
receiving a sonar pulse at 20 Hz cycles. Although this works for short cycles, it is unadvised for
continuous operation. For this reason, the sonar sensors are chained together.
The TX pin on each sonar sensor sends out a logic HI when a sonar pulse has been successfully
read. This signal is then sent to the RX of the next sonar sensor, which will send out a signal,
transmit, and the loop will continue on indefinitely. The BW pin must be held high for this
operation, and will operate off of the 2.5V supplied by the DAC.
The sonar sensors will not operate without the initial RX for the system. When the system is
started, the sonar sensors will need to be effectively “jump started”. A switch is included to
manage this operation.
The minimum distance that can be read is 6 inches, with each inch increased corresponding to
an increase of 09.8 mV per inch.
No additional hardware is necessary to read in the values from the sonar sensor.
9.1.3. Thermistor
The ISSC utilizes two thermistors. Although they are different models, they are both 10K ohm
thermistors, with identical thermal properties. The thermistors utilized for the ISSC are
industrial thermistors used in commercial duct work for temperature regulation. The
operational temperature is between -40 and 250 degrees Fahrenheit. By adjusting the RSET
resistor, the operational range can be tuned to work within a more manageable range. The
thermistor is set at 10Kohms at 72 degrees Fahrenheit.
The thermistor resistive value cannot be directly read by the DAC. To give an appropriate
voltage to the DAC, an INA330 is being utilized (See Figure 7: INA330). This driver generates a
signal between 0 and 5 volts. Rset is used as a reference to the thermistor being utilized, while
Vadjust is used to determine the center temperature. The setup that will be utilized will be
capable of accurate readings within a +/- 5 degree temperature range. This will ensure
accurate readings within the room at all times. Any reading above or below these values will
cause the system to saturate at 0 or 5 volts respectively.
Figure 7: INA330
9.1.4. Microphone
The microphone utilized is a standard one channel microphone, with a 3.5mm jack. A two
channel microphone can be used with no degradation to the system.
9.1.5. RFID (Radio Frequency IDentification)
The ISSC was originally going to use an industrial RFID reader to obtain signals. However, due
to the moving involved in Coover to the new sections of the building, the RFID software and
access codes were lost. A new, smaller RFID reader has been implemented instead. The
Phidget reader (see , although not as sophisticated as the originally intended model, has proven
to have many benefits which could have been problematic with the original RFID reader.
Figure 8: Phidget RFID Reader
The RFID reader interfaces via a standard USB connection, and the software for this reader is
controlled exclusively on the computer. This is a benefit over the original model, which
required software dependant both on the computer, and on the unit itself. Additionally, this
reader is much cheaper ($65), then the original model that was going to be used (around
$1500). Finally, the Phidget RFID is designed to work directly with LabView.
The RFID reader recognizes tags utilizing the EM4102 protocol (125-140KHz operating
frequency) within three (3) inches of the antenna. An onboard LED can be controlled via
software, as well as two digital outputs. The digital outputs are not currently being utilized.
The tags being utilized are the credit card sized tags (see Figure 8: Phidget RFID Reader). The
tags are reasonably priced ($3) and can be easily programmed into the system for tour guides,
or students who purchase and dedicate a tag. No security measures are currently in place for
ensuring non-offensive images are utilized, so it is not recommended that individual students
be given access to the system until a security protocol is devised.
9.2.Software
The following sections are used to describe the software utilized, and how functionality of the
system works internal to the computer interface. The documentation will flow from input to
output for the DAC, RFID, and pushbutton interface. Figure 9: LabView VI hierarchy shows the
software hierarchy for the system (the hierarchy wraps from level to level).
Figure 9: LabView VI hierarchy
9.2.1. GUI (Graphic User Interface)
The ISSC GUI is designed within LabView, and allows control of the various systems (See Figure
10: LabView GUI). The GUI displays the controls for device selection, Manual light control, RFID
recognition, Sonar control, Thermistor control, Sound pressure information, and information
push buttons with description bar.
Figure 10: LabView GUI
9.2.1.1. Control
The Control within the GUI selects how the system will be operating (See Figure 11: GUI
Control). The user can cycle through 5 different options for the controller. Sound selects the
Microphone for system control, Heat selects the thermistors, Sonar the Sonar sensors, Standby
gives the user manual override of the system, and Off powers down the LEDs.
Figure 11: GUI Control
The control for the system is relatively simple. Each setting on the control is given an integer
value between 0 and 4 (See Figure 12: GUI Control (LabView) for the following). The red box
highlights the controller within the code. The green box represents a conditional state (for this
example, the control is set to off). Depending on the input from the controller, the actions
executed will change. This box operates in a similar fashion to an If-else statement in
traditional programming language. When in the off state, a value of zero is sent out to the
PWM generator no matter what the other inputs read in (The PWM generator will be discussed
in a following section). Before the individual controls are discussed, signal acquisition needs to
be discussed.
Figure 12: GUI Control (LabView)
9.2.1.2. DAC Analog Signal Acquisition
The original development of the DAC for signal acquisition utilized a continuous sampling of
1000 samples at 1KHz. This signal was changed to a sine wave, which was then filtered through
a Butterworth filter, and the maximum value for the sample was found. Although this worked
in the initial development, it proved incompatible with the DAC digital out. The system was
redesigned such that it utilized 6 instances of the DAQ, in the same setup that is currently used
for determining LED intensity. This, although worked in theory, caused the system to operate
to slowly. The current solution appears to resolve the issues with controlling I/O at a
reasonable rate.
The current system utilizes only a single instance of the DAC. This DAC simultaneously takes in
all 6 analog inputs. These signals are then put through a single bus, and separated into their
separate components. The signal splitter shown below dedicates the signals contained in the
bus to the respective line. Table 2: Splitter Line Dedication shows the correlation between the
splitter line, and the appropriate signal.
Figure 13: DAC
Table 2: Splitter Line Dedication
Splitter Line
Line 1
Line 2
Line 3
Line 4
Line 5
Line 6
Signal
Sonar 1
Sonar 2
Sonar 3
Sonar 4
Thermistor 1
Thermistor 2
Both the Sonar control and the Thermistor control work in similar fashions, with exception to
the sonar control utilizes 4 inputs, and the Thermistor control utilizes 2 inputs.
The output that is sent to the PWM is a value between 0 and 10 (The reason behind this will be
discussed later with how the PWM is generated). This is accomplished through several steps.
First, the signals that obtained from the device being used are each added together. Since the
thermistor utilizes only two signals, the inputs are first scaled so that the same logic can be
utilized for both systems. Figure 14: Signal Addition shows this process in the code. The left
represents the Sonar sensors, the right represents the Thermistors.
Figure 14: Signal Addition
Once the signals have been added, the correlation to the LED is determined. The input can
range between 0 and 20. Refer to Figure 15: DAC PWM Value for the following. A center value
is decided for each of the inputs (IE, what input will result in a particular LED being at maximum
luminosity. The below example sets the center values to 6 (10-3) and four (10-4)). This value is
set above 10 so that the maximum value is not a discrete point (12.5 in the below example). If
the input to the comparator is less than 12.5 (after the addition to determine the center value),
then the input is sent to the PWM. IF the value is greater than 12.5, then the system will use
(V-(V-15)*2) to determine the value sent to the PWM. This effectively creates a ramp function
with a small plateau. The multiplier shown can be controlled by the user, and determines how
steep the ramp function will be. Negative values are acceptable as an output to the PWM
generator.
Figure 15: DAC PWM Value
9.2.1.3. Sound Control
The sound input has a different functionality than the other inputs. Figure 16: Obtaining a
Sound sample shows how a sound input is obtained. First, the number of channels is selected.
Though only one channel is currently used, a two channel device can be used, and the ability to
select two channels is included for future development. The number of samples is decided
upon, as well as the format. These controls, although available, are currently hidden below the
chart, and are there for testing and development purposes only.
The signals value ranges between 0 and 1. If a pressure value is input to the DAC output with a
value over a particular value in a given sample time, the respective LED will light up. If the
pressure detected has an average value less than the set value (0.1, .2, .3, .4, and .5) then the
light will fail to light up. IE, the louder sound received, the brighter the room will get.
Figure 16: Obtaining a Sound sample
Additionally, as well as being visible through the LEDs, the individual can see their voice
displayed on a graph on the main GUI. Future growth is expected from the sound input.
9.2.1.4. Manual Control
The manual control functionality (See Figure 17: Manual Control) allows the user to customize
the rooms color scheme to their desired preferences. This is the default mode for the system
when it starts up. The scale goes from 0 to 10, with 10 being the maximum intensity.
Figure 17: Manual Control
Error! Reference source not found. shows the logic. The value obtained from 1 to 10 is sent to
he PWM generator. Setting the control to 0 sets the LED associated to off. Increasing the value
will increase the intensity of the lights up to 10, which correlates to full power.
9.2.1.5. PWM generation
Although the functionality of the PWM changes between the sound input, manual control and
the DAC inputs, the logic is identical for all instances, and will only be discussed once.
The greatest challenge with operating this system is keeping the operating frequency above 47
Hz. Because of the speed at which LEDs turn on and off, if the system operates below this, the
LEDs will begin to blink. The system has needed to be optimized several times in order to keep
the operating frequency above 50 Hz. The problem appears to have been resolved by not only
optimizing the program, but by increasing the performance of the compute by defragmenting,
and performing several system scans and cleanups.
The DAC is not individually capable of generating a PWM. It can take one true or false
statement per cycle through the while loop, and translate that value into an output. So, the
while loop is one factor to the performance of the PWM, and also determines the number of
discrete intensities which the individual LED bar can operate off of.
Figure 18: PWM generation
Refer to Figure 18: PWM generation for the following. The DAC for the PWM out follows the
same logic as the DAC inputs. It is faster to utilize one instance with multiple channels then to
instantiate multiple instances. To do this, all of the signals are brought into a single bus which is
then sent to the PWM generator. If the value read in Is greater than the current iteration, then
the PWM will send out a true value, if not, then the generator will send out a false value. Once
the system has reached a certain number of iterations, then the loop will exit, a new value will
be obtained, and the cycle will start again.
Timing is critical for smooth operation. To ensure this, timed while loops are utilized. By
setting an appropriate period of time for each while loop, smooth and continuous operation is
ensured. Additionally, timing the system actually results in faster operation for the system
overall.
9.2.2. RFID
The RFID operates simultaneously with the LED system within LabView. The RFID logic also includes the functionality of the
information buttons.
Figure 19: RFID Control (1) and Figure 20: RFID Control (2) show the functionality of the RFID
system. The information being passed through the RFID is continually transmitted to LabView
via the green wire shown in both figures.
When a value is detected by the RFID, the comparator recognizes that a new entry must be
displayed. This sets both instances of the write function to true. Additionally, if one of the
information buttons is pressed, it will set table one to true, and table two to false. The only
difference between these two instances is that when an information button is pressed, only the
image is updated, and all other information remains the same.
Figure 19: RFID Control (1)
Figure 20: RFID Control (2)
When the two conditional statements result in TRUE TRUE, the tag ID is concatenated into
three different strings. These strings represent locations in a folder on the desktop labeled Tag
Information. The first string opens up a text file containing the name associated with the tag.
“Welcome” is concatenated to the front of the name, and is displayed. Additionally, the Tag
Number is displayed (See Figure 21: RFID Name Representation). If no name is associated with
the tag, the name will be left blank and a file containing the associated name needs to be
created. The tag number will still be displayed for identification purposes.
Figure 21: RFID Name Representation
The last string on the page is associated with a .wav file. If the individual chooses to, they can
record a greeting message which will play when their tag is identified.
The second string created opens an image associated with the tag. It is recommended to use a
picture of the individual, or something important to the individual as the image. The picture
must be 1200X1024 to be displayed properly. If the image is not the correct size, a portion of
the previous image will not be overwritten, and the two images will be displayed together.
Figure 22: RFID Image shows an example of an incorrectly sized image being displayed. This
persons picture of an ISU football game has the remainder of another person’s image of a
popular video game. The yellow box highlights the manual control, and the red box highlights
the information buttons.
Figure 22: RFID Image
In Figure 22: RFID Image there is a box labeled “Information” (Blue box). From
Figure 19: RFID Control (1), we can see that a button press from one of the Information buttons
results in a file being located and opened. This file contains text which describes interesting
technical facts about topic pressed, and how it relates to the room. Additionally, the image will
update to show technical information relevant to the topic chosen. (This is the TRUE FALSE
case, and is similar to the TRUE TRUE case, with exception to the fact that the welcome
message is not displayed, and the sound file is not played).
10.
PCB
In order to ensure that the components would be secure after installation, a Printed Circuit
Board (PCB) was created for the ISSC. The components installed on the PCB include 5 STC2 LED
drivers, 2 INA330 thermistor drivers, and a power supply for the 4 sonar sensors. The PCB has
the ability to install a total of 8 LED drivers, however only 5 will be installed in the current stage.
The remainder of the spaces are reserved for future growth of the system.
During development of the PCB, the two largest difficulties that we had to deal with were the
layout of the INA330s (there were routing issues), as well as the fact that no members of the
team previously had any experience working with laying out PCB. Extensive assistance was
required from Lee Harker for the completion of this phase of the project.
One final high risk during development was the lack of testing preformed on the INA330. Due
to its small size, no testing was able to be completed prior to the build of the PCB. A test board
was successfully completed, however, for the STC2 prior to its installation. The test board was
destroyed, however, due to reverse biasing the circuit, and damaging the component.
There are basically 3 stages necessary to create the PCB. You need a schematic, a layout, and to
compile the machine code for drilling instructions. Orchad and Orchad Layout were used to
produced each of these different stages of development. The schematic and layout can be seen
in the figures below.
Figure 23: PCB Schematic
Figure 24: PCB Layout
11.
Testing
Unit testing as well as system testing and verification were performed for the ISSC. System
testing and verification is included as an appendix to this document.
The following unit tests are completed:









Sonar
Thermistor
STC2
Microphone
NI USB-6008
RFID
LED Rope Lights
Sound Out
Information button
A System Integration test is also completed.
(See Appendix 1)
12.
Users Manual
The user’s manual is used to describe how the system operates, and how individuals interact
and operate the ISSC. This includes basic installation instructions, file management, and some
instructions relating to trouble shooting issues that were noticed during the development of
the system.
(See Appendix 2)
13.
Cost Analysis
The Following is the cost analysis for the Iowa State Science Center. This section details both
the costs expected, and costs incurred. The budget allotted for hardware was over by $162.66.
This cost was accepted by Iowa State University.
The hours worked were also over budget. This project was designed for a team of three,
however it was expected to take more time then desired due to efficiency lost by being able to
divide up the work more.
DEC0807 Cost Analysis
Created by: Alex Moran
Hardware Cost Analysis
Budget:
$150
Item
Description
Part
LED Driver
STC2
Therm. Driver
Sonar
LED (RED)
LED (Blue)
LED (White)
LED (Green)
LED (Amber)
DAC
Thermistor
INA330
Maxbotix LV-EZ1
N/A
N/A
N/A
N/A
N/A
NI USB-6008
(Unknown)
Part #
49706560-1ND
296-13861-1ND
SEN-00639
N/A
N/A
N/A
N/A
N/A
N/A
(Unknown)
Material
Cost
Total
Units
Total
Cost
($5.07)
8
($40.56)
($3.83)
($24.95)
($10.45)
($14.99)
($19.99)
($15.99)
($10.45)
$0
$0
2
4
3
2
2
2
3
1
2
($7.66)
($99.80)
($31.35)
($29.98)
($39.98)
($31.98)
($31.35)
$0.00
$0.00
TOTAL
Cost
Variance
29 ($312.66)
($162.66)
The additional cost was approved for development.
Item
DAC
LED
LED Driver
Sonar
Thermistor
Website
www.ni.com
www.cconcept.com
www.digikey.com
http://sparkfun.com/commerce/product_info.php?products_id=639
Unknown - Product donated by Ahern Heating and Plumbing
Thermistor
Driver
www.digikey.com
Work Effort Analysis
Last updated: 11/24/08
Cost based off of a $12 per hour wage. This cost is theoretical, and does not actually impact the
overall cost of design and integration
Task
Effort
Budgeted
(In Hours)
Actual
Effort
Schedule
Variance
BWCS/
BWCP
ACWP
Cost Variance
(70.00)
Total Hours Desired
Software
Development
Hardware
Development
270
340
120
120
45
114
$3,240.00
$4,080.00
($840.00)
$1,440.00
$1,440.00
$0.00
$540.00
$1,368.00
($828.00)
$840.00
$792.00
$48.00
$420.00
$480.00
($60.00)
$3,240.00
$4,080.00
($840.00)
0.00
(69.00)
4.00
Testing
70
66
(5.00)
Documentation
35
40
(70.00)
Totals
270
340
Team Member:
Total Hours Desired
Software
Development
Hardware
Development
Alex Moran
90
78
$936.00
18
$216.00
Testing
29
$348.00
Documentation
24
$288.00
149
$1,788.00
Total Hours
Team Member:
Total Hours Desired
Software
Development
Hardware
Development
Testing
Documentation
Total Hours
June Koo Kang
90
22
$264.00
48
$576.00
18
$216.00
7
$84.00
95
$1,140.00
Team Member:
Total Hours Desired
Software
Development
Hardware
Development
Testing
Documentation
Total Hours
14.
Seung Han You
90
20
$240.00
48
$576.00
19
$228.00
9
$108.00
96
$1,152.00
Project Conclusion
While this project was set out to originally be a smaller scope than other projects (due to the
small group size), there were definitely some challenges which needed to be overcome in order
to successfully complete the Iowa State Science Center, including the need to completely learn
several programs from the ground up, with no prior experience.
Despite some small bugs within the system, our group believes that the project was, overall,
successful. The only implementation which was not included is expected to be included with
the next senior design team, and should be ready for demo by its intended date at Veisha.
This project has been good experience for the future workforce. The information applied in
developing the system, from the technical aspects, to the documentation, even the teamwork,
will be beneficial in all of our future jobs, no matter where they may be.
15.
Appendix 1: Testing and Verification
Testing and System Verification
Iowa State Science Center
DEC0807
Completed by:
Alex Moran
Seung Han You
June Koo Kang
Testing Information
The following tests represent the formal testing done to verify functionality of individual
components within the system. Each component, as well as individual I/O capabilities are
tested within each of the following formal tests. Additional testing which is not listed has also
been completed during the testing phase.
The overall system test is shortened due to individual functionality already being tested within
the previous unit and software tests.
Non-Functional Test
Test Operator: Alex Moran
Purpose:
This test is to ensure that all equipment necessary for the ISSC is present for integration into
the ISSC.
Pre-Test Requirements:
Verify that the ISSC is setup and configured for full operation
Test Procedures:












1. Verify that there exist four (4) LV-MaxSonar-EZ1 sonar sensors.
2. Verify that there exist two (2) thermistors.
3. Verify that there exists (1) microphone device.
4. Verify that there exists (1) NI USB-6008.
5. Verify the ISSC PCBMain contains (2) INA330 devices, properly wired for operation.
6. Verify The ISSC PCBMain contains the ability to utilize up to 8 STCS2 LED drivers.
7. Verify the ISSC PCBMain contains at least five (5) STC2 LED drivers.
8. Verify that there exists one (1) amber colored LED rope light (12 VDC necessary to Verify color)
9. Verify that there exists one (1) red colored LED rope light (12 VDC necessary to Verify color)
10. Verify that there exists one (1) blue colored LED rope light (12 VDC necessary to Verify color)
11. Verify that there exists one (1) green colored LED rope light (12 VDC necessary to Verify color)
12. Verify that there exists one (1) white colored LED rope light (12 VDC necessary to Verify color)
This test verified completed and accurate by the tester(s) listed below:
Alex Moran
Sonar Unit Test
Test Operator: Alex Moran, Seung Han Yoo, June Koo Kang
Purpose:
This test is to ensure proper functionality of Vo from the four sonar sensors. There will be four
columns for verification. Record the values obtained at different distances within these boxes.
Record each value to within .01 volts.
Pre-Test Requirements:
Connect power to a sonar sensor, and a multimeter (or the LabView DAC) to the sensors analog
out. Use tape to mark distances on the floor, and a table to receive distances off of. Measure
values to within 0.01 volts.
Test Procedures:
1
2
3
4
.07
.08
.04
.06




1. Setup the sonar sensor such that the object to read is closer than 6 inches and
record the voltage obtained.
2. Verify the above value is 0.06 V (+/- .05 V)
3. Move the detected object out to 16 inches.
.15
.16
.15
.18
4. Record the new value.




5. Verify the above value is 0.16 V (+/- .05 V)
6. Move the detected object out to 3 feet.
.41
.30
.32
.33
7. Record the new value




8. Verify the above value is 0.36 V (+/- .05 V)
9. Move the detected object out to 10 feet.
1.22
1.27
1.13
1.21
10. Record the new value




11. Verify the above value is 1.2 V (+/- .1 V)
Note: Although the values were obtained, it did take progressively longer to obtain the value
each time.
This test verified completed and accurate by the tester(s) listed below:
Alex Moran
June Koo Kang,
Seung Han You
Thermistor Unit Test
Test Operator: Alex Moran, Seung Han Yoo, June Koo Kang
Purpose:
This test is to verify proper functionality of the two thermistors to be utilized.
Pre-Test Requirements:
Connect a multimeter to the thermistor in ambient conditions. (NOTE: Due to the limited
control over the environment, exact values are not tested in these procedures.
Test Procedures:
1
2
1. Allow the thermistor to become stable with the environment for 20 seconds (72 °F).
 
2. Verify that a resistive value around 11,000 Ohms is obtained (+/-200 Ohms).
3. Physically grab the temperature probe.
 
4. Verify the temperature resistance begins to decrease.
5. Release the temperature probe and submerge in ice.
 
6. Verify that a resistive value around 28,000 ohms is obtained (+/- 500 Ohms)
7. Remove the probe from the ice, and allow it to sit at room temperature for at least 1
minute.
 
8. Verify that a resistive value around 11,000 ohms is obtained.
This test verified completed and accurate by the tester(s) listed below:
Alex Moran
June Koo Kang,
Seung Han You
Microphone/Sound Unit Test
Test Operator: Seung Han Yoo, June Koo Kang
Purpose:
This test is to verify that the microphone to be used in the ISSC is properly functioning.
Pre-Test Requirements:
Power on the ISSC computer, and attach the microphone to the 3.5mm jack in the back.
Test Procedures
1. On the ISSC computer, click on the start button, then select the control panel.
2. Double click sounds and audio devices.
3. Select the Voice tab.
4. Select the Test Hardware… button.
5. Follow the instructions given on the screen.

6. Verify the integrated test passes.
This test verified completed and accurate by the tester(s) listed below:
June Koo Kang,
Seung Han You
LED Unit Test
Test Operator: Alex Moran, Seung Han Yoo, June Koo Kang
Purpose:
This test is to verify that the LEDs received all function (are capable of lighting up)
Pre-Test Requirements:
Power on the power supply, and set the voltage to 12 V.
Test Procedures
1. Connect the amber LED rope to the power supply.

2. Verify the rope glows amber.
230 mA
3. Record the current to the left.
4. Connect the red LED rope to the power supply.

220 mA
5. Verify the rope glows red.
6. Record the current to the left
7. Connect the blue LED rope to the power supply.

190 mA
8. Verify the rope glows blue.
9. Record the current to the left
10. Connect the green LED rope to the power supply.

11. Verify the rope glows green.
260 mA
12. Record the current to the left
13. Connect the white LED rope to the power supply.

14. Verify the rope glows white.
250 mA
15. Record the current to the left

16. Verify no currents exceed 1 ampere.
This test verified completed and accurate by the tester(s) listed below:
Alex Moran
June Koo Kang,
Seung Han You
NI-6008
Test Operator: Alex Moran
Purpose:
This test is to verify the functionality of the NI-6008. The analog out functionality is not tested
because it is not utilized.
Pre-Test Requirements:
Power on the ISSC computer, and start the ISSC TEST program.
Power on the oscilloscope and power supply. Set the power supply to 0 volts.
Test Procedures
NOTE: The following procedures have a tolerance of +/- 0.1 volt.
1. Start running the ISSC test program.
2. Connect the power supply to pins A10 and A14.

3. Verify that the test program reads 0 volts for AI0.
4. Increase the power supply voltage to 2.5 volts.

5. Verify the test program reads 2.5 volts for AI0.
6. Increase the power supply voltage to 5 volts.

7. Verify the test program reads 5 volts for AI0.
8. Decrease power to 1 volt.

9. Verify the test program reads 1 volts for AI0.
10. Connect the power supply to pins A11 and A15.

11. Verify that the test program reads 0 volts for AI1.
12. Increase the power supply voltage to 2.5 volts.

13. Verify the test program reads 2.5 volts for AI1.
14. Increase the power supply voltage to 5 volts.

15. Verify the test program reads 5 volts for AI1.
16. Decrease power to 1 volt.

17. Verify the test program reads 1 volts for AI1.
18. Connect the power supply to pins A12 and A16.

19. Verify that the test program reads 0 volts for AI2.
20. Increase the power supply voltage to 2.5 volts.

21. Verify the test program reads 2.5 volts for AI2.
22. Increase the power supply voltage to 5 volts.

23. Verify the test program reads 5 volts for AI2.
24. Decrease power to 1 volt.

25. Verify the test program reads 1 volts for AI2.
26. Connect the power supply to pins A13 and A17.

27. Verify that the test program reads 0 volts for AI3.
28. Increase the power supply voltage to 2.5 volts.

29. Verify the test program reads 2.5 volts for AI3.
30. Increase the power supply voltage to 5 volts.

31. Verify the test program reads 5 volts for AI3.
32. Decrease power to 1 volt.

33. Verify the test program reads 1 volts for AI3.
34. Connect the power supply to pins A14 and GND.

35. Verify that the test program reads 0 volts for AI4.
36. Increase the power supply voltage to 2.5 volts.

37. Verify the test program reads 2.5 volts for AI4.
38. Increase the power supply voltage to 5 volts.

39. Verify the test program reads 5 volts for AI4.
40. Decrease power to 1 volt.

41. Verify the test program reads 1 volts for AI4.
42. Connect the power supply to pins AI5 and GND.

43. Verify that the test program reads 0 volts for AI5.
44. Increase the power supply voltage to 2.5 volts.

45. Verify the test program reads 2.5 volts for AI5.
46. Increase the power supply voltage to 5 volts.

47. Verify the test program reads 5 volts for AI5.
48. Decrease power to 1 volt.

49. Verify the test program reads 1 volts for AI5.
50. Connect the power supply to pins AI6 and GND.

51. Verify that the test program reads 0 volts for AI6.
52. Increase the power supply voltage to 2.5 volts.

53. Verify the test program reads 2.5 volts for AI6.
54. Increase the power supply voltage to 5 volts.

55. Verify the test program reads 5 volts for AI6.
56. Decrease power to 1 volt.

57. Verify the test program reads 1 volts for AI6.
58. Connect the power supply to pins AI7 and GND.

59. Verify that the test program reads 0 volts for AI7.
60. Increase the power supply voltage to 2.5 volts.

61. Verify the test program reads 2.5 volts for AI7.
62. Increase the power supply voltage to 5 volts.

63. Verify the test program reads 5 volts for AI7.
64. Decrease power to 1 volt.

65. Verify the test program reads 1 volts for AI7.
66. Set the digital outs for the DAC to 01010101












67. Verify P0.0 is LO
68. Verify P0.1 is HI
69. Verify P0.2 is LO
70. Verify P0.3 is HI
71. Verify P0.4 is LO
72. Verify P0.5 is HI
73. Verify P0.6 is LO
74. Verify P0.7 is HI
75. Verify P1.0 is LO
76. Verify P1.1 is HI
77. Verify P1.2 is LO
78. Verify P1.3 is HI


79. Verify +5V is supplying 5 volts.
80. Verify +2.5V is supplying +2.5 volts
81. Set the digital outs for the DAC to 10101010












82. Verify P0.0 is HI
83. Verify P0.1 is LO
84. Verify P0.2 is HI
85. Verify P0.3 is LO
86. Verify P0.4 is HI
87. Verify P0.5 is LO
88. Verify P0.6 is HI
89. Verify P0.7 is LO
90. Verify P1.0 is HI
91. Verify P1.1 is LO
92. Verify P1.2 is HI
93. Verify P1.3 is LO
This test verified completed and accurate by the tester(s) listed below:
Alex Moran
STC2
Test Operator: Alex Moran
Purpose:
This test is to verify the functionality of the STC2
Pre-Test Requirements:
A test board needs to be constructed for the STC2 prior to testing. See PCB layout schematic
for wiring diagram.
Connect the STC2 test board to a +12V power supply, 1.8V square wave signal generator, and
any LED rope.
Test Procedures
1. Set the square wave generator to 10 Hz.

2. Verify the LED rope light is blinking at roughly 10 Hz.
3. Set the duty cycle to 80%.
4. Increase the frequency to 50 Hz.

5. Verify the LED rope light is no longer blinking.
6. Decrease the duty cycle to 50%

7. Verify the LED rope light visibly dims.
8. Decrease the duty cycle to 20%

9. Verify the LED rope light visibly dims.
10. Set the signal generators voltage to 100mV.

11. Verify the LED rope light turns off.
12. Set the signal generators voltage to 1.8V.

13. Verify the LED rope light turns back on with a low intensity.
14. Increase the duty cycle to 50%.

15. Verify the LED rope light become brighter.
16. Set the duty cycle to 80%

17. Verify the LED rope light becomes brighter.
This test verified completed and accurate by the tester(s) listed below:
Alex Moran
LabView Controller Verification
Test Operator: Alex Moran
Purpose:
This test is to verify that the controller implemented in the LabView code works as desired.
Pre-Test Requirements:



Start the ISSC Final software.
Apply a 0V to the Sonar Signal inputs and a separate voltage supply to the thermistor
inputs.
P0.0 and P0.4 need to be connected to the oscilloscope.
Test Procedures
1. Set the ISSC controller to OFF.

2. Verify the Oscilloscope shows no signal.
3. Set the ISSC controller to Standby.

4. Verify the Oscilloscope shows a PWM operating at least 50HZ.
5. Set the RED LED control to 10.

6. Verify that the oscilloscope shows one signal high, and one signal as a PWM.
7. Set the ISSC controller to Sonar.

8. Verify that one signal reads high, and one signal reads low.
9. Increase the voltage to the thermistors to 2.5 volts.

10. Verify that the oscilloscope shows no change.
11. Set the thermistor voltage to 0V.
12. Increase the Sonar voltage to 2.5 volts.

13. Verify that the oscilloscope shows a PWM for both signals.
14. Increase the sonar voltage to 5 volts.

15. Verify the oscilloscope shows a high signal, and a low signal.
16. Set the controller to heat.
17. Set the sonar sensors voltage to 0V.

18. Verify that one signal reads high, and one signal reads low.
19. Increase the voltage to the sonar sensors to 2.5 volts.

20. Verify that the oscilloscope shows no change.
21. Set the sonar sensors voltage to 0V.
22. Increase the thermistors voltage to 2.5 volts.

23. Verify that the oscilloscope shows a PWM for both signals.
24. Increase the thermistors voltage to 5 volts.

25. Verify the oscilloscope shows a high signal, and a low signal.
26. Set the ISSC controller to sound.
27. Set all voltages to 0Volts

28. Verify the oscilloscope shows both signals as low.
29. Increase voltage to the sonar sensors and thermistors to 2.5 volts.

30. Verify the oscilloscope shows both signals as low.
31. Speak into the microphone.

32. Verify at least p0.0 goes high.
This test verified completed and accurate by the tester(s) listed below:
Alex Moran
RFID and Information button Verification
Test Operator: Alex Moran, Seung Han You, June Koo Kang
Purpose:
This test is to verify that the controller implemented in the LabView code works as desired.
Pre-Test Requirements:

Start the ISSC Final software.
Test Procedures



1. Verify that the default image is present on the ISSC GUI.
2. Verify the RFID name recognition is blank on the ISSC GUI.
3. Verify no sound is coming out of the computer.
4. Hold an RFID tag up to the reader, which has no files associated with it.

5. Verify that the tag ID is shown on the GUI, and no errors occur.
6. Hold an RFID tag up to the reader, which has the necessary files associated with it.



7. Verify the sound file is played.
8. Verify the image changes to the associated tag.
9. Verify the name recognition shows the correct name associated with the tag.
10. Hold another RFID tag up to the reader with a different address.



11. Verify the sound file is played.
12. Verify the image changes to the associated tag.
13. Verify the name recognition shows the correct name associated with the tag.
14. Press the first information button.


15. Verify the text associated with the button is displayed in the information box.
16. Verify the image associated with the button is displayed.
17. Press the second information button.


18. Verify the text associated with the button is displayed in the information box.
19. Verify the image associated with the button is displayed.
20. Press the third information button.


21. Verify the text associated with the button is displayed in the information box.
22. Verify the image associated with the button is displayed.
23. Press the fourth information button.


24. Verify the text associated with the button is displayed in the information box.
25. Verify the image associated with the button is displayed.
26. Press the fifth information button.


27. Verify the text associated with the button is displayed in the information box.
28. Verify the image associated with the button is displayed.
29. Press the sixth information button.


30. Verify the text associated with the button is displayed in the information box.
31. Verify the image associated with the button is displayed.
32. Hold an RFID tag up to the reader.

33. Verify all RFID tag information is displayed.
This test verified completed and accurate by the tester(s) listed below:
Alex Moran
June Koo Kang,
Seung Han You
16.
Appendix 2: Users Manual
Iowa State Science Center Users Manual
DEC0807
Created by: Alex Moran
Introduction
This manual is dedicated to describing installation and functionality of the Iowa State Science
center. The following instructions inform you how to correctly setup your computer, so that
you can run the Iowa State Science Center.
1. Installation
1: Install LabView 8.5 or later, or the LabView Runtime engine onto the desired computer. This
can be obtained from www.NI.com.
2: Install the NI-6008 driver to the computer for LabView. This can be obtained from
www.NI.com
3: Install the PHidgetRFID driver from www.phidgets.com/downloads.php?os_id=1. The file is
labeled Phidget 21 MSI.
4: Restart the computer.
5: Plug in the NI-6008 (Refer to wiring Schematic or Project Evaluation for wiring information).
6: Drag and drop the folders Tag Information and Scripts onto the desktop.
6: Plug in the Phidget RFID reader.
7: Double click on the executable file labeled ISSC.
The ISSC is now operational on your system.
2. Operation:
The ISSC contains an easy to use Graphic User Interface (GUI). The following describes the
functionality of different functions within the GUI. The number associated with each
description shows the location of the interface within the following figure.
1
2
3
4
5
6
7
1: The CONTROLLER is used to determine which input the ISSC will interact with. The
controller can be controlled via the pushbutton on the right, or by clicking next to the desired
function on the red and yellow dragline. The controller pushbutton for scrolling up and down
does not support wraparound functionality.
2: The Standby Manual Control will control the intensity of the LEDs when the CONTROLLER is
placed into standby mode. None of the sensors are used when this setting is being used.
3: The RFID WELCOME SCREEN displays all RFID tag information. Programming tags will be
discussed later in the document.
4: The Sonar/Thermistor BW Controller is used to tune the range of values that the sensors
will be able to react with the output of the system. Choosing a higher value will result in a
more narrow beam, while a lower number results in a wider beam.
5: Pressing any of these Information Buttons will result in displaying text and an image with
information relevant to the button pressed. THE information will be displayed in field 7.
6: There is no interaction with this device. It is used to display the sound pressure information
going into the system.
7: The Information Display will display any information related to the Information Button
pressed.
3. RFID tag programming
To program a new tag:
1) Scan the tag with the ISSC program running. This will give you the tag ID. Write this ID
down.
2) Open the folder labeled Tag Information.
3) Open the folder labeled Names
4) Create a new .txt file with the same name as the tag ID
5) Save the name to be associated with this tag in the .txt file (this file can be updated at any
time to display a new name).
6) Return to the Tag Information folder
7) Open the folder labeled Images
8) Save the desired image to display (preferably a picture of the individual) with the name
being the same as that of the tag ID. The image must be 1200X1024.
9) Return to the tag information folder
10) Save a .wav file containing the desired sound file (such as “Welcome Gregory House”) to
this folder.
All necessary information is now entered for the RFID tag.
4. Script Adjustment
To modify or change an existing script image or picture, simply open up the file with the
associated name within the Scripts folder on the desktop.
To Create a new script:
1)
2)
3)
4)
Create a button on the LabView GUI, and give the appropriate name.
Move this button to the same location as the other buttons within the LabView Code.
Extend the Bit to Array icon, and attach the new button.
Create a new instance within the conditional box attached directly to the output of the “Bit
Array to number” function (Do not modify the conditional box that is attached to the
greater than zero function).
5) Determine the new bits numerical value. The value will be 2^(n-1), where n is the
connection point to the array.
6) Copy the contents of condition 1 to the new conditional statement
7) Set the numerical value to the conditional statement to the same value determined in step
5.
8) Connect the two strings to the same points they are connected in condition 1.
9) Change the names of each string to the appropriate location and name of the new text and
image that you created in the Scripts file.
You have now created a new script button.
Old buttons can be relabeled when in edit mode by simply clicking on the button and typing in
the new value.
17.
Addendum: Original Design Document