Correct thesis report
Signed-off-by: Severin Kaderli <severin@kaderli.dev>
This commit is contained in:
parent
2f8b0b524a
commit
1862068f09
10 changed files with 70 additions and 50 deletions
|
@ -1,9 +1,9 @@
|
|||
\chapter{Solution}
|
||||
The solution consists of two separate applications: a website used for transmitting data and a smartphone application used for receiving data. Transmission between the two application happens using a simple protocol on top of signals made using magnetic induction. I call the system MagSend.
|
||||
The solution consists of two separate applications: a website used for transmitting data, and a smartphone application used for receiving data. Transmission between the two application happens by a simple protocol on top of signals that use magnetic induction. I call the system MagSend.
|
||||
|
||||
\section{Protocol}
|
||||
\label{section:protocol}
|
||||
The following section describes how the MagSend protocol works. I explain the entire protocol first by explaining how the data gets encoded on the sender site, then the transmission and finally how the data is received.
|
||||
The following section describes how the MagSend protocol works. First I explain how the data gets encoded on the sender site, then the transmission, and finally how the data is received.
|
||||
|
||||
\subsection{Sending}
|
||||
This section explains how a user-provided message gets encoded and finally transmitted using \gls{mi}.
|
||||
|
@ -11,7 +11,7 @@ This section explains how a user-provided message gets encoded and finally trans
|
|||
Data over MagSend gets sent in a packet. For the structure of the packet I tried to follow other packet formats that already exist. Most of the structure is similiar to the structure of a LoRa packet. \cite{LoRaPacketFormat} I choose LoRa as example as I am familiar to it was a part of my studies and as LoRa is also a protocol designed with a low data-rate in mind. The packet contains three parts.
|
||||
|
||||
\subsubsection*{Header}
|
||||
The first part of the packet is the header. The header is \SI{4}{\bit} long and contains the length of the payload in bytes. The length is mainly used, to be able to detect the end of the payload.
|
||||
The first part of the packet is the header. The header is \SI{4}{\bit} long and contains the length of the payload in bytes. The length is mainly used to detect the end of the payload.
|
||||
|
||||
\subsubsection*{Payload}
|
||||
Next is the actual payload. As the length of the payload is specified in the header, the payload is limited to a size of $2^4$ bytes. While the contents of the payload can be any bit stream, the sender and receiver should assume that the bit stream is interpreted as ASCII text.
|
||||
|
@ -27,7 +27,7 @@ The transmission works over magnetic induction. By putting a load on a CPU the r
|
|||
|
||||
To indicate the start of a message in the signal, a preamble is used. The preamble used in this protocol is 3 high signals, followed by 3 low signals, followed by 3 high signals. The duration of one signal in the preamble is 1 second. That means the entire preamble takes 9 seconds.
|
||||
|
||||
After the preamble that contents of the manchester encoded packet is sent.
|
||||
After the preambl, the contents of the manchester encoded packet is sent.
|
||||
|
||||
\begin{figure}[H]
|
||||
\begin{bytefield}[bitwidth=.05\linewidth, bitheight=11mm]{4}
|
||||
|
@ -78,9 +78,9 @@ process.
|
|||
\caption{Website - Home}
|
||||
\end{figure}
|
||||
|
||||
When the calibration process is started, a message is displayed so it's clear
|
||||
that we are in the calibration process. What happens technically is the website
|
||||
will just put a full load on the CPU for the duration of the calibration. The
|
||||
When the calibration process is started, a message is displayed, so it's clear
|
||||
that we are in the calibration process. What happens during calibration is, that the website
|
||||
puts a full load on the CPU for the duration of the calibration. The
|
||||
actual calibration process happens in the smartphone application.
|
||||
|
||||
\begin{figure}[H]
|
||||
|
@ -90,10 +90,9 @@ actual calibration process happens in the smartphone application.
|
|||
\end{figure}
|
||||
|
||||
\newpage
|
||||
When the user presses the sending button, the text will be sent by website
|
||||
When the user presses the sending button, the text will be sent by the website
|
||||
using the protocol described in \autoref{section:protocol}, by putting stress
|
||||
on the CPU to generate a signal. While sending there is a message which
|
||||
indicates that there is currently a send in process.
|
||||
on the CPU to generate a signal. A message is displayed that indicates that a sending process is ongoing.
|
||||
|
||||
\begin{figure}[H]
|
||||
\centering
|
||||
|
@ -114,7 +113,7 @@ On the homescreen you have two buttons. One button is for receiving messages and
|
|||
\end{figure}
|
||||
|
||||
\newpage
|
||||
The calibration mode is used to find the most optimal location where the user should put the smartphone on the sending device. The website will continously put a load on the CPU. The app will then show the current strength of the magnetic field. The location where the strength is the highest is the one, where you will get the best transmission results.
|
||||
The calibration mode is used to find the most optimal location where the user should put the smartphone on the sending device. The website will continously put a load on the CPU. The app will then show the current strength of the magnetic field. The location where the strength is the highest is the one where you will get the best transmission results.
|
||||
|
||||
\begin{figure}[H]
|
||||
\centering
|
||||
|
@ -123,7 +122,7 @@ The calibration mode is used to find the most optimal location where the user sh
|
|||
\end{figure}
|
||||
|
||||
\newpage
|
||||
When receiving a message, the currently received text is displayed on the screen while a loading indicator indicates that the receiving is still in process. When the receiving is finished the complete text is displayed. While receiving the user has the possibility to restart the receiving process to receive a new message.
|
||||
During the reception process, the currently received text is displayed on the screen while a loading indicator indicates that the process is still ongoing. When the process is finished, the complete text is displayed. At any time, the user has the possibility to restart the reception process for a new message.
|
||||
|
||||
\begin{figure}[H]
|
||||
\begin{minipage}{.5\textwidth}
|
||||
|
|
Reference in a new issue