X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=appendix-protocol.tex;h=00d2ced8fa678eb633a120f02d21858846f6341e;hb=b855f7f75705291002f50f99eab11d4f450cef48;hp=39365888d144f3b99654762a4f76da7a99a949d5;hpb=76254fbf2941fa0b5a02ab3a98104cad56959218;p=msc-thesis1617.git

diff --git a/appendix-protocol.tex b/appendix-protocol.tex
index 3936588..00d2ced 100644
--- a/appendix-protocol.tex
+++ b/appendix-protocol.tex
@@ -4,14 +4,38 @@ easier. Message exchanges have a \emph{Request} and \emph{Response} header.
 The \emph{Request} header means that the server is sending to the client. The
 \emph{Response} header means that the client is sending to the server. In some
 cases either the \emph{Request} or \emph{Response} is empty. This means that
-the message is not acknowledged or responded upon.
+the message is not acknowledged or responded upon. Multibyte values are
+interpreted as \gls{MSB} first integers.
 
 \section{Handshake}
-\todo{Handshake, here the client tells the server what they can do}
+\begin{table}[H]
+	\centering
+	\begin{subfigure}[t]{.48\textwidth}
+		\begin{tabular}{ll}
+			\toprule
+			\multicolumn{2}{c}{Request}\\
+			byte & value\\
+			\midrule
+			1 & \texttt{'c'}\\
+			\midrule\midrule
+			\multicolumn{2}{c}{Response}\\
+			byte & value\\
+			\midrule
+			1 & \texttt{'c'}\\
+			2 & Peripheral bitmask\\
+			3,4 & Bytes of memory\\
+			5,6 & Size of the stack\\
+			7 & Number of analog pins\\
+			8 & Number of digital pins\\
+			\bottomrule
+		\end{tabular}
+		\caption{Send a device specification}
+	\end{subfigure}
+\end{table}
 
 \newpage
 \section{mTasks}
-\begin{table}[!ht]
+\begin{table}[H]
 	\centering
 	\begin{subfigure}[t]{.48\textwidth}
 		\begin{tabular}{ll}
@@ -56,7 +80,7 @@ the message is not acknowledged or responded upon.
 \end{table}
 
 \section{SDSs}
-\begin{table}[!ht]
+\begin{table}[H]
 	\centering
 	\begin{subfigure}[t]{.2\textwidth}
 		\begin{tabular}{ll}