Don’t Forget Me - Lab 4
Lab 4 – Don’t Forget Me: User Manual
Don’t Forget Me Development Team
CS411
Janet Brunelle
April 23, 2008
Table of Contents
13
Don’t Forget Me - Lab 4
1 Introduction (David) 1
2 Product Overview (David) 1
3 Product Features (Daniel) 2
3.1 DFM Virtual Instrument (VI) GUI 4
3.2 Motion Sensor 5
4 Getting Started (David) 8
4.1 Hardware 8
4.2 Software 9
5 Prototype Procedures (Hernan) 9
4.1 Initialization Procedure 10
4.2 Activation Procedure 13
4.3 The Running State 14
4.4 Termination Procedure 17
6 Error Messages (Brandon) 19
6.1 Errors by message 20
6.2 Errors by action number 21
7 Troubleshooting (Brandon) 22
8 References 24
13
Don’t Forget Me - Lab 4
List of Figures
13
Don’t Forget Me - Lab 4
Figure 1. DFM system prototype major functional component diagram 2
Figure 2. The DFM system VI simulated signal 9
Figure 3. The DFM system VI real sensor signal 9
Figure 4. The DFM system VI no signal 10
Figure 5. The DFM system VI force on signal 10
Figure 6. LabView run button 11
Figure 7. DFM system Danger Level indicator 11
Figure 8. The DFM system VI microphone graph example 12
Figure 9. The DFM system VI life detection sensors light indicators 12
Figure 10. The DFM system VI temperature sensor and key fob 13
Figure 11. The DFM system VI preempt switch 13
Figure 12. LabView pause button 13
Figure 13. LabView stop button 14
Figure 14. The DFM system VI reset button (light on). 14
List of Tables
13
Don’t Forget Me - Lab 4
Table 1. Error Messages 15
13
Don’t Forget Me - Lab 4
1 Introduction (David)
Welcome to the Don’t Forget Me system (DFM System) prototype. We thank you for your support in the prototype possess. This document includes an overview of the DFM system and the functional systems therein. It also includes information on how to use the prototype, what testing should be done, and troubleshooting information. Again we thank you for your interest in the DFM system prototype.
2 Product Overview (David)
The DFM system is a life saving tool utilizing sensor technology designed to prevent an occupant from being left behind in a vehicle. The system will be implemented into vehicles at the time of their manufacture. It will most likely be powered off the internal car battery, but this will be left up to the manufacturer. In a vehicle installed with a DFM system, it will be active at any time the car is parked, including when the car itself is off. Utilizing hardware sensors such as a pressure sensor, a motion sensor, and a heartbeat sensor, the software algorithm will calculate the probability of an occupant being in the seat. It will also calculate how far the driver is from the vehicle by measuring the signal strength of a transmitter on the vehicle key (Ballentine, David 2008).
When the DFM system concludes that there is an occupant in the seat, and if the driver is more than twenty feet away from the vehicle, the vehicle’s alarm will sound. There is the option to temporarily disable the alarm. A switch on the occupant’s seat will turn off the alarm. The driver or a child old enough can activate this switch. The deactivation of the switch will cause the system to enter standby mode. It will continue to monitor the occupant, as well as the conditions inside the car. If the conditions become too hostile, the alarm will sound again. This time it will not be possible to turn the alarm off without the occupant being removed from the vehicle (Ballentine, David 2008).
3 Getting Started (David)
This section discusses the steps to get started in running the DFM system prototype. The main steps are broken down into two categories. The first category is the hardware aspect and what must be done with the hardware to get the prototype set up. The second category is the software aspect.
3.1 Hardware
Before the prototype can be run, certain hardware dependencies must be correctly assembled. The main hardware is the sensors used within the prototype. As the sensors can also be simulated, the connection of the actual hardware sensors is optional, but required if you want to check the hardware functionality of that particular sensor. The DAQ must also be connected to the compliant computer correctly. The following steps must be taken.
Step 1: Ensure the computer used is in proper working order.
Step 2: Connect the motion sensor to the DAQ.
Step 3: Connect the temperature sensor to the DAQ.
Step 4: Connect the pulse sensor to the DAQ.
Step 5: Connect the RF receiver to the DAQ.
Step 8: Connect the microphone to the computer
Step 9: Connect the DAQ to the computer via USB.
3.2 Software
After the hardware is correctly installed, the software must be initiated. The DFM Prototype runs inside LabVIEW. The following steps must be taken.
Step 1: Correctly install LabVIEW onto the computer.
Step 2: Update the computer with the DAQ drivers.
Step 3: Ensure the prototype file DFM.vi is on the computer.
Step 4: Run LabVIEW and open the prototype VI file.
Step 5: Ensure all the sensor VI’s are correctly loaded.
Step 6: Ensure the CarHorn.wav file is available in the prototype directory.
Step 7: Ensure the CarHorn.wav file is correctly linked in the prototype.
Step 8: Ensure there are log files for every sensor created.
Step 9: Ensure the sensor log files are correctly referenced in the prototype.
4 Prototype Procedures (Hernan)
This section demonstrates the procedure of how to operate the DFM system prototype GUI. The procedure is divided into four different parts: initialization procedure, activation procedure, the running state, and termination procedure of the DFM system VI. The following are procedures of how to operate the GUI.
4.1 Initialization Procedure
1. To select a simulated sensor, select the radio button that says, “Simulated”. The VI will generate random numbers meant to match the actual hardware. Figure X shows a panel where simulated signal has been selected.
Figure X. The DFM system VI simulated signal
2. To select a real sensor, select the radio button that says, “Real”. The VI will use the data is generated from the actual hardware device. Figure X shows a panel where the real signal has been selected.
Figure X. The DFM system VI real sensor signal
3. To force a sensor to indicate that life is detected, select the radio button that says, “Force On”. It will set the sensor data value to 100, which is high enough to make all the sensors life detection value positive. Figure X shows a panel where force on has been selected.
Figure X. The DFM system VI force on signal
4. To turn off a sensor, select the radio button that says, “Force Off”. It will set the sensor data value to zero. Figure X shows no signal has been chosen.
Figure X. The DFM system VI force off signal
5. To disable a sensor, select the radio button that says, “Disable”. The VI will not produce any signals to the sensor. Figure X shows no signal has been chosen.
Figure X. The DFM system VI disable signal
4.2 Activation Procedure
1. Click the “Run” button on the toolbar.
Figure X. LabView run button
2. The program will continue running until the danger level reaches a value greater than five. The alarm will then activate and the alarm light will turn on. Figure X shows an example where the danger level is greater than five.
Figure X. DFM system Danger Level indicator
3. To restart the system, select the “Reset” button. Make sure that the reset light is off, which means reset has been done or there is no need to reset the system, before running the VI again. Figure X shows that reset light is off, which indicate that the VI is ready to run again.
Figure X. The DFM system VI reset button (light off).
4.3 The Running State
1. To view each sensor’s data in the form of a graph, click the tab on the graph display. Figure X shows an example of the simulated microphone data graph.
Figure X. The DFM system VI microphone graph example
2. All sensors and the key fob can be switched to the simulated, real, off, or force on state from their current state while the VI is running.
3. A life detection sensor light indicator is turned on when a sensor has detected life; otherwise, the light is off. Figure X shows an example where microphone and C02 sensors have detected life; however, the pulse, motion, and pressure sensors have not detected life.
Figure X. The DFM system VI life detection sensors light indicators
4. The temperature sensor light indicator turns on when temperature is above 89 °F; however, the key fob light indicator is turned on when the key fob reading is above one. If the temperature sensor and the key fob are both simulated or real, then either one of them that goes beyond the predefined limit first will activate the alarm, of course unless the danger level is 5 or below. Figure X shows an example of both sensors that are simulated and neither is activated. The system will only activate the alarm if the danger level is above five and either is on.
Figure X. The DFM system VI temperature sensor and key fob
5. To ignore the key fob reading, turn on “Preempt” switch.
Figure X. The DFM system VI preempt switch
6. To pause the VI, click the “Pause” button on the toolbar.
Figure X. LabView pause button
4.4 Termination Procedure
To terminate the running VI, click the “Stop” button on the toolbar.
Figure X. LabView stop button
1. Normally after termination, the reset light remains on. The reset light turns on to remind the user that the system must be reset before running again, so make sure to reset the system every time the reset light remains on. Just click the reset button to reset the alarm setting. Once the reset button is selected, the light will turn off. Figure X shows that the system needs to be reset before running again.
Figure X. The DFM system VI reset button (light on).
5 Product Features (Daniel)
You will find descriptions of the major components of the Don’t Forget Me (DFM) system prototype in this section. The individual components make up the major functional component diagram for the DFM system. The listed components include: DFM interface, motion sensor, pulse oximeter, CO2 sensor, temperature sensor, microphone, pressure sensor, and blue tooth transmitter and receiver. The Major Functional Component Diagram (MFCD) for the DFM system can be seen in figure 1. The environment sensor utilized in the DFM system can be seen in figure 2. A thermistor senses the temperature within the compartment of the vehicle. The life detection sensors consist of CO2 sensor, pressure sensor, microphone, motion sensor, and pulse oximeter. The sensors can be seen in figure 3.
Figure 1. DFM system prototype major functional component diagram
Figure 2-Environmental sensor for the DFM system
Figure 3-Occupancy detection sensors for the DFM system
5.1 DFM Virtual Instrument (VI) GUI
The DFM GUI is an interface used for the purpose of demonstrating and testing the DFM system. It has the capability of turning on the components individually. It also includes graphical components for interpreting the outputs for each sensor.
1.1. Turn on each component individually: This feature allows the user to turn on or off any of the sensors and the key fob. There is a panel for each component giving the capability of simulating the component, turning on the real component, turning off the component, and force the component on. For the simulated sensor, a set of random data points between a predefined range will be generated to provide a simulated sensor.
1.2. Capable of preempting system: This feature allows the end user to preempt the DFM system to prevent the alarm from going off. This feature is overridden when the temperature is in a safe state. There will be instances when someone will leave the vehicle, leaving an occupant behind in the vehicle. One example of this is when the driver wants to pump gas in the car.
1.3. Reset feature: This feature allows the end user to reset the DFM system. The reset button when turned on will reinitialize the DFM system. If an occupant and/or unsafe conditions are detected, the alarm will sound until the system is reset.
1.4. Numeric Display: Numeric data fields are given for each component to provide accurate readings in order determine the actual value returned from the sensor. All numeric fields are read only. Every component has a numeric field display including a numeric field for the displaying the danger level. All signal values have a precision of three decimal places.
1.5. Light Emitting Diode (LED) Display: LED components are utilized in the DFM interface to provide a visual of when the occupancy sensors: detect an occupant; key fob is not detected; and when unsafe conditions are detected. There will also be LEDs provided to show when the system and/or alarm is on.
1.6. Amplitude vs. Time Graph: A graphical chart provides a visual display of data that otherwise would be presented in a text. A chart conveys ideas about the data that would not be readily apparent if they were displayed as text. Charts are provided for the microphone, CO2 sensor, motion sensor, pressure sensor, key fob, and temperature sensor. Each chart can be selected by selecting the indicated tab. Each chart is plotted by amplitude vs. time.
5.2 Motion Sensor
The motion sensor utilized in the prototype features an ultrasonic motion sensor included in an ultrasonic movement detector kit. The kit is assembled and soldered together. The circuit uses a matched pair of 40 kHz transducer elements to detect movement up to 22 feet away. An LED is included for movement indication. Sensitivity is adjustable via control. To provide maximum stability, a Crystal locked circuit is used. The motion detector will be utilized to indicate if a movement of one inch or more has been detected which indicates occupancy.