summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report
diff options
context:
space:
mode:
Diffstat (limited to 'notFinishedCode/Report')
-rw-r--r--notFinishedCode/Report/.test.tex.kate-swpbin0 -> 841 bytes
-rw-r--r--notFinishedCode/Report/test.aux4
-rw-r--r--notFinishedCode/Report/test.log18
-rw-r--r--notFinishedCode/Report/test.pdfbin597569 -> 598443 bytes
-rw-r--r--notFinishedCode/Report/test.tex15
-rw-r--r--notFinishedCode/Report/test.tex.backup14
-rw-r--r--notFinishedCode/Report/test.tex~15
-rw-r--r--notFinishedCode/Report/test.toc4
8 files changed, 37 insertions, 33 deletions
diff --git a/notFinishedCode/Report/.test.tex.kate-swp b/notFinishedCode/Report/.test.tex.kate-swp
new file mode 100644
index 0000000..bc13d34
--- /dev/null
+++ b/notFinishedCode/Report/.test.tex.kate-swp
Binary files differ
diff --git a/notFinishedCode/Report/test.aux b/notFinishedCode/Report/test.aux
index 981dc32..0d9c017 100644
--- a/notFinishedCode/Report/test.aux
+++ b/notFinishedCode/Report/test.aux
@@ -4,11 +4,11 @@
\@writefile{lof}{\select@language{english}}
\@writefile{lot}{\select@language{english}}
\@writefile{toc}{\contentsline {section}{\numberline {1}Introduction and Motivation}{3}}
-\@writefile{toc}{\contentsline {section}{\numberline {2}Software requests}{4}}
+\@writefile{toc}{\contentsline {section}{\numberline {2}Requests}{4}}
\@writefile{toc}{\contentsline {section}{\numberline {3}Database design}{5}}
\@writefile{toc}{\contentsline {section}{\numberline {4}Software design}{6}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Usage}{6}}
-\@writefile{toc}{\contentsline {section}{\numberline {5}Hardware Design}{7}}
+\@writefile{toc}{\contentsline {section}{\numberline {5}Hardware design}{7}}
\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces }}{7}}
\@writefile{toc}{\contentsline {section}{\numberline {6}Communication protocol}{8}}
\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces }}{8}}
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index 60378f0..214d813 100644
--- a/notFinishedCode/Report/test.log
+++ b/notFinishedCode/Report/test.log
@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 9 OCT 2011 16:52
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 9 OCT 2011 17:55
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -321,27 +321,27 @@ File: sshTunnel.png Graphic file (type png)
<./sshTunnel.png (PNG copy)>]
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <9> on input line 174.
+(Font) <9> on input line 175.
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <5> on input line 174.
+(Font) <5> on input line 175.
[11] [12]
-LaTeX Font Info: Try loading font information for OMS+cmr on input line 285.
+LaTeX Font Info: Try loading font information for OMS+cmr on input line 286.
(/usr/share/texmf-texlive/tex/latex/base/omscmr.fd
File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 285.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 286.
[13] [14] [15]
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <12> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 357.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 358.
<resultsImage.png, id=67, 702.625pt x 431.6125pt>
File: resultsImage.png Graphic file (type png)
<use resultsImage.png>
[16 <./resultsImage.png (PNG copy)>] [17]
-LaTeX Font Info: Try loading font information for T1+cmtt on input line 382.
+LaTeX Font Info: Try loading font information for T1+cmtt on input line 383.
(/usr/share/texmf-texlive/tex/latex/base/t1cmtt.fd
@@ -369,9 +369,9 @@ ur/jknappen/ec/ecsx1440.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen
0.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen/ec/ecrm1728.600pk></u
sr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmsy10.pfb></usr/share/te
xmf-texlive/fonts/type1/public/amsfonts/cm/cmsy9.pfb>
-Output written on test.pdf (18 pages, 597569 bytes).
+Output written on test.pdf (18 pages, 598443 bytes).
PDF statistics:
- 564 PDF objects out of 1000 (max. 8388607)
+ 566 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 500000)
36 words of extra memory for PDF output out of 10000 (max. 10000000)
diff --git a/notFinishedCode/Report/test.pdf b/notFinishedCode/Report/test.pdf
index 59f91b4..0d5459c 100644
--- a/notFinishedCode/Report/test.pdf
+++ b/notFinishedCode/Report/test.pdf
Binary files differ
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index 8b8c36b..d0e70d9 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -102,26 +102,27 @@ 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 the option to choose all the hardware ourself beside the two BeagleBoards, which we were luckily 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 our 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}
-\par Our first attempt was to control a Nokia cell phone 3310 over the supplied USB connection cables.
-Protocol used by Nokia 3310 was the F-Bus and it was not easy to work with.
+\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.
+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.
\newpage
\section{Communication protocol}
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}
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index 8b8c36b..24fb21e 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -102,26 +102,27 @@ 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 the option to choose all the hardware ourself beside the two BeagleBoards, which we were luckily 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 our 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}
-\par Our first attempt was to control a Nokia cell phone 3310 over the supplied USB connection cables.
-Protocol used by Nokia 3310 was the F-Bus and it was not easy to work with.
+\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.
+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 and it was not so difficult to control it with the
\newpage
\section{Communication protocol}
diff --git a/notFinishedCode/Report/test.toc b/notFinishedCode/Report/test.toc
index 3c22ab2..2f6da58 100644
--- a/notFinishedCode/Report/test.toc
+++ b/notFinishedCode/Report/test.toc
@@ -1,10 +1,10 @@
\select@language {english}
\contentsline {section}{\numberline {1}Introduction and Motivation}{3}
-\contentsline {section}{\numberline {2}Software requests}{4}
+\contentsline {section}{\numberline {2}Requests}{4}
\contentsline {section}{\numberline {3}Database design}{5}
\contentsline {section}{\numberline {4}Software design}{6}
\contentsline {subsection}{\numberline {4.1}Usage}{6}
-\contentsline {section}{\numberline {5}Hardware Design}{7}
+\contentsline {section}{\numberline {5}Hardware design}{7}
\contentsline {section}{\numberline {6}Communication protocol}{8}
\contentsline {section}{\numberline {7}Security and safety of the system}{10}
\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{10}