diff --git a/docs/3D Scanning and Printing.md b/docs/3D Scanning and Printing.md
index af4320a210bf42854f07c2f58821c2c430c8d740..7deb5e8ddf94a45da5cba14272aa50becfbd6239 100644
--- a/docs/3D Scanning and Printing.md
+++ b/docs/3D Scanning and Printing.md
@@ -18,9 +18,8 @@ This week I made some 3d printed tools and 3d scanned using photogrammetry.
---
I used [these files on thingiverse](https://www.thingiverse.com/thing:533472) to test design rules of the Ultimaker 3 I used in the lab.
These test geometries are designed to evaluate specific performance characteristics and motion systems in common low-cost FDM/FFF machines. Make Magazine's third annual 3D Printing Shootout was conducted using these files, created by Andreas Bastian to benchmark performance of desktop 3D printers.
-How to evaluate the test geometries at: [link](http://wp.me/p22K2I-1TOt)
-There are 7 individual files that help test:
+These tests individually help with testing:
1. Dimensional Accuracy
2. Bridging Performance
3. Overhang Performance
@@ -29,7 +28,22 @@ There are 7 individual files that help test:
6. XY Resonance
7. Z Resonance
-I will finish this part when I am back in the lab.
+I use Cura to make the gcode. They are supposed to be evaluated at default at default 'normal' settings in PLA with a 0.4mm nozzle.
+Layer Height: 0.15
+Infill: 18%
+Adhesion On
+Support Off
+
+
+
+I used an Ultimaker 2+ to perform the tests (Fablab SP).
+
+
+There is a nice evaluation system described in [How to evaluate the test geometries](https://makezine.com/2014/11/07/how-to-evaluate-the-2015-make-3dp-test-probes/). I used this to score the printer I was using. This is the result.
+
+
+Here are all the tests overall:
+
2. Designing for 3D printing
---
diff --git a/docs/Electronics Design.md b/docs/Electronics Design.md
index d21d32b72cdccd8b0520007b213e7f4197b110b1..cf8fb990c8b0e3542bc865a15375b8e07e0a4b28 100644
--- a/docs/Electronics Design.md
+++ b/docs/Electronics Design.md
@@ -121,12 +121,17 @@ But this time I used [Mods](http://mods.cba.mit.edu/) instead of Fabmodules. Her
+#### At the lab
-I could not fabricate this board because did not have access to a lab.
+I started to mill the board, solder the components by following the workflow described in [Electronics Production week](./Electronics Production.md).
-#### At the lab
+On the first attempt, the I found that the edges of outline were too close to the traces, and they were fragile.
+
+
+After offsetting the outline farther away, and milling the board again, the board with componants looks like this:
+
-So steps remaining for this week - mill the board, solder the components, test.
+Programming the board is done during the [Embedded Programming](./Embedded Programming.md) week.
#### References
diff --git a/docs/Input Devices.md b/docs/Input Devices.md
index c64f4ab7213ef5076af116dc7802f2225ae3c7a8..b5c65101ccbcf8942c5335d020d13cb52e2820f2 100644
--- a/docs/Input Devices.md
+++ b/docs/Input Devices.md
@@ -15,28 +15,28 @@ When I have access to a lab, I will make a microcontroller board with a colour s
---
0. Inputs using Arduino board (no lab access)
----
- I wanted to start with a simple project to get the basics right and understand fundamentals of using inputs with a microcontroller board. Using an Arduino Uno board with it's documentation was very basic. So I did this before designing my own board.
- For reference, I used the [Arduino Project 3](https://create.arduino.cc/projecthub/godboi123/love-o-meter-bda552) as it used the temperature sensor.
- I started by collecting all the components.
+-
+I wanted to start with a simple project to get the basics right and understand fundamentals of using inputs with microcontroller board. Using an Arduino Uno board with it's documentation was very basic. So I did this befordesigning my own board.
+For reference, I used the [Arduino Project 3](https://create.arduino.cc/projecthub/godboi123/love-o-meter-bda552) ait used the temperature sensor.
+I started by collecting all the components.
- 
+
- I used this schematic to connect everything.
- 
+I used this schematic to connect everything.
+
- The circuit setup was fairly easy. This is how it looks.
- 
+The circuit setup was fairly easy. This is how it looks.
+
- At first, all lights were continuously on. I checked the serial monitor and saw that the temperature was around 26 degrees without touching. So I adjusted the baseline temperature to 25 in the sketch. After some trial and error, I adjusted the sketch so that on touching it lightly for about 5 seconds, the second led lit up and on holding it tight for some seconds the third led lit up. The serial monitor indicated temperature range from 26-32 degrees.
- So an increment of 2-4-6 degrees worked out perfectly.
- 
+At first, all lights were continuously on. I checked the serial monitor and saw that the temperature was around 2degrees without touching. So I adjusted the baseline temperature to 25 in the sketch. After some trial and error, adjusted the sketch so that on touching it lightly for about 5 seconds, the second led lit up and on holding it tighfor some seconds the third led lit up. The serial monitor indicated temperature range from 26-32 degrees.
+So an increment of 2-4-6 degrees worked out perfectly.
+
- This is it in action:
- 
+This is it in action:
+
- The code was fairly simple as well. You can find it here - [Sketch](./images/input/3leds.zip)
- Understanding the basics:
+The code was fairly simple as well. You can find it here - [Sketch](./images/input/3leds.zip)
+Understanding the basics:
```
// defining constants
const int SensorPin = A1; // analog template input from temp sensor
@@ -95,12 +95,19 @@ When I have access to a lab, I will make a microcontroller board with a colour s
1. Probing an input device's analog levels and digital signals
---
+
2. Designing a micro-controller board to read input
---
For this I want to try measuring light color using a RGB colour sensor.
-[ATtiny412 Datasheet](https://ww1.microchip.com/downloads/en/DeviceDoc/ATtiny212-214-412-414-416-DataSheet-DS40002287A.pdf)
-[VEML6040](https://www.vishay.com/docs/84276/veml6040.pdf)
+First task is to select a microcontroller for the selected sensor.
+By looking at the datasheet and pinout of the sensor VEML6040, it needs only SDA and SCL to be connected by I2C communication protocol. The SDA needs a pull-up resistor.
+
+The microcontroller itself needs to Tx, RX to be able to connect through UPDI to a programmer.
+
+I choose the Attiny412 because...
+[ATtiny412 Datasheet](https://ww1.microchip.com/downloads/en/DeviceDoc/ATtiny212-214-412-414-416-DataSheet-DS40002287A.pdf)
+[VEML6040](https://www.vishay.com/docs/84276/veml6040.pdf) - RGBW Color Sensor with I2C Interface
Downloaded the footprint from [Here](https://www.snapeda.com/parts/VEML6040A3OG/Vishay%20Semiconductor%20Opto%20Division/view-part/702426/?company=-&welcome=home)
Installed the symbol and footprint on KiCAD using [this guide](https://www.snapeda.com/about/import/#)
@@ -139,5 +146,5 @@ Installed the symbol and footprint on KiCAD using [this guide](https://www.snape
8. Important and Interesting Links
---
-https://en.wikipedia.org/wiki/List_of_sensors
-https://hackmd.io/RzTkiKoXTbqeQOn4Nz_zAw?view#INPUTS
+[List of sensors Wiki article](https://en.wikipedia.org/wiki/List_of_sensors)
+[Victor's notes - INPUTS](https://hackmd.io/RzTkiKoXTbqeQOn4Nz_zAw?view#INPUTS)
diff --git a/docs/images/ed/ss/board.jpg b/docs/images/ed/ss/board.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be2fa12f0760a492717fe95b3324f61c442543c7
Binary files /dev/null and b/docs/images/ed/ss/board.jpg differ
diff --git a/docs/images/ed/ss/board1.jpg b/docs/images/ed/ss/board1.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f70ae5278e52a0fef14560515e42e15178fac32
Binary files /dev/null and b/docs/images/ed/ss/board1.jpg differ
diff --git a/docs/images/ed/ss/cura.jpg b/docs/images/ed/ss/cura.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c741ea5261ee3b60075b0d59c61d907214b9410f
Binary files /dev/null and b/docs/images/ed/ss/cura.jpg differ
diff --git a/docs/images/ed/ss/evaluation.jpg b/docs/images/ed/ss/evaluation.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d0d423fe3d10f34c0699af71bf2902e18bafb80b
Binary files /dev/null and b/docs/images/ed/ss/evaluation.jpg differ
diff --git a/docs/images/ed/ss/tests.jpg b/docs/images/ed/ss/tests.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..48966e0298e36d1f096aff43d08d5a47a98751a7
Binary files /dev/null and b/docs/images/ed/ss/tests.jpg differ
diff --git a/docs/images/ed/ss/u2.jpg b/docs/images/ed/ss/u2.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..717c5395c09c90c93c175513aeb137811b8d3dab
Binary files /dev/null and b/docs/images/ed/ss/u2.jpg differ
diff --git a/docs/images/input/t412+VEML6040-schematic.pdf b/docs/images/input/t412+VEML6040-schematic.pdf
new file mode 100644
index 0000000000000000000000000000000000000000..8e3f73c2d39246a7f5e7cf93b59931c650580717
Binary files /dev/null and b/docs/images/input/t412+VEML6040-schematic.pdf differ