summaryrefslogtreecommitdiffstats
path: root/notFinishedCode
diff options
context:
space:
mode:
Diffstat (limited to 'notFinishedCode')
-rw-r--r--notFinishedCode/Report/.test.tex.kate-swpbin1827 -> 0 bytes
-rw-r--r--notFinishedCode/Report/test.aux6
-rw-r--r--notFinishedCode/Report/test.log126
-rw-r--r--notFinishedCode/Report/test.pdfbin603598 -> 609349 bytes
-rw-r--r--notFinishedCode/Report/test.tex55
-rw-r--r--notFinishedCode/Report/test.tex.backup65
-rw-r--r--notFinishedCode/Report/test.tex~53
-rw-r--r--notFinishedCode/Report/test.toc4
8 files changed, 252 insertions, 57 deletions
diff --git a/notFinishedCode/Report/.test.tex.kate-swp b/notFinishedCode/Report/.test.tex.kate-swp
deleted file mode 100644
index 67f696f..0000000
--- a/notFinishedCode/Report/.test.tex.kate-swp
+++ /dev/null
Binary files differ
diff --git a/notFinishedCode/Report/test.aux b/notFinishedCode/Report/test.aux
index e4a2b13..4bb90ba 100644
--- a/notFinishedCode/Report/test.aux
+++ b/notFinishedCode/Report/test.aux
@@ -9,7 +9,7 @@
\@writefile{toc}{\contentsline {section}{\numberline {4}Software design}{6}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}Database access}{6}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}Controlling the cell phones}{6}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}}{6}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}subsection}{6}}
\citation{beagleDataSheet}
\@writefile{toc}{\contentsline {section}{\numberline {5}Hardware design}{7}}
\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}BeagleBoard}{7}}
@@ -17,9 +17,11 @@
\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Cell phones}{8}}
\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}Cables for the cell phones}{8}}
\@writefile{toc}{\contentsline {section}{\numberline {6}Communication protocol}{9}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Hanlder side}{9}}
\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces }}{9}}
\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces }}{9}}
-\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces }}{10}}
+\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces }}{9}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verification of the protocol}{10}}
\citation{sshTunnel}
\@writefile{toc}{\contentsline {section}{\numberline {7}Security and safety of the system}{11}}
\@writefile{toc}{\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{11}}
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index 46dc006..4e10f0a 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 18:49
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 9 OCT 2011 19:18
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -287,13 +287,13 @@ Class scrartcl Info: You've told me to use the font selection of the element
(scrartcl) on input line 13.
Class scrartcl Info: You've told me to use the font selection of the element
(scrartcl) `sectioning' that is an alias of element `disposition'
-(scrartcl) on input line 14.
+(scrartcl) on input line 16.
Class scrartcl Info: You've told me to use the font selection of the element
(scrartcl) `sectioning' that is an alias of element `disposition'
-(scrartcl) on input line 17.
+(scrartcl) on input line 19.
Class scrartcl Info: You've told me to use the font selection of the element
(scrartcl) `sectioning' that is an alias of element `disposition'
-(scrartcl) on input line 20.
+(scrartcl) on input line 22.
)
\tf@toc=\write4
\openout4 = `test.toc'.
@@ -312,36 +312,116 @@ File: protocolCommunicationcControllerReceiver.png Graphic file (type png)
<use protocolCommunicationcControllerReceiver.png>
<protocolCommunicationcControllerCaller.png, id=38, 1808.16705pt x 766.62883pt>
File: protocolCommunicationcControllerCaller.png Graphic file (type png)
-<use protocolCommunicationcControllerCaller.png> [9 <./protocolCommunicationHan
-dler.png (PNG copy)> <./protocolCommunicationcControllerReceiver.png (PNG copy)
->] [10 <./protocolCommunicationcControllerCaller.png (PNG copy)>]
-<sshTunnel.png, id=45, 696.6025pt x 152.57pt>
-File: sshTunnel.png Graphic file (type png)
- <use sshTunnel.png> [11
+<use protocolCommunicationcControllerCaller.png> [9
- <./sshTunnel.png (PNG copy)>]
+ <./protocolCommunicationHandler.png (PNG copy)> <./protocolCommunicationcContr
+ollerReceiver.png (PNG copy)> <./protocolCommunicationcControllerCaller.png (PN
+G copy)>]
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <9> on input line 194.
+(Font) <9> on input line 175.
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <5> on input line 194.
- [12] [13]
-LaTeX Font Info: Try loading font information for OMS+cmr on input line 305.
+(Font) <5> on input line 175.
+
+
+! Package inputenc Error: Keyboard character used is undefined
+(inputenc) in inputencoding `latin2'.
+
+See the inputenc package documentation for explanation.
+Type H <return> for immediate help.
+ ...
+
+l.182 ...tor 44 byte, depth reached 65, •••
+ errors: 0 •••
+You need to provide a definition with \DeclareInputText
+or \DeclareInputMath before using this key.
+
+
+! Package inputenc Error: Keyboard character used is undefined
+(inputenc) in inputencoding `latin2'.
+
+See the inputenc package documentation for explanation.
+Type H <return> for immediate help.
+ ...
+
+l.182 ...tor 44 byte, depth reached 65, •••
+ errors: 0 •••
+You need to provide a definition with \DeclareInputText
+or \DeclareInputMath before using this key.
+
+
+! Package inputenc Error: Keyboard character used is undefined
+(inputenc) in inputencoding `latin2'.
+
+See the inputenc package documentation for explanation.
+Type H <return> for immediate help.
+ ...
+
+l.182 ...tor 44 byte, depth reached 65, •••
+ errors: 0 •••
+You need to provide a definition with \DeclareInputText
+or \DeclareInputMath before using this key.
+
+
+! Package inputenc Error: Keyboard character used is undefined
+(inputenc) in inputencoding `latin2'.
+
+See the inputenc package documentation for explanation.
+Type H <return> for immediate help.
+ ...
+
+l.182 ...reached 65, ••• errors: 0 •••
+
+You need to provide a definition with \DeclareInputText
+or \DeclareInputMath before using this key.
+
+
+! Package inputenc Error: Keyboard character used is undefined
+(inputenc) in inputencoding `latin2'.
+
+See the inputenc package documentation for explanation.
+Type H <return> for immediate help.
+ ...
+
+l.182 ...reached 65, ••• errors: 0 •••
+
+You need to provide a definition with \DeclareInputText
+or \DeclareInputMath before using this key.
+
+
+! Package inputenc Error: Keyboard character used is undefined
+(inputenc) in inputencoding `latin2'.
+
+See the inputenc package documentation for explanation.
+Type H <return> for immediate help.
+ ...
+
+l.182 ...reached 65, ••• errors: 0 •••
+
+You need to provide a definition with \DeclareInputText
+or \DeclareInputMath before using this key.
+
+[10] <sshTunnel.png, id=47, 696.6025pt x 152.57pt>
+File: sshTunnel.png Graphic file (type png)
+ <use sshTunnel.png> [11
+
+ <./sshTunnel.png (PNG copy)>] [12] [13]
+LaTeX Font Info: Try loading font information for OMS+cmr on input line 338.
(/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 305.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 338.
[14] [15] [16]
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 377.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 410.
<resultsImage.png, id=70, 702.625pt x 431.6125pt>
File: resultsImage.png Graphic file (type png)
<use resultsImage.png>
[17 <./resultsImage.png (PNG copy)>] [18]
-LaTeX Font Info: Try loading font information for T1+cmtt on input line 402.
+LaTeX Font Info: Try loading font information for T1+cmtt on input line 435.
(/usr/share/texmf-texlive/tex/latex/base/t1cmtt.fd
@@ -349,10 +429,10 @@ File: t1cmtt.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
AED: lastpage setting LastPage [19] (./test.aux) )
Here is how much of TeX's memory you used:
- 4885 strings out of 495061
- 67574 string characters out of 1182621
+ 4886 strings out of 495061
+ 67587 string characters out of 1182621
255259 words of memory out of 3000000
- 8002 multiletter control sequences out of 15000+50000
+ 8003 multiletter control sequences out of 15000+50000
18484 words of font info for 43 fonts, out of 3000000 for 9000
28 hyphenation exceptions out of 8191
36i,10n,45p,751b,1285s stack positions out of 5000i,500n,10000p,200000b,50000s
@@ -369,9 +449,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 (19 pages, 603598 bytes).
+Output written on test.pdf (19 pages, 609349 bytes).
PDF statistics:
- 578 PDF objects out of 1000 (max. 8388607)
+ 589 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 5056692..939dad1 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 af12352..1224bf0 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -114,23 +114,28 @@ Our first version of the developed program code for controlling the cell phones
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{}
+\subsection{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.
+In our team project we had the option to choose all the required hardware ourself beside the two BeagleBoards, which we were 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 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}.
+Source Community.
\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}
+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}.
+We run on it a special precompiled version of Ubuntu for the ARM processor type.
+The board has an USB hub and network port attached to it. In our project it is connected to our
+internal university LAN network and to a cell phone. We positioned the two BeagleBoards in rooms where
+we had LAN access and GSM signal coverage of our two local base stations.
\subsection{Cell phones}
Our first attempt was to control a Nokia cell phone 3310 with the supplied USB connection cable.
@@ -142,27 +147,55 @@ At the start we did not have a cable supplied for the Siemens S55 phone. We cont
\subsection{Cables for the cell phones}
-\newpage
-\section{Communication protocol}
+\clearpage
+\section{Communication protocol}
+\subsection{Hanlder side}
\begin{figure}[ht!]
\centering
- \includegraphics[width=140mm]{protocolCommunicationHandler.png}
+ \includegraphics[width=130mm]{protocolCommunicationHandler.png}
\caption[]{Flowchart of the protocol, on the handler side}
\end{figure}
\begin{figure}[ht!]
\centering
- \includegraphics[width=140mm]{protocolCommunicationcControllerReceiver.png}
+ \includegraphics[width=130mm]{protocolCommunicationcControllerReceiver.png}
\caption[]{Flowchart of the protocol, on the controller side for the caller}
\end{figure}
\begin{figure}[ht!]
\centering
- \includegraphics[width=140mm]{protocolCommunicationcControllerCaller.png}
+ \includegraphics[width=130mm]{protocolCommunicationcControllerCaller.png}
\caption[]{Flowchart of the protocol, on the controller side for the receiver}
\end{figure}
+\subsection{Verification of the protocol}
+The verification results are listed here:
+\begin{lstlisting}
+(Spin Version 6.1.0 -- 2 May 2011)
+ + Partial Order Reduction
+Full statespace search for:
+ never claim - (none specified)
+ assertion violations +
+ cycle checks - (disabled by -DSAFETY)
+ invalid end states +
+State-vector 44 byte, depth reached 65, ••• errors: 0 •••
+ 40 states, stored
+ 3 states, matched
+ 43 transitions (= stored+matched)
+ 90 atomic steps
+hash conflicts: 0 (resolved)
+ 2.195 memory usage (Mbyte)
+unreached in proctype Server1
+ (0 of 36 states)
+unreached in proctype Server2
+ (0 of 36 states)
+unreached in proctype Client
+ (0 of 67 states)
+pan: elapsed time 0 seconds
+\end{lstlisting}
+
+
\clearpage
\newpage
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index 2bf7a72..28acb38 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -117,23 +117,38 @@ our first approach was inferior and slower. The state controlled method connecte
\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.
+In our team project we had the option to choose all the required hardware ourself beside the two BeagleBoards, which we were 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 found in our lab.
+\subsection{BeagleBoard}
+``The BeagleBoard is an OMAP3530 platform designed specifically to address the Open
+Source Community.
\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.
-At the start we did not have a cable supplied with the Siemens S55 phone. We controlled it over the Bluetooth port.
-\subsection{Cables}
+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}.
+We run on it a special precompiled version of Ubuntu for the ARM processor type.
+The board has an USB hub and network port attached to it. In our project it is connected to our
+internal university LAN network and to a cell phone. We positioned the two BeagleBoards in rooms where
+we had LAN access and GSM signal coverage of our two local base stations.
+
+\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}
+
+\clearpage
-\newpage
\section{Communication protocol}
\begin{figure}[ht!]
@@ -154,6 +169,33 @@ At the start we did not have a cable supplied with the Siemens S55 phone. We con
\caption[]{Flowchart of the protocol, on the controller side for the receiver}
\end{figure}
+\begin{lstlisting}
+
+(Spin Version 6.1.0 -- 2 May 2011)
+ + Partial Order Reduction
+Full statespace search for:
+ never claim - (none specified)
+ assertion violations +
+ cycle checks - (disabled by -DSAFETY)
+ invalid end states +
+State-vector 44 byte, depth reached 65, ••• errors: 0 •••
+ 40 states, stored
+ 3 states, matched
+ 43 transitions (= stored+matched)
+ 90 atomic steps
+hash conflicts: 0 (resolved)
+ 2.195 memory usage (Mbyte)
+unreached in proctype Server1
+ (0 of 36 states)
+unreached in proctype Server2
+ (0 of 36 states)
+unreached in proctype Client
+ (0 of 67 states)
+pan: elapsed time 0 seconds
+
+\end{lstlisting}
+
+
\clearpage
\newpage
@@ -401,6 +443,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}
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index 5719ec7..dc38a71 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -114,23 +114,28 @@ Our first version of the developed program code for controlling the cell phones
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{}
+\subsection{Some 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.
+In our team project we had the option to choose all the required hardware ourself beside the two BeagleBoards, which we were 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 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}.
+Source Community.
\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}
+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}.
+We run on it a special precompiled version of Ubuntu for the ARM processor type.
+The board has an USB hub and network port attached to it. In our project it is connected to our
+internal university LAN network and to a cell phone. We positioned the two BeagleBoards in rooms where
+we had LAN access and GSM signal coverage of our two local base stations.
\subsection{Cell phones}
Our first attempt was to control a Nokia cell phone 3310 with the supplied USB connection cable.
@@ -142,9 +147,10 @@ At the start we did not have a cable supplied for the Siemens S55 phone. We cont
\subsection{Cables for the cell phones}
-\newpage
-\section{Communication protocol}
+\clearpage
+\section{Communication protocol}
+\subsection{Hanlder side}
\begin{figure}[ht!]
\centering
\includegraphics[width=140mm]{protocolCommunicationHandler.png}
@@ -163,8 +169,35 @@ At the start we did not have a cable supplied for the Siemens S55 phone. We cont
\caption[]{Flowchart of the protocol, on the controller side for the receiver}
\end{figure}
+\subsection{Verification of the protocol}
+The verification results are listed here:
+\begin{lstlisting}
+(Spin Version 6.1.0 -- 2 May 2011)
+ + Partial Order Reduction
+Full statespace search for:
+ never claim - (none specified)
+ assertion violations +
+ cycle checks - (disabled by -DSAFETY)
+ invalid end states +
+State-vector 44 byte, depth reached 65, ••• errors: 0 •••
+ 40 states, stored
+ 3 states, matched
+ 43 transitions (= stored+matched)
+ 90 atomic steps
+hash conflicts: 0 (resolved)
+ 2.195 memory usage (Mbyte)
+unreached in proctype Server1
+ (0 of 36 states)
+unreached in proctype Server2
+ (0 of 36 states)
+unreached in proctype Client
+ (0 of 67 states)
+pan: elapsed time 0 seconds
+\end{lstlisting}
+
+
\clearpage
-\newpage
+
\section{Security and safety of the system}
@@ -410,7 +443,7 @@ 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
+\bibitem{beagleDataSheet} \emph{BeagleBoard System Reference Manual}, accessed on 20.06.2011, available at
\url{http://beagleboard.org/static/BBSRM_latest.pdf}.
%bibliography end
diff --git a/notFinishedCode/Report/test.toc b/notFinishedCode/Report/test.toc
index a6e62b0..9616a50 100644
--- a/notFinishedCode/Report/test.toc
+++ b/notFinishedCode/Report/test.toc
@@ -5,12 +5,14 @@
\contentsline {section}{\numberline {4}Software design}{6}
\contentsline {subsection}{\numberline {4.1}Database access}{6}
\contentsline {subsection}{\numberline {4.2}Controlling the cell phones}{6}
-\contentsline {subsection}{\numberline {4.3}}{6}
+\contentsline {subsection}{\numberline {4.3}subsection}{6}
\contentsline {section}{\numberline {5}Hardware design}{7}
\contentsline {subsection}{\numberline {5.1}BeagleBoard}{7}
\contentsline {subsection}{\numberline {5.2}Cell phones}{8}
\contentsline {subsection}{\numberline {5.3}Cables for the cell phones}{8}
\contentsline {section}{\numberline {6}Communication protocol}{9}
+\contentsline {subsection}{\numberline {6.1}Hanlder side}{9}
+\contentsline {subsection}{\numberline {6.2}Verification of the protocol}{10}
\contentsline {section}{\numberline {7}Security and safety of the system}{11}
\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{11}
\contentsline {subsection}{\numberline {7.2}Security on the web site}{12}