summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--notFinishedCode/Report/test.aux54
-rw-r--r--notFinishedCode/Report/test.log54
-rw-r--r--notFinishedCode/Report/test.pdfbin1486561 -> 1489239 bytes
-rw-r--r--notFinishedCode/Report/test.tex22
-rw-r--r--notFinishedCode/Report/test.tex.backup34
-rw-r--r--notFinishedCode/Report/test.tex~23
-rw-r--r--notFinishedCode/Report/test.toc39
7 files changed, 150 insertions, 76 deletions
diff --git a/notFinishedCode/Report/test.aux b/notFinishedCode/Report/test.aux
index 2bc478e..f4262b2 100644
--- a/notFinishedCode/Report/test.aux
+++ b/notFinishedCode/Report/test.aux
@@ -35,43 +35,47 @@
\@writefile{lof}{\contentsline {figure}{\numberline {9}{\ignorespaces }}{14}}
\@writefile{lof}{\contentsline {figure}{\numberline {10}{\ignorespaces }}{14}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Ping class}{14}}
+\citation{wiki}
\@writefile{lof}{\contentsline {figure}{\numberline {11}{\ignorespaces }}{15}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.5}Data logging}{15}}
\@writefile{lof}{\contentsline {figure}{\numberline {12}{\ignorespaces }}{15}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.6}SSH Class}{15}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.7}USB Cell phone detection class}{15}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.8}Truth table class}{16}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.9}Init Test class}{16}}
\citation{beagleDataSheet}
-\@writefile{toc}{\contentsline {section}{\numberline {5}Hardware design}{16}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}BeagleBoard}{16}}
-\@writefile{lof}{\contentsline {figure}{\numberline {13}{\ignorespaces }}{16}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Cell phones}{17}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}Cables for the cell phones}{17}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {5.4}Server}{17}}
-\@writefile{toc}{\contentsline {section}{\numberline {6}Communication protocol}{18}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Communication between the handler and controller}{18}}
+\@writefile{toc}{\contentsline {section}{\numberline {5}Hardware design}{17}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}BeagleBoard}{17}}
+\@writefile{lof}{\contentsline {figure}{\numberline {13}{\ignorespaces }}{17}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Cell phones}{18}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}Cables for the cell phones}{18}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {5.4}Server}{18}}
+\@writefile{toc}{\contentsline {section}{\numberline {6}Communication protocol}{19}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {6.1}Communication between the handler and controller}{19}}
\citation{spin}
\citation{spin}
\citation{wiki}
-\@writefile{lof}{\contentsline {figure}{\numberline {14}{\ignorespaces }}{19}}
-\@writefile{lof}{\contentsline {figure}{\numberline {15}{\ignorespaces }}{19}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verification of the protocol}{19}}
-\@writefile{lof}{\contentsline {figure}{\numberline {16}{\ignorespaces }}{20}}
+\@writefile{lof}{\contentsline {figure}{\numberline {14}{\ignorespaces }}{20}}
+\@writefile{lof}{\contentsline {figure}{\numberline {15}{\ignorespaces }}{20}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verification of the protocol}{20}}
+\@writefile{lof}{\contentsline {figure}{\numberline {16}{\ignorespaces }}{21}}
\citation{sshTunnel}
-\@writefile{toc}{\contentsline {section}{\numberline {7}Security and safety of the system}{22}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{22}}
-\@writefile{lof}{\contentsline {figure}{\numberline {17}{\ignorespaces }}{22}}
+\@writefile{toc}{\contentsline {section}{\numberline {7}Security and safety of the system}{23}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{23}}
+\@writefile{lof}{\contentsline {figure}{\numberline {17}{\ignorespaces }}{23}}
\citation{https}
-\@writefile{toc}{\contentsline {subsection}{\numberline {7.2}Security on the web site}{23}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {7.2}Security on the web site}{24}}
\citation{https}
\citation{https}
-\@writefile{toc}{\contentsline {section}{\numberline {8}Web page}{27}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Communication between the web page and the test software}{27}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Results on the web page}{27}}
+\@writefile{toc}{\contentsline {section}{\numberline {8}Web page}{28}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Communication between the web page and the test software}{28}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Results on the web page}{28}}
\citation{pChart}
-\@writefile{lof}{\contentsline {figure}{\numberline {18}{\ignorespaces }}{28}}
-\@writefile{toc}{\contentsline {section}{\numberline {9}How to use and start the system}{29}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {9.1}Required libraries}{29}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {9.2}Configuring hardware}{29}}
-\@writefile{toc}{\contentsline {section}{\numberline {10}Conclusion}{30}}
+\@writefile{lof}{\contentsline {figure}{\numberline {18}{\ignorespaces }}{29}}
+\@writefile{toc}{\contentsline {section}{\numberline {9}How to use and start the system}{30}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {9.1}Required libraries}{30}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {9.2}Configuring hardware}{30}}
+\@writefile{toc}{\contentsline {section}{\numberline {10}Conclusion}{31}}
\bibcite{network}{1}
\bibcite{python}{2}
\bibcite{mysqlManual}{3}
@@ -82,4 +86,4 @@
\bibcite{https}{8}
\bibcite{pChart}{9}
\bibcite{beagleDataSheet}{10}
-\newlabel{LastPage}{{}{31}}
+\newlabel{LastPage}{{}{32}}
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index 6f1488b..c729637 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) 23 OCT 2011 15:34
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 24 OCT 2011 16:36
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -281,22 +281,22 @@ Class scrartcl Info: You've told me to use the font selection of the element
(scrartcl) on input line 8.
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 15.
+(scrartcl) on input line 17.
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.
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 23.
+(scrartcl) on input line 25.
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 26.
+(scrartcl) on input line 28.
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 29.
+(scrartcl) on input line 31.
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 32.
+(scrartcl) on input line 34.
)
\tf@toc=\write4
\openout4 = `test.toc'.
@@ -368,40 +368,40 @@ File: ping.png Graphic file (type png)
File: logging.png Graphic file (type png)
<use logging.png> [14 <./serverClass.png (PNG copy)> <./ClientClass.png (PNG co
-py)>] [15 <./ping.png (PNG copy)> <./logging.png (PNG copy)>]
-<bb.jpg, id=80, 521.95pt x 516.93124pt>
+py)>] [15 <./ping.png (PNG copy)> <./logging.png (PNG copy)>] [16]
+<bb.jpg, id=83, 521.95pt x 516.93124pt>
File: bb.jpg Graphic file (type jpg)
- <use bb.jpg> [16
+ <use bb.jpg> [17
- <./bb.jpg>] [17]
-[18
+ <./bb.jpg>] [18]
+[19
-] <protocolCommunicationHandler.png, id=91, 2486.93823pt x 792.13588pt>
+] <protocolCommunicationHandler.png, id=95, 2486.93823pt x 792.13588pt>
File: protocolCommunicationHandler.png Graphic file (type png)
<use protocolCommunicationHandler.png>
-<protocolCommunicationcControllerReceiver.png, id=92, 1808.16705pt x 766.62883p
+<protocolCommunicationcControllerReceiver.png, id=96, 1808.16705pt x 766.62883p
t>
File: protocolCommunicationcControllerReceiver.png Graphic file (type png)
<use protocolCommunicationcControllerReceiver.png>
-<protocolCommunicationcControllerCaller.png, id=93, 1808.16705pt x 766.62883pt>
+<protocolCommunicationcControllerCaller.png, id=97, 1808.16705pt x 766.62883pt>
File: protocolCommunicationcControllerCaller.png Graphic file (type png)
-<use protocolCommunicationcControllerCaller.png> [19 <./protocolCommunicationHa
+<use protocolCommunicationcControllerCaller.png> [20 <./protocolCommunicationHa
ndler.png (PNG copy)> <./protocolCommunicationcControllerReceiver.png (PNG copy
-)>] [20 <./protocolCommunicationcControllerCaller.png (PNG copy)>] [21]
-<sshTunnel.png, id=105, 696.6025pt x 152.57pt>
+)>] [21 <./protocolCommunicationcControllerCaller.png (PNG copy)>] [22]
+<sshTunnel.png, id=108, 696.6025pt x 152.57pt>
File: sshTunnel.png Graphic file (type png)
- <use sshTunnel.png> [22
+ <use sshTunnel.png> [23
- <./sshTunnel.png (PNG copy)>] [23] [24]
+ <./sshTunnel.png (PNG copy)>] [24] [25]
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 596.
- [25] [26] [27]
-<resultsImage.png, id=125, 702.625pt x 431.6125pt>
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 616.
+ [26] [27] [28]
+<resultsImage.png, id=128, 702.625pt x 431.6125pt>
File: resultsImage.png Graphic file (type png)
<use resultsImage.png>
-[28 <./resultsImage.png (PNG copy)>] [29] [30] AED: lastpage setting LastPage
-[31] (./test.aux) )
+[29 <./resultsImage.png (PNG copy)>] [30] [31] AED: lastpage setting LastPage
+[32] (./test.aux) )
Here is how much of TeX's memory you used:
4948 strings out of 495061
68792 string characters out of 1182621
@@ -424,9 +424,9 @@ r/fonts/pk/ljfour/jknappen/ec/ecrm1728.600pk></usr/share/texmf-texlive/fonts/ty
pe1/public/amsfonts/cm/cmmi10.pfb></usr/share/texmf-texlive/fonts/type1/public/
amsfonts/cm/cmsy10.pfb></usr/share/texmf-texlive/fonts/type1/public/amsfonts/cm
/cmsy9.pfb>
-Output written on test.pdf (31 pages, 1486561 bytes).
+Output written on test.pdf (32 pages, 1489239 bytes).
PDF statistics:
- 711 PDF objects out of 1000 (max. 8388607)
+ 717 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 500000)
96 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 1e24ac2..66ca636 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 10bee7c..3d8430b 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -305,7 +305,27 @@ How the class works and what kind of outputs it produces can be found on our pro
\subsection{SSH Class}
Since security played an important role in our team project. We decided to encrypt all of our data that was not processed on our server computer.
The simplest solution to this problem was to build an SSH Class that could open and close a local forwarding port.
-All data sent through that port is encrypted until it gets to its destination location.
+All data sent through the created port is encrypted until it gets to its destination location.
+\subsection{USB Cell phone detection class}
+Since we had used cables to connect the cell phones with the computer, usually the devices
+got their own port addresses. They were automatically assigned by the operating system,
+either after the cables were plugged into the USB port or after a system reboot.
+One of the problems we had to deal with was assigning the right cell phone
+(i.e. with the appropriate GSM network) to the corresponding port address.
+The operating system randomly assigned the port names after every reboot.
+We were looking for a solution to prevent this misaddressing of the devices.
+Our solution was to recognize every device and update the port address in the database.
+The principle how we identify the cell phones is by their calling numbers in the database.
+More details can be found on our project wiki page \cite{wiki}.
+\subsection{Truth table class}
+The truth table class was built to identify the broken and working parts of the system.
+It requires the test results to be present to be operable.
+Then the class tries to identify the broken parts of our telecommunication network.
+The class can easily identify how many nanoBTSs are installed in the network and
+derive a decision which part of the network is broken.
+All the test results are stored in a list and can be easily read by calling the
+\emph{initTrueTable(x)} function.
+\subsection{Init Test class}
\clearpage
\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 supplied by Konrad and Dennis.
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index acf4885..15329de 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -221,8 +221,13 @@ proceeds with the tests by connecting itself to the handlers and sending them co
to perform the tests\footnote{Before it connects to the handlers, it uses the ping
results to see is the service/device physically connected to the network.}.
At the higher level, these commands can be seen as requests for being the
-callee and caller. Meanwhile the handlers send their test result to the main
-test software which
+callee and caller. Meanwhile the handlers send their test results to the main
+test software which in return decides if the test result was successful or not.
+The result is written to the database (in case the software was started from the website),
+otherwise the results are displayed in the terminal window and the user who started
+it manually can see the test results. We will proceed with introducing the classes.
+The software class diagram can be seen in the following figure. More details for the
+classes, like the input/output can be found on our project's wiki page \cite{wiki}.
\begin{figure}[ht!]
@@ -231,6 +236,7 @@ test software which
\caption[]{Class diagram (some classes were excluded)}
\end{figure}
+\newpage
\subsection{Database access} % subsection 2.1.1
Accessing the database is of critical value to our project, therefore we had developed our own class that limits the access to the database. In the process of developing our own class we used the MySQLdb library in Python \cite{mysqlManual}.
The database class has two working modes, a normal working mode and a debugging mode. The difference between these two modes is in the output information. In case the error handling function raises an error and it is unknown, if the debug mode is set a complete back-trace of the error will be printed out. A developer can change the mode by setting the variable \emph{debugMode=1}. The class diagram can be seen in the following figure.
@@ -287,7 +293,8 @@ A ping timeout response was set up to 2 seconds. For more details and insights,
\caption[]{Ping class, used by test software}
\end{figure}
\subsection{Data logging}
-If bugs appear it is important to reconstruct the case. One of the best ways to reconstruct the case was to log every single step part of code gets executed.
+If errors appear it is important to reconstruct the events that led to the misbehaviour of the software. One of the best ways to reconstruct the events was to log
+events for different blocks of programming code.
We had used the logging class to follow our handler code run on the BeagleBoard. In case there is an error we could look inside of the log files and track the error.
How the class works and what kind of outputs it produces can be found on our project wiki page \cite{wiki}.
\begin{figure}[ht!]
@@ -296,6 +303,27 @@ How the class works and what kind of outputs it produces can be found on our pro
\caption[]{Logging class}
\end{figure}
\subsection{SSH Class}
+Since security played an important role in our team project. We decided to encrypt all of our data that was not processed on our server computer.
+The simplest solution to this problem was to build an SSH Class that could open and close a local forwarding port.
+All data sent through the created port is encrypted until it gets to its destination location.
+\subsection{USB Cell phone detection class}
+Since we had used cables to connect the cell phones with the computer, usually the devices
+got their own port addresses. They were automatically assigned by the operating system,
+either after the cables were plugged into the USB port or after a system reboot.
+One of the problems we had to deal with was assigning the right cell phone
+(i.e. with the appropriate GSM network) to the corresponding port address.
+The operating system randomly assigned the port names after every reboot.
+We were looking for a solution to prevent this misaddressing of the devices.
+Our solution was to recognize every device and update the port address in the database.
+The principle how we identify the cell phones is by their calling numbers in the database.
+More details can be found on our project wiki page \cite{wiki}.
+\subsection{Truth table class}
+The truth table class was built to identify the broken and working parts of the system.
+It requires the test results to be present to be operable.
+Then the class tries to identify the broken parts of our telecommunication network.
+The class can easily identify how many nanoBTSs are installed on the network and
+derive a decision which part of the network is broken.
+All the results are stored in the list which are easy to read by the initTrueTable(x) function.
\clearpage
\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 supplied by Konrad and Dennis.
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index a0b7df3..d9bc00e 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -303,8 +303,27 @@ How the class works and what kind of outputs it produces can be found on our pro
\caption[]{Logging class}
\end{figure}
\subsection{SSH Class}
-Since security played an important role in our team project. We decided to encrypt all our data that was not handled on our server.
-The simplest solution to this problem was to build an SSH Class that could open and close a local virtual port.
+Since security played an important role in our team project. We decided to encrypt all of our data that was not processed on our server computer.
+The simplest solution to this problem was to build an SSH Class that could open and close a local forwarding port.
+All data sent through the created port is encrypted until it gets to its destination location.
+\subsection{USB Cell phone detection class}
+Since we had used cables to connect the cell phones with the computer, usually the devices
+got their own port addresses. They were automatically assigned by the operating system,
+either after the cables were plugged into the USB port or after a system reboot.
+One of the problems we had to deal with was assigning the right cell phone
+(i.e. with the appropriate GSM network) to the corresponding port address.
+The operating system randomly assigned the port names after every reboot.
+We were looking for a solution to prevent this misaddressing of the devices.
+Our solution was to recognize every device and update the port address in the database.
+The principle how we identify the cell phones is by their calling numbers in the database.
+More details can be found on our project wiki page \cite{wiki}.
+\subsection{Truth table class}
+The truth table class was built to identify the broken and working parts of the system.
+It requires the test results to be present to be operable.
+Then the class tries to identify the broken parts of our telecommunication network.
+The class can easily identify how many nanoBTSs are installed in the network and
+derive a decision which part of the network is broken.
+All the test results are stored in a list, can be forwarded to the \emph{initTrueTable(listWithResults)} function.
\clearpage
\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 supplied by Konrad and Dennis.
diff --git a/notFinishedCode/Report/test.toc b/notFinishedCode/Report/test.toc
index 759c6d7..00deae8 100644
--- a/notFinishedCode/Report/test.toc
+++ b/notFinishedCode/Report/test.toc
@@ -12,21 +12,24 @@
\contentsline {subsection}{\numberline {4.4}Ping class}{14}
\contentsline {subsection}{\numberline {4.5}Data logging}{15}
\contentsline {subsection}{\numberline {4.6}SSH Class}{15}
-\contentsline {section}{\numberline {5}Hardware design}{16}
-\contentsline {subsection}{\numberline {5.1}BeagleBoard}{16}
-\contentsline {subsection}{\numberline {5.2}Cell phones}{17}
-\contentsline {subsection}{\numberline {5.3}Cables for the cell phones}{17}
-\contentsline {subsection}{\numberline {5.4}Server}{17}
-\contentsline {section}{\numberline {6}Communication protocol}{18}
-\contentsline {subsection}{\numberline {6.1}Communication between the handler and controller}{18}
-\contentsline {subsection}{\numberline {6.2}Verification of the protocol}{19}
-\contentsline {section}{\numberline {7}Security and safety of the system}{22}
-\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{22}
-\contentsline {subsection}{\numberline {7.2}Security on the web site}{23}
-\contentsline {section}{\numberline {8}Web page}{27}
-\contentsline {subsection}{\numberline {8.1}Communication between the web page and the test software}{27}
-\contentsline {subsection}{\numberline {8.2}Results on the web page}{27}
-\contentsline {section}{\numberline {9}How to use and start the system}{29}
-\contentsline {subsection}{\numberline {9.1}Required libraries}{29}
-\contentsline {subsection}{\numberline {9.2}Configuring hardware}{29}
-\contentsline {section}{\numberline {10}Conclusion}{30}
+\contentsline {subsection}{\numberline {4.7}USB Cell phone detection class}{15}
+\contentsline {subsection}{\numberline {4.8}Truth table class}{16}
+\contentsline {subsection}{\numberline {4.9}Init Test class}{16}
+\contentsline {section}{\numberline {5}Hardware design}{17}
+\contentsline {subsection}{\numberline {5.1}BeagleBoard}{17}
+\contentsline {subsection}{\numberline {5.2}Cell phones}{18}
+\contentsline {subsection}{\numberline {5.3}Cables for the cell phones}{18}
+\contentsline {subsection}{\numberline {5.4}Server}{18}
+\contentsline {section}{\numberline {6}Communication protocol}{19}
+\contentsline {subsection}{\numberline {6.1}Communication between the handler and controller}{19}
+\contentsline {subsection}{\numberline {6.2}Verification of the protocol}{20}
+\contentsline {section}{\numberline {7}Security and safety of the system}{23}
+\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{23}
+\contentsline {subsection}{\numberline {7.2}Security on the web site}{24}
+\contentsline {section}{\numberline {8}Web page}{28}
+\contentsline {subsection}{\numberline {8.1}Communication between the web page and the test software}{28}
+\contentsline {subsection}{\numberline {8.2}Results on the web page}{28}
+\contentsline {section}{\numberline {9}How to use and start the system}{30}
+\contentsline {subsection}{\numberline {9.1}Required libraries}{30}
+\contentsline {subsection}{\numberline {9.2}Configuring hardware}{30}
+\contentsline {section}{\numberline {10}Conclusion}{31}