From b48d6acfecfc5af7ccac4bc7dca73954b5726f49 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Henrik=20Tj=C3=A4der?= <henrik@tjaders.com> Date: Thu, 22 Dec 2016 21:23:15 +0100 Subject: [PATCH] Fixed very odd formatting due to huge picture and referenced LAMP --- implementation/ethernet-lidar.tex | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/implementation/ethernet-lidar.tex b/implementation/ethernet-lidar.tex index 69abbc9..45f714b 100644 --- a/implementation/ethernet-lidar.tex +++ b/implementation/ethernet-lidar.tex @@ -1,3 +1,4 @@ +\newpage \subsection{Ethernet} \label{sec:ethernet} \subsectionauthor{Author: Henrik Tjäder\\Reviewer: Fredrik Grönlund} @@ -108,5 +109,5 @@ This will be great for controlling the amount of data sent over the UWB radio li The standard setting sends $2 \cdot 1474 + 543 = 3491$ bytes of data (including headers). The \texttt{UWB} maximum \texttt{MTU} is \texttt{127 bytes}. Thus the UWB would have to transmit at least 28 frames just for the LIDAR. Then there is the metadata such as the stepper motor angle, the sonar data etc. -This is where the \texttt{LAMP} protocol comes into play. +This is where the \texttt{LAMP}~\ref{sec:LAMP} protocol comes into play. -- GitLab