From 979e33c3ae52782c046aedcebfa07a3f781e7644 Mon Sep 17 00:00:00 2001
From: Refik Hadzialic
Date: Sun, 9 Oct 2011 19:19:00 +0200
Subject: Writing report!

---
 notFinishedCode/Report/test.tex | 55 ++++++++++++++++++++++++++++++++---------
 1 file changed, 44 insertions(+), 11 deletions(-)

(limited to 'notFinishedCode/Report/test.tex')

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
 
-- 
cgit v1.2.3-55-g7522

