summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-09 18:52:04 +0200
committerRefik Hadzialic2011-10-09 18:52:04 +0200
commit5c3c664882a3cd5112e45768075f8d92318ffeea (patch)
tree6b41ba73da0633a02c055c8c48bd2e0925710c96 /notFinishedCode/Report/test.tex
parentAdded changes to the report! (diff)
downloadgsm-selftest-5c3c664882a3cd5112e45768075f8d92318ffeea.tar.gz
gsm-selftest-5c3c664882a3cd5112e45768075f8d92318ffeea.tar.xz
gsm-selftest-5c3c664882a3cd5112e45768075f8d92318ffeea.zip
Writing report :(
Diffstat (limited to 'notFinishedCode/Report/test.tex')
-rw-r--r--notFinishedCode/Report/test.tex40
1 files changed, 31 insertions, 9 deletions
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index d0e70d9..af12352 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -102,27 +102,46 @@ Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Mei
Before we had started working on our project, we had to analyze the overall network to come up with test cases that contain the highest information content. The next step in our procedure was to implement our ideas into a working piece of software.
Gradually we implemented a bit-by-bit of the final software. Every single step was accompanied by testing and validation procedures. At the end we connected all the ``black-boxes'' into one big piece of software. We have fulfilled our requests and goals and made a fully working and operable test software. Despite developing a working software, all the way along we thought about the simplicity of the usage of the software. In the following chapters we will describe in more detail our approach and how each subsystem works.
\newpage
-\section{Requests} % chapter 2
+\section{Requirements} % chapter 2
\newpage
\section{Database design}
+How we designed our database and why, explain in this section!
\newpage
\section{Software design} % section 2.1
-\subsection{Usage} % subsection 2.1.1
+\subsection{Database access} % subsection 2.1.1
+\subsection{Controlling the cell phones}
+Our first version of the developed program code for controlling the cell phones used predefined timed values
+to send commands instead of using a state controlled approach to confirm that every command was successfuly received and executed by the cell phone.
+It meant we had to make an enormous number of assumptions. In comparison to our second approach, to build a state controlled cell phone control class,
+our first approach was inferior and slower. The state controlled method connected two cell phones, on the same base station, up to 15 times faster than timed approach.
+\subsection{}
\newpage
\section{Hardware design}
In our team project we had the option to choose all the required hardware ourself beside the two BeagleBoards, which we were luckily supplied by Konrad and Dennis.
-Since one of the project goals was to reduce the costs as much as it was possible, we had tried to use some of the leftovers in our lab.
-
+Since one of the project goals was to reduce the costs as much as it was possible, we had tried to use some of the leftovers found in our lab.
+
+\subsection{BeagleBoard}
+``The BeagleBoard is an OMAP3530 platform designed specifically to address the Open
+Source Community. It has been equipped with a minimum set of features to allow the
+user to experience the power of the OMAP3530 and is not intended as a full development
+platform as many of the features and interfaces supplied by the OMAP3530 are not
+accessible from the BeagleBoard'' \cite{beagleDataSheet}.
\begin{figure}[ht!]
\centering
\includegraphics[width=130mm]{bb.jpg}
\caption[]{BeagleBoard, a linux-on-chip board where our controller software runs the GSM device }
\end{figure}
-\par Our first attempt was to control a Nokia cell phone 3310 with the supplied USB connection cable.
-Protocols used by old versions of Nokia phones as the 3310 use the F-Bus protocol. It was not easy to work with.
-After performing various experiments we found out that it was not possible to
-send commands for controlling the calls. In the meantime we found two Siemens phones, one M45 and S55.
-The first one, Siemens M45, had a cable supplied with it and it was not difficult to control it with AT commands.
+
+\subsection{Cell phones}
+Our first attempt was to control a Nokia cell phone 3310 with the supplied USB connection cable.
+The protocols used by old versions of Nokia cell phones, as the 3310, use the F-Bus protocol. It was not easy to work with.
+After performing various experiments we succeeded to send and to read SMS messages. Later on we found out that it was not possible to
+send commands for receiving and making the calls. In the meantime we found two Siemens phones, one M45 and S55.
+The first one, Siemens M45, had a cable supplied with it and it was not difficult to control it with the standard set of AT modem commands.
+At the start we did not have a cable supplied for the Siemens S55 phone. We controlled it over the Bluetooth port.
+
+\subsection{Cables for the cell phones}
+
\newpage
\section{Communication protocol}
@@ -391,6 +410,9 @@ Hypothesis}, preprint (2003), available at
\bibitem{pChart} \emph{pChart}, accessed on 15.08.2011, available at
\url{http://http://www.pchart.net/}.
+\bibitem{beagleDataSheet} \emph{BeagleBoard System Reference Manual}, accessed on 20.06.2011, available at
+\url{http://beagleboard.org/static/BBSRM_latest.pdf}.
+
%bibliography end
\end{thebibliography}