Week 5 stuff

IDMNYU · Oct 4, 2024 · de5cb10 · de5cb10
1 parent 0f7ae60
commit de5cb10
Show file tree

Hide file tree

Showing 3 changed files with 35 additions and 41 deletions.
diff --git a/schedule.md b/schedule.md
@@ -26,58 +26,55 @@
 * analog output
 * [Midterm intro](midterm.md)
 
-# [Week 5 - Fri October 4]()
+# [Week 5 - Fri October 4](week5/main.md)
 * Presentations!
 * discussion of reading
 * Show your work
 * silly scopes
 * servos and tone
 
-# [Week 6 - Fri October 11]()
+# Week 6 - Fri October 11
 * Field Trip to Volvox Labs
 
-# [Week 7 - Fri October 18]()
+# Week 7 - Fri October 18
 * Serial Communication
 * Midterm Presentations!
 * Assignments
   * Take home quiz
   * Observation Project.
 
-# [Week 8 - Fri October 25]()
+# Week 8 - Fri October 25
 * Presentations!
 * Serial examples
 * BLE and internal sensors
 * Assignment for 11/1
   * Create an application in the langiage of your choice that communicates with your microcontroller. Post a video of this on your blog. What are you making?
 
-# [Week 9 - Fri November 1]()
+# Week 9 - Fri November 1
 * Presentations!
 * Serial communication results
 * Lots of LEDs
-* VOTE
+* Vote if you can
 
-# [Week 10 - Fri November 8]()
+# Week 10 - Fri November 8
 * presentations
 * Motors and things that move
 
-# [Week 11 - Fri November 15]()
-* machine learning on the BLE33
-* [Final project proposals]() - Come up with a proposal for what you would like to do for a final project. 
+# Week 11 - Fri November 15
+* What is a BOM?
+* Final project proposals - Come up with a proposal for what you would like to do for a final project. 
+* battery power
+* network connections
 
 # Week 12 - Fri November 22 
-* [Final project pitches]()
-
-# Week 13 - Friday December 6
-* What is a BOM?
+* Final project pitches
 * SD cards
   * datalogger
   * reading from files
-* battery power
-* [network connections]()
-* final project one on one meetings
-* [BOM due]()
-* final project workshop
-* [Functional prototype of project due]()
+
+# Week 13 - Friday December 6
+* BOM due
+* Functional prototype of project due
 
 # Week 14 - Wednesday December 11
-* [Final project presentations and documentation due]()
+* Final project presentations and documentation due
diff --git a/week5/main.md b/week5/main.md
@@ -1,19 +1,16 @@
-# Week 5 - Monday October 2 & Wed October 4
-## Monday
-* Presentation by Lianna & Riley
-* how bout them switches?
-* analog input 
-* [midterm intro](../midterm.md)
-* Readings for Wed - 
-  * [Notes on analog input and output](week5.md)
-  * [Phsyical Computing's Greatest Hits and Misses](https://www.tigoe.com/blog/category/physicalcomputing/176/)
-
-## Wednesday
-* [analog output (PWM an LED)](week5.md)
-* [servo motors & libraries](servos_and_tone.md)
-* [tone()](servos_and_tone.md)
-* Homework -
-  * Read -  [A Taxonomy of Tangible User interfaces](http://courses.ischool.berkeley.edu/i262/f13/readings_pdf/taxonomy.pdf)
-  * [All about LEDs](https://learn.sparkfun.com/tutorials/light-emitting-diodes-leds/all)
-  * Build a love machine that identifies how compatible two people are with the microcontroller. Use analog sensors for this. Work in pairs. Document this in your journal and bring it to class.
-  * Write a short decription of your midterm idea. Draw a sketch of what the system will be, think about how someone will interact with it. Be prepared to discuss your proposal next week in class. 
+# Week 5 - Friday October 4
+* Presentation by Marco & Kimmy
+* Show your work
+* discussion of TUI reading
+* Midterm idea discussion
+* [servos and tone](servos_and_tone.md)
+* oscilliscopes and other time based probes
+  * Reading [How to use a digital oscilloscope](https://learn.sparkfun.com/tutorials/how-to-use-an-oscilloscope/all)
+* _Homework_ -
+  * Read 
+    * [A Taxonomy of Tangible User interfaces](http://courses.ischool.berkeley.edu/i262/f13/readings_pdf/taxonomy.pdf)
+  * Make 
+     * Work on your midterm, due in class October 18
+  * Write 
+     * short decription of your midterm project. Each member fo the group needs to write their own summary. This should include what you planned to do, what you actually made (these are not always the same!!), if you hit a wall anywhere in your capacity to make something, how you might expand on the work given more time and respurces, and what you would do differently if you started over.
+  * optional videos to watch - [servos and libraries](https://www.youtube.com/watch?v=nETu_RFHLUc&list=PLnkvii1uWBvGVXOz4owDTtIItr07wVluC)
diff --git a/week5/servos_and_tone.md b/week5/servos_and_tone.md
@@ -80,4 +80,4 @@ void loop() {
   delay(15);                           // waits for the servo to get there
 }
 ```
-One thing to note about servos is that their wire color can vary. If you have a servo that has a black and red cable, you can safely assume red is power, black is ground, and the third wire is your signal. If you have one that's orange, red brown, I've found this is generally the proper wiring : red is 5v, brown is ground, and orange is the signal. If you have something different, search for the model number of the servo online, or look up something like "servo wires " + the colors of the wires.
+One thing to note about servos is that their wire color can vary. If you have a servo that has a black and red cable, you can safely assume red is power, black is ground, and the third wire is your signal. If you have one that's orange, red brown, I've found that, generally, the wiring is : red = 5v, brown = ground, and orange = signal. If you have something different, search for the model number of the servo online, or look up something like "servo wires " + the colors of the wires.