University of Arkansas – CSCE Department
Capstone I– Final Proposal– Fall 2014
SafeTexter
Kenney Lewis, Donovan Hicks, Michael Dowdy, Danny Thepvongsa
Abstract (Michael Dowdy)
In a time where approximately 90% of adults have and use cell phones, it's not surprising
unfortunately, that there are around 1.3 million automobile accidents that involve drivers using
cell phones and texting. A quarter of teens will respond to a text once or more every time that
they drive. This is a seriously problem going forward as vehicle aren’t going away and the use of
cell phones are just increasing as they do more everyday tasks. Take away the phones and you
have no accidents caused by phones. Obviously this isn't a realistic goal but it is possible to limit
the use of phones in the vehicle which would make accidents due to cell phones drop
significantly. This is the goal.
The way to limit phone usage would be to get access to the driver’s phone and run a
program that would limit the incoming and outgoing texts as well as limiting the application
usage that could possibly distract the eyes of the driver from the road. The best way to access
that phone would be through a Bluetooth module that is implemented inside of the vehicle that
would tell an application in the phone that it is time to limit the usage once the driver is in the
vehicle. If we are able to successfully complete this then the impact could be literally life
changing for many people. The hope is that we are able to allow parents to ensure that their
children can be safe on the road as well as allowing every person to not be tempted to take their
life in their hands by texting and using their phone while driving.
Problem (Donovan Hicks)
In this day and age, technology plays a very integral part in our daily lives. From the time
you wake up in the morning, to the time you go to bed at night, there is a nearly infinite source of
information, communication, or entertainment available to you (usually at your very fingertips)!
At the forefront of this vast archive is the cell phone, which nowadays acts as a gateway which
connects you to the rest of the world. However, there are negatives to having such easy access…
One of the biggest issues that has arisen along with the prevalence of the cell phone is the
unsafe practice of texting while driving. Having your attention frequently focused on a mobile
device while on the road has proven to be a recipe for disaster, heartbreak, and tragedy. In 2011,
23% of all auto collisions involved cell phones, which is equivalent to roughly 1.3 million
collisions (OnlineSchools). Studies have shown that you are 6 times more likely to cause an
accident when you’re texting while driving as opposed to driving while intoxicated. Not
surprisingly, texting while driving has now surpassed drinking and driving as the leading cause
of death among teenagers (TRW).
If left unchecked, these bleak statistics will only continue to worsen. We live in a bitter
reality where parents across the country have to bury their children over something as
inconsequential as a text, and that is simply unacceptable.
Objective (Michael Dowdy)
To make driving safer by limiting the use of the cell phone of the driver.
Facilities (Danny Thepvongsa)
One of the most issues in safety is in transportation facilities. Transportation by vehicle is
the most common way to travel. This innovation is designed to help prevent the dangers on the
road, specifically with texting while driving. This will allow parents the comfort of allowing
their teenage children to be behind the wheel. The system is designed to be installed into the
vehicle while still maintaining the factory warranty. This will serve the future of driving,
allowing more safety on the road and less accidents.
Related Work (Michael Dowdy)
Due to the severity of the issue we are trying to prevent, there is a large number of groups
working to solve this problem. Only one group is going about solving this the same way that we
hope to, by using hardware inside the vehicle to communicate with the mobile phone. This
group, TextBuster[1], is leaving the driver in charge of actually preventing the use of phone
where we feel like the parent should be able to actually monitor and control when their child is
able to use the phone along with what applications they can use. There are other companies such
as Esure[2], AT&T[3], and DrivePower[4] who have created applications that shut down
distracting phone apps for drivers but these all require the phone to calculate the speed to check
if they are driving. The problem with these is that they would also be triggered if you are a
passenger in any vehicle moving faster than 10-25 mph regardless of if you are a driver or not.
Also in slow moving traffic or traffic jams these would also turn off, leaving the driver to
potentially become distracted by their phone in one the worst places possible. So all-in-all there
are other companies doing similar things but we believe they have not maximized the safety
possibilities yet.
[1] – TextBuster – www.textbuster.com
179$ for the hardware to install into your vehicle
[2] – DriveOFF http://www.esure.com/media_centre/archive/mobile_devices_more_of_a_distraction.html
[3] – DriveMode - http://www.att.com/gen/press-room?pid=23185
[4] – DriveScribe - http://drivescribe.com/
Approach (Kenney Lewis)
To create our system, we will be using an FPGA to control the starting of the vehicle.
Additionally, an application will be downloaded to the user’s android device that would allow
interaction with the FPGA. This FPGA will be used to capture Bluetooth signal from the android
device; the Bluetooth ID of this device would be on record within the FPGA. Upon connection, a
relay in circuit with the vehicle’s ignition will be powered, allowing the vehicle to start.
Additionally, the application will prevent the user from using texting or social media when the
Bluetooth is connected. In the event of unusual circumstances (user does not have phone, another
person is driving the vehicle, etc.), a keypad will be implemented. This could be used as an
alternative to the Bluetooth signal to power the relay via the FPGA. The user would be able to
enter a password (presumably known by the parents) to bypass Bluetooth and enable the starting
of the vehicle without the use of the application. If, at any time during the drive, the user’s phone
should become disconnected, a safeguard will be implemented to deal with this situation. The
user will be given some warning (audio cue, led, etc.) that will start a timer of 15 minutes or so
(time still not decided). If the user does now start the vehicle or reconnect their phone before the
timer runs out, the fuel pump will be disconnected and the vehicle will come to a stop as if
running out of gas.
[High Level / Detailed] Architecture (Danny Thepvongsa)
The design will involve a Module with the use of an FPGA, Bluetooth add-on
component, keypad add-on component, and a few relays to implement the hardware side of the
project. On the software side, we will design the application using Androids ADT with JAVA.
HARDWARE SIDE
This image signifies the generic location of the module and the keypad install location.
The module will need to be able to access the ignition for power and the starter wire. For the fuel
pump wire the location can be found either around the ignition, fuse box, or at the fuel pump
location. The keypad will need to be installed in a location that is not visible but still be easy to
access, like the glove box, center console or any other location depending on the vehicle.
The image below is the relay system that will be implement with the FPGA to control the
vehicle’s starting system. The way this relay system is set up, the starter wire is always
connected until the ignition is turned on and will reconnect when a trigger from the FPGA is
sent. This is implemented by using 2 Single Pole Double Throw (SPDT) relays. Relay 2 is
connected to the starter wire by splitting the starter wire in half and connecting it to the normally
closed portion of the relay. The key side of the starter wire will be connected to the common pin
30, and the 87a normally closed pin is connected to the starter side of the wire. Pin 86 and 85 are
part of the coil which, when energize will create and open circuit of the starter wire. Pin 85 will
be connected to the ignition of the vehicle, so whenever the ignition is on the coil will be
energized and the starter wire will disconnect preventing the vehicle to start. Pin 86 is connected
to the normally closed pin 87a of relay 1. Relay 2 will always be connected to ground until the
coil in relay 1 is energize. The purpose for relay 1, is to allow a signal from the FPGA to
energize the coil of relay 1 which will disconnect relay 2 from ground allowing the starter wire
to be reconnected. The design of the relay also allows the ease of dealing with issues if the
module were to ever fail. The connection between the 2 relays can be disconnected allowing the
vehicle to operate normally.
The next image is a schematic of a 2012 Honda Civics’ starter system. Here the module
is installed between the ignition and the fuse box. The green wires are the same green wires in
the above picture. The reason for this location is in case of the module ever back feeding the fuse
box will protect the circuits in the vehicle.
This same method can be used for the fuel pump implementation. Example of the fuel pump
implementation.
SOFTWARE SIDE
The application on the mobile phone will consist of 2 connections, the parents and the
teenager. In the parent’s side, the parents will be able to access the configuration of the module.
The will be able to change the code of the keypad and turn off the system all together. On the
teenager side, the application is hidden and ran on the background of the phone. Whenever the
application is paired with the module inside the vehicle then the application will lock the user
from being able to use the text messaging and social media features of the vehicle.
Hardware Components
Tasks (Kenney Lewis)
1. Understand how a vehicle’s operation can be manipulated through an FPGA, and get a
background on the android app development process.
2. Configure the FPGA and android app to interact with each other and the vehicle through
bluetooth and relay circuitry.
3. Test that the vehicle starts at the appropriate time and that the app correctly blocks access
to specified functionalities of the user’s phone.
4. Demonstrate that the vehicle will start only when the app is connected and blocking
access to social media/texting.
5. Document the progress and degree of success of the project.
Tentative Schedule (Danny Thepvongsa)
Fall
Spring
1. Understanding
2. Design
3. Implement
4. Test
5. Demonstrate
6. Document
Deliverables (Kenney Lewis)
•
•
•
•
•
Source code for android app
VHDL code for FPGA programming
Circuit diagram for ignition relay system
Simplified schematic diagram for entire system
Final report
Key Personnel (Michael Dowdy)
Danny Thepvongsa – Thepvongsa is a senior Computer Engineering major in the
Computer Science and Computer Engineering Department at the University of Arkansas. He has
completed Embedded Systems, System on a Chip, and Computer Architecture. This student is
primarily responsible for the hardware side of the project. Including dealing with any
connections between any vehicle part and the computer hardware.
Kenneth Lewis – Lewis is a senior Computer Engineering major in the Computer
Science and Computer Engineering Department at the University of Arkansas. He has completed
Embedded Systems, System on a Chip, Circuits and Electronics, and Programming Paradigms.
This student is responsible for working on the software side of the project with Michael.
Michael Dowdy – Dowdy is a senior Computer Science major in the Computer Science
and Computer Engineering Department at the University of Arkansas. He has completed
Database Management, Information Retrieval, and Mobile Programming. This student is
primarily responsible for the software side of the project which includes creating and
maintaining the android application that will communicate with the Bluetooth device and carry
out the necessary restrictions to the phone that is required for the project.
Donovan Hicks - Hicks is a senior Computer Engineering major in the Computer
Science and Computer Engineering Department at the University of Arkansas. He has completed
System on a Chip and Embedded Systems. This student is primarily responsible for the hardware
side of the project. He will assist Danny wherever needed.
Use Cases (Authors Indicated)
Use Case 1
Use Case:
During driving
Author:
Danny Thepvongsa
Primary Actor:
Driver
Goal in context:
device
Prevent the user from driving when the phone is disconnected from the
Preconditions:
downloaded on the
Driver has the device installed in the vehicle and the application
device and is paired with the Bluetooth device.
Trigger:
vehicle is in
The cellphone becomes disconnected from the Bluetooth device while the
motion
Scenario:
•
•
•
•
•
Driver: While driving decides to turn off the Bluetooth on the cellphone.
FPGA component: detects the disconnection and detects the vehicle is in motion.
FPGA component: triggers a warning to the driving allowing them 15 minutes to
re-connect the Bluetooth Devices.
FPGA component: after 15 minutes without a connection, the fuel pump will be
disconnected.
Vehicle: will slow down, imitating a vehicle that is running out of fuel.
Exceptions:
•
•
The parent has turned off the devices.
The driver knows the keypad code and bypasses the devices
Priority:
Medium
Channel to Actor:
Speaker
Usage Frequency:
During motion of vehicle
Secondary Actors:
FPGA, Relays, Fuel Pump
Use Case 2
Use Case:
Starting the vehicle normally
Author:
Kenney Lewis
Primary Actor:
User
Preconditions:
User has the device installed in his/her vehicle and the app downloaded on
his/her android device.
Trigger:
The user wants to operate his/her vehicle.
Scenario:
•
•
•
•
User: enters his/her vehicle and activates the android app on his/her phone.
App: blocks access to social media and texting and sends Bluetooth signal to the
FPGA
FPGA: receives signal from android device
FPGA: sends signal to the relay circuitry start the vehicle.
Priority: High
Channel between Actors: Android App GUI
Usage Frequency: Daily; every time the system is used
Secondary Actors: FPGA, App (on Android Device), Relay Circuitry
Channels to Secondary Actors: Bluetooth between app and FPGA, electrical signals between
FPGA and circuitry
Use Case 3
References
•
•
•
OnlineSchools. Texting and Distracted Driving Infographic. 2014.
<http://www.textinganddrivingsafety.com/texting-and-driving-stats/>.
TRW. Texting While Driving Now Leading Cause of US Teen Deaths. 2014.
<http://safety.trw.com/texting-while-driving-now-leading-cause-of-us-teendeaths/0710/>.
Cell phone facts from pewinternet.org
•
•
•
•
TextBuster – www.textbuster.com 179$ for the hardware to install into your
vehicle
DriveOFF http://www.esure.com/media_centre/archive/mobile_devices_more_of_a_distracti
on.html
DriveMode - http://www.att.com/gen/press-room?pid=23185
DriveScribe - http://drivescribe.com/