Permalink
Browse files

Lots to fix

  • Loading branch information...
VictoryIsMine committed Dec 12, 2010
1 parent 41e8e09 commit e9a888914960ed356ac071b494b4f06025ccd69c
Showing with 76 additions and 19 deletions.
  1. +6 −0 doc/paper/report.bib
  2. BIN doc/paper/report.pdf
  3. +70 −19 doc/paper/report.tex
View
@@ -1,3 +1,9 @@
+@Misc{ maxbotix:maxsonar-datasheet,
+ title = "{LV-MaxSonar-EZ1 High Performance Sonar Range Finder}",
+ publisher = "{MaxBotix Inc.}",
+ note = "\url{http://www.maxbotix.com/uploads/LV-MaxSonar-EZ1-Datasheet.pdf}",
+}
+
@Misc{ xbow:telosb-datasheet,
title = "{TelosB Datasheet}",
publisher = "{Crossbow}",
View
Binary file not shown.
View
@@ -178,8 +178,54 @@ \section{Design}\label{sec:design}
knowledge and is described below.
\subsection{Hardware}
+When choosing the hardware for our PGI system we had specific goals in mind. The system would need to be low cost, reliable, power efficient, and easily customized to meet the needs of the specific structure/lot.
-In order to monitor the status of individual parking spaces in a lot or garage we need reliable, low cost hardware
+We believe most of our potential business would come from upgrading existing parking structures versus that of new construction. This is why we believe the need for the system to be easily customized is the most important requirement for a successful adoption by the parking industry. When adding a system such as this it is typically the installation cost that are prohibitive vs the devices themselves
+
+By supporting many different sensor types and configurations for existing construction we are providing new construction many options as well.
+
+\subsubsection{Parking Space Monitors}
+
+The Parking Space Monitors need to be able to do more than just determine if a vehicle is present in a parking space. They need to be able to run on a set of batteries for an extended period of time, support multiple sensor types and interfaces, wireless transmit relevant data to a base-station. For all these reasons we chose the TelosB wireless sensor module as the base to our Parking Space Monitors. The TelosBs provide a multitude of features and sensor and still manages to support.
+
+\begin{figure}
+ \begin{center}
+ \includegraphics[width=\columnwidth]{figures/telosb}
+ \end{center}
+ \caption{TelosB.}
+ \label{fig:telosb}
+\end{figure}
+
+The TelosB is an ultra low power IEEE 802.15.4 compliant wireless sensor module. More about the TelosB.
+
+By choosing the TelosB we have many different options to attach sensors with
+The parking space monitors are the
+
+There are many different types of sensors that we could have been used to monitor if a parking space is occupied or vacant. These include infrared range finders, magnetic
+
+We chose to use ultra sonic
+
+\begin{figure}
+ \begin{center}
+ \includegraphics[width=\columnwidth]{figures/range_finder}
+ \end{center}
+ \caption{LV-MaxSonar-EZ1.}
+ \label{fig:range_finder}
+\end{figure}
+
+To actual
+
+LV-MaxSonar-EZ1 - Ultrasonic Rangefinder
+Supply voltage 2.5V to 5.5V
+Detects objects from 6 inches out to 254 inches with 1 inch resolution (0-6 inches range as 6 inches)
+Output formats include pulse width, analog voltage, and serial digital
+
+\subsubsection{Base-Station}
+Following with our theme of low cost we tried to keep the requirements of the base-station to a minimum as well. The base-station will support multiple
+
+The base-station has two key roles. First
+
+In order to reliably and cost effectively monitor the status of individual parking spaces in a lot or garage we need reliable, low cost hardware
The TelosB mote was chosen to monitor
@@ -197,26 +243,27 @@ \subsection{Hardware}
\subsection{Collection Software}
-Yup we had software.
+\subsubsection{Parking Space Monitors}
+
+The Parking Space Monitors are powered by TinyOS. We chose TinyOS because it fully supports the TelosB and provides many features that rapidly speed-up development and
+
+One of out key design goals was wireless reliability. We need to ensure that packets containing sensor details always make it back to the base-station for processing. This can be very difficult in dynamic environment such as a parking structure.
-A paragraph or two about TinyOS and building whatever we used there
-(interfaces, interaction with other sensors and base
-station, CTP)~\cite{tep119:collection}.
-A paragraph about the base station software and what it does.
+CTP stuff~\cite{tep119:collection}.
+
+\subsubsection{Base-Station}
+
+The base-station has multiple function. It is responsible for configuring the Parking Space Monitors, ensuring the Parking Space Monitors are
+
+The base station collects sensor reading from the parking space monitors and determines what data is import
+
+Collects sensor data.
+
+Determines what data is important
+
+Since the base-station has a TelosB.
-% from proposal
-The major components of this project are building and developing the
-sensing devices, writing and testing the networking and communications
-software to handle data delivery, and creating a friendly front end to
-present and track the information as needed.
-If we discover any of these components are significantly easier than
-others, it is easy to combine forces to develop new/better methods for any
-of them.
-We also have an interest in discovering more specific information of
-existing systems and getting up-to-date in the area of intelligent
-transportation systems.
-% end from proposal
\subsection{Aggregation Software}
@@ -390,7 +437,11 @@ \section{Experiment}\label{sec:experiment}
\subsection{Sensing and Sending}
-Discussion of how sensing and sending was tested
+Sensing and sending from the Parking Space Monitors to the base-station to the
+
+Testing of the sensing and sending was extensive.
+
+Voltage rangefinder
\subsection{Backend and Frontend}

0 comments on commit e9a8889

Please sign in to comment.