From c91bdfb9f527e43249a34d50ccb41c96cb4282df Mon Sep 17 00:00:00 2001
From: Kamal Alkahwati <kamal.alkahwati@gmail.com>
Date: Fri, 30 Sep 2016 15:57:15 +0200
Subject: [PATCH] written statusreport

---
 statusReport.tex | 24 ++++++++++++++----------
 1 file changed, 14 insertions(+), 10 deletions(-)

diff --git a/statusReport.tex b/statusReport.tex
index a37f392..f30d0cd 100644
--- a/statusReport.tex
+++ b/statusReport.tex
@@ -6,22 +6,26 @@
 \include{latexoptions}
 \begin{document}
 \maketitle
-\section{Week 37 - status}
+\section{Week 39 - status}
 	\begin{itemize}
 	\item  Software \newline
-		Software progress is a bit behind schedule, we have experienced some issues
-		setting up the F767ZINucleo properly. This will be resolved until
-		Monday the 19th, including peripheral drivers.
+		Software progress is still a bit behind schedule. We have set up peripherals using STMs HAL (Hardware abstraction layer). Using multiple sensors (sonars with timers, IR with ADC) is a bit harder than we expected. 
+			
+			Sonars should be done this week according to the gantt-schedule but will be finished next week.\newline
+			The IR sensors will be 6 instead of 12 since its not worth the hassle with multiple ADCs.\newline
+			SPI development is standing quite still, to fix this Fredrik is going to help Emil setting up the peripheral properly.\newline
+			Ethernet and UART development is also a bit behind schedule but will be finished next week.\newline 
+
+			In whole, the software development is almost 1 week behind schedule.
 
 
 	\item Hardware \newline
-		Hardware progress is proceeding as planned. A shield-chip for the Nucleo board
-			is in design phase. This will make it easier for us to set up connections
-			to peripherals on the Nucleo.
+		Hardware development is also a bit behind schedule due to late arriving parts. The copter parts arrived on Friday, and according to our gantt it should have been built by that day.
+			As a result, the hardware development is almost 1 week behind schedule.
+
 	\item Group \newline
-		The group in whole has been doing research on git workflows, reading documents
-			(F767ZI, peripheral protocols and components). We have also written on
-			the report.
+		We have restructured the whole UML diagram and put Authors/reviewers on chapters in the report. 
+		
 
 	\end{itemize}
 \end{document}
-- 
GitLab