fp dev

docs/Project Development.md

@@ -16,25 +16,26 @@ This part of the course was longer for me than a couple of weeks. I managed to f
 **Demand- vs supply-side time management** - Generally I used this for the last 2-3 weeks before the final project submission deadline.  
 **Spiral development, DevOps** - This is my favourite. I have started using this in my design practice and various other aspects of life.  
 **Serial vs parallel tasks** - I do both depending on the task, the time and the surrounding contexts.  
-**System integration** - getting better and better at this with time, documentation this aspect is very difficult because of non compartmentalisation.  
+**System integration** - getting better and better at this with time, documenting this is very difficult because of non compartmentalisation.  
 **Finish quality** - I believe in using materials in an honest way to hero their intrinsic properties and not hide them under aesthetic finishes. This makes the underlying parts neat and organised automatically.   
 
 2. Tracking progress
 ---
-**What tasks have been completed, and what tasks remain?**
-I kept a record of this by making a to-do list every week in my notebook and then assigning time for each task.
-Here are some pictures of my to-dos:
-![]()
-![]()
+**What tasks have been completed, and what tasks remain?**  
+I kept a record of this by making a to-do list every week in my notebook and then assigning time for each task in my calendar. Here are some pictures of my to-dos:
+![to-do](./images/final-project/timemanagement.jpg)   
+![calendar](docs/images/final-project/calendar.jpg)   
 
-**What's working? What's not?**
-The OLED screen I borrowed from the lab, stopped working after I tried it with an Arduino Uno. I'm not sure what was wrong, but I checked every connection with a multimeter. I tried an [i2c_scanner](./images/final-project/i2c_scanner.zip) but it still did not detect the device. I also tried it with a different programming board, and a I2C LCD screen with the same board. But after testing each connecting part, something in the OLED did not work. So finally, I got a new one.
+**What's working? What's not?**  
+The OLED screen I borrowed from the lab, stopped working after I tried it with an Arduino Uno. I'm not sure what was wrong, but I checked every connection with a multimeter. I tried an [I2C scanner detector](./images/final-project/i2c_scanner.zip) but it still did not detect the device. I also tried it with a different programming board, and a I2C LCD screen with the same board. But after testing each connecting part, something in the OLED did not work. So finally, I got a new one.  
 
 The laser cutter I used at the Lab - a Universal Laser system, had a different kerf in the x-axis and the y-axis. I tried many different combinations of settings and materials. But still could not figure out how to fix this. Eventually I offset my tongue and groove joints different in X- and Y- directions.  
+![different kerfs](./images/final-project/xykerfs.jpg)  
 
-I designed and made my PCB using an ATtiny44 microcontroller. Early on I figured that all the different libraries I would need to work the DHT11, the OLED would not fit in the 4k storage space. So I desoldered and used an ATtiny84, so that nothing would change but the microcontroller. Eventually I discovered the tiny libraries for OLED and DHT - optimal versions of the full libraries and turned out the code used only 4136 bytes of storage space.  
+I designed and made my PCB using an ATtiny44 microcontroller. Early on I figured that all the different libraries I would need to work the DHT11 and the OLED would not fit in the 4k storage space. So I desoldered the 44 and used an ATtiny84, so that nothing would change but the microcontroller. Eventually I discovered the tiny libraries for OLED and DHT - optimal versions of the full libraries and turned out the code used only 4136 bytes of storage space.  
 
-I made the first layout of the PCB trying to make it compact as possible by keeping parts close together and traces more optimised on space. Eventually, I changed the layout of the header pins that connect to all different input/ out puts and matched them to their physical location on the machine. This resulted in a much bigger PCB but a very neat layout of all the wiring. I planned it such that the wiring would neatly stretch on the side of the machine, but Neil suggested usng a cable manager instead.  
+I made the first layout of the PCB trying to make it as compact as possible by keeping parts close together and traces more optimised on space. Eventually, I changed the layout of the header pins that connect to all different input/ out puts and matched them to their physical location on the machine. This resulted in a much bigger PCB but a very neat layout of all the wiring. I planned it such that the wiring would neatly stretch on the side of the machine, but Neil suggested using a cable manager instead.  
+![early layout](./images/final-project/early-final.jpg)  
 
 I also wanted to add a mobile application to control the machine instead of the physical regulators and switches as the last spiral development cycle including a wifi module.  
 
@@ -182,12 +183,12 @@ Connecting all inputs and outputs
 
 ####Soldering components
 After making a 'shopping list' I gathered all components. Most of them were available from the Lab (FabLAb UAE).  
-![shopping list]()   
+![shopping list](./images/final-project/shopping-list.jpg)   
 As good standard practice, I soldered all components from left to right and top to bottom. Starting with the microcontroller, then smaller components like resistors, capacitors, then the larger mosfets and DC-DC voltage regulator and all the header pins in the end.
 ![soldering components](./images/final-project/soldering.gif)   
 
 
-####Testing board
+####Testing board  
 I was missing a diode. Since this wasn't in the lab, I used a TH component, cut legs and soldered it directly onto the copper tracks. It was a little delicate, but it worked. I had to make sure it was connected in reverse to save the DC outputs from burning.
 ![TH diode](./images/final-project/diode.jpg)   
 
@@ -241,20 +242,3 @@ https://app.ultralibrarian.com/content/help/index.htm?converting-ultra-librarian
 4. Important and interesting links
 ---
 [Project Development class notes](http://academy.cba.mit.edu/classes/project_development/index.html) + [video](https://vimeo.com/558297880)  
-
- </p><br /><br /><br /><br /><br /><br /><br /><br />
-<p><br><br><a href=”https://skunkology.com/how-does-hydroponics-work-infographics/” target=”_blank”><img src=”https://skunkology.com/wp-content/uploads/2017/10/How-does-hydroponics-work.jpg” alt=”How does hydroponics work? – Infographics” border=”0″ width=”550″ /></a><br><span style=”font-size: 14px;”>(via <a href=”https://www.skunkology.com/”>Skunkology.com</a>).</span><br><br><br></p><br /><br /><br /><br /><br /><br /><br /><br />
-<p>
-
-Prepare a summary slide and a one minute video showing its
-   conception, construction, and operation
-Your project should incorporate 2D and 3D design,
-   additive and subtractive fabrication processes,
-   electronics design and production,
-   embedded microcontroller interfacing and programming,
-   system integration and packaging
-Where possible, you should make rather than buy
-   the parts of your project
-Projects can be separate or joint, but need to show individual
-   mastery of the skills, and be independently operable
-Present your final project, weekly and group assignments, and documentation