summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex.backup
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-09 17:57:06 +0200
committerRefik Hadzialic2011-10-09 17:57:06 +0200
commit6b6ecd745e6940f8d59d27cdb7f3036c54ff9c96 (patch)
treed9b59b5d72a8db4740d25a8ad737248259a0c285 /notFinishedCode/Report/test.tex.backup
parentContinued to work on the report! (diff)
downloadgsm-selftest-6b6ecd745e6940f8d59d27cdb7f3036c54ff9c96.tar.gz
gsm-selftest-6b6ecd745e6940f8d59d27cdb7f3036c54ff9c96.tar.xz
gsm-selftest-6b6ecd745e6940f8d59d27cdb7f3036c54ff9c96.zip
Added changes to the report!
Diffstat (limited to 'notFinishedCode/Report/test.tex.backup')
-rw-r--r--notFinishedCode/Report/test.tex.backup14
1 files changed, 8 insertions, 6 deletions
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index 73c65bd..9cc4e7c 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -102,24 +102,26 @@ 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{Software requests} % chapter 2
+\section{Requests} % chapter 2
\newpage
\section{Database design}
\newpage
\section{Software design} % section 2.1
\subsection{Usage} % subsection 2.1.1
\newpage
-\section{Hardware Design}
-In our team project we had not the option to choose the hardware however we were lucky to have
-two BeagleBoards which were supplied by Konrad and Dennis.
-Since one of the project goals was to save as much money as it was possible we had tried to use some of the leftovers in the lab.
+\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.
\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}
-Our first attempt was
+\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.
\newpage
\section{Communication protocol}