Merge branch 'master' of gitlab.henriktjader.com:D7039E-E7025E/conexreport

chapters/systemDesign.tex

-
+	\subsection{Code of Conduct}
+		The code follows a simple code of conduct. This generally helps avoid variable naming collisions and other issues which may result in undefined behavior.
 		
 	\subsection{Static Design}
 		\subsubsection{Class Diagram}
@@ -6,11 +7,12 @@
 				\centering
 				\includegraphics[width=\textwidth]{Pictures/uml}
 			\end{figure}
+		
 		\subsubsection{Module Diagram}
 			\begin{figure}[H]
 				\centering
-                \includegraphics[width=\textwidth]{Pictures/componentchart_2}
 				\caption{System module diagram}
+				\includegraphics[width=\textwidth]{Pictures/componentchart_2}
 			\end{figure}
 
 	\subsection{Dynamic Design}

implementation/flightcontroller_imp.tex

@@ -18,7 +18,9 @@ To be able to do this we need to interact with the flight controller from our MC
 
 The flight controller do have support for four different communication protocols.
 It can take PWM inputs, where one PWM controls one channel.
+%It has
 It have PPM support, which is quite the same as a PWM but it has support for 8 PWM signals on one line.
+%does?
 It do support sBUS, which is some sort of secure serial protocol with inverted signals.
 The last protocol it supports is called MSP (MultiWii Serial Protocol), which also is a serial protocol.
 Our first thought was that we wanted to implement both the MSP and PPM protocols to control the copter.