From aca2ae54e5ab124da622f1a0192e3c41f221c7ea Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Bj=C3=B6rk?= <ddbjork@gmail.com>
Date: Wed, 21 Dec 2016 17:40:42 +0100
Subject: [PATCH] Main: implementation/imu.tex added; IMU: picture moved to
implementation; text written impl/IMU
---
components/imu.tex | 8 --------
implementation/imu.tex | 13 +++++++++++++
main.tex | 1 +
3 files changed, 14 insertions(+), 8 deletions(-)
create mode 100644 implementation/imu.tex
diff --git a/components/imu.tex b/components/imu.tex
index 8f9fcdb..75f4955 100644
--- a/components/imu.tex
+++ b/components/imu.tex
@@ -2,11 +2,3 @@
To track the movement of the copter in flight, a stable IMU with minimal swing effect has to be used. There are several low cost IMU's available on the market, similar to the one in the flight controller. While these are great for tracking instantaneous movement, they are not good at tracking movement over time. Due to noise and swinging of the gyro while accelerating in any direction, the tracking will be skewed while moving up and down the cave. This mostly results in incorrect or unreliable scanning data.
Xsens Technologies are well known in the industry for producing stable and accurate IMU's. Their product series \href{https://www.xsens.com/products/mti-1-series/}{MTi 1} features all the specifications needed for the copter and was chosen as the primary IMU for the project.
-
-
-
- \begin{figure}[H]
- \centering
- \includegraphics[width=0.5\textwidth]{flowcharts/IMU2}
- \caption{IMU communication flowchart}
- \end{figure}
diff --git a/implementation/imu.tex b/implementation/imu.tex
new file mode 100644
index 0000000..1954ddc
--- /dev/null
+++ b/implementation/imu.tex
@@ -0,0 +1,13 @@
+\subsection{IMU}
+ Upon initialization of the \texttt{IMU} code, a request to go to configuration mode is sent to the MTi. The MTi is now prepared to be configured. \texttt{IMU} then transmit the configuration data, which enables the output of Euler Angles and Free Acceleration data at 100Hz.
+
+ See Figure~\ref{fig:imuflowchart} for a visual representation of the communication flow. \texttt{IMU} first transmits a request of configuration mode, waits for a confirmation response, and then continues to transmit configuration data. When the configuration is complete, a request of measurement mode is sent to the MTi. The MTi will now continuously transmit data at the configured rate.
+
+ \begin{figure}[H]
+ \centering
+ \includegraphics[width=0.5\textwidth]{flowcharts/IMU2}
+ \caption{\texttt{IMU} communication flowchart}
+ \label{fig:imuflowchart}
+ \end{figure}
+
+ The data received \texttt{8bits} at a time. Each data point transmitted contains \texttt{32bits}, formatted as a standard \texttt{IEEE 754 float}. The data is shifted into a temporary \texttt{32bit unsigned int} and then a \texttt{memcopy} is executed from the \texttt{int} to a \texttt{float}. The data points are then sent over to \texttt{MSP} and stored.
\ No newline at end of file
diff --git a/main.tex b/main.tex
index 9cbf642..d787f32 100644
--- a/main.tex
+++ b/main.tex
@@ -100,6 +100,7 @@
\newpage
\section{Implementation}
\input{./implementation/workflow.tex}
+ \input{./implementation/imu.tex}
\input{./implementation/spi-uwb.tex}
\input{./implementation/sonar.tex}
\input{./implementation/ppm.tex}
--
GitLab