Updates from October, 2011 Toggle Comment Threads | Keyboard Shortcuts

  • Yury Gitman 12:12 am on October 31, 2011 Permalink | Reply  

    For Next Class 

    Hi All,

    I’m just reviewing to make sure everyone is on the same page.

    In the next class you are coming in with you WORKING project.  You DO need blog post documenting your project.

    The working project is do next class.  The blog post can be turned in the following class.  BUT, it’s always easier to document while your project still works well and is fresh to the mind.

    The Blog Post should have:
    1) Project Name
    2) A photo of the electronics
    3) A photo of the final project
    4) A short video demonstrating it. [More in video below]
    5) The code you used.

    Regarding the video, it should:
    Be 60-90 seconds long.
    Contain the project title [either with a graphic or via voice over)
    Demonstrate the concept and function.

    This does not have to be a perfect “Pixar-quality” video. It just needs to contain the above.  It can be done very well with a careful long-take, with a voice over.
    The video should be posted on Vimeo or google and then embedded in to

    Bring to next class:

    1) The LOL Shield. We will be soldering them.

    2) A power strip if you have one. I’ll try to bring one too.

     
  • yongjaelee2011 5:25 pm on October 28, 2011 Permalink | Reply  

    PIR Motion Sensor 

    https://docs.google.com/present/view?id=0AcwFEsZiA2XlZGdmNjl4cWtfMWY2NGh4cGd4

     
  • aisencc 5:10 pm on October 28, 2011 Permalink | Reply  

    Toccata CalaBach 

    Toccata Calabaza is an interactive pumpkin design that has different functions based on three inputs. A motion sensor, when triggered plays the Toccata and Fugue in D minor. When the night falls a photoresistor triggers the light inside the pumpkin. A temperature sensor is set to change the lights to flickering orange when it gets colder outside.

    Some of the challenges I found in making this pumpkin is that the PIR sensor is too sensitive, so the the Toccata plays constantly. I will have to take off the lens, and perhaps the sound will be more accurate to movement. Another challenge is better representing the chill of the ghost with more than just an orange flicker. Some positive aspects of the project have been learning to compose with PWM, and having to do more research on motion sensing. I’m excited to learn more about music tones with PWM pins.

     
  • yongjaelee2011 4:30 pm on October 28, 2011 Permalink | Reply  

    Paper Halloween Pumpkin 

    1) Project Title:

    Paper  Halloween Pumpkin

    2) Concept:

    Based on a users distance and interaction, my pumpkin will display different colors to create different mood. Also, there will be sound to make people surprise or scared.

    First of all, yellow color will be shown. When a motion sensor detect a user, color will change to red. There will be photo sensor that will activate the multi-mouse led lights.

    Once a user shake my pumpkin, it will play a music.

    3)My Experience:

    Working with codes is not easy for me. I will have to combine different function of codes to make my pumpkin alive.

     
  • Catalina 4:30 pm on October 28, 2011 Permalink | Reply  

    Pumpkin-Sky Lamp 

    My idea is to create a pumpkin lamp.
    The lamp consist on 3 small pumpkins that interact with each other and they also respond to it’s environment using the motion sensor and the photocell.

    The one in the middle will have little holes, like the sky, with blue LED’s inside, and will light as knight rider when the photocell is activated. It’ll also have a motion sensor which will respond lighting the RGB lights that are inside the other two pumpkins, changing colors.

    The most challenging part will be to  solder everything because I’ve never done it before.
    And the most interesting and fun part so far, has been to make the photocell work and react to the changes of light intensity inside the room.

     
  • firmread 4:24 pm on October 28, 2011 Permalink | Reply  

    Boo!!! I’m not a pumpkin! 

    midterm project of : Firm Tharit Tothong
    project name : Boo!!! I’m not a pumpkin!

    This pumpkin take a character like a ghost in Mario game. (this guy )

    Basically, the idea is the pumpkin going to do something when you’re not there.
    Initial ideas now are to use proximity sensor to detect people and it hide itself if there is someone there, while it casually lit up when nobody nearby.
    Also, it make some sound this sound is refer to Ghost house theme in Mario game and the beat is an analogy of the heartbeat of Boo. So when no body is closed to it, the beat goes slow because it’s relax. And goes more upbeat if there is someone nearby.

    documentation video

     #include "pitches.h"
     int speaker = 5;
     int bulb = 6;
     int lightPin1 = 3;
     int lightPin2 = 4;
     int brightness = 0;
     int fadeAmount = 5;</code>
    
    // notes in the melody:
     int melody[] = {
     NOTE_B3, NOTE_CS4, NOTE_A3, NOTE_C4, NOTE_B3 ,NOTE_CS4, NOTE_A3, NOTE_C4};
    
    // note durations: 4 = quarter note, 8 = eighth note, etc.:
     int noteDurations[] = {
     4, 4, 4, 4,4,4,4,4 };
    
    void setup() {
     pinMode(speaker, OUTPUT);
     pinMode(bulb, OUTPUT);
     }
    
    void loop() {
     note();
     fade();
     }
    
    void note(){
     for (int thisNote = 0; thisNote < 8; thisNote++) {
    
    // modulate music speed through proximity sensor
     int tempo = map (analogRead(0),10,400,300,4000);
     int noteDuration = tempo/noteDurations[thisNote];
     tone(speaker, melody[thisNote],noteDuration);
     int pauseBetweenNotes = noteDuration * 1.30;
     delay(pauseBetweenNotes);
     // stop the tone playing:
     noTone(speaker);
     }
     }
    
    void fade(){
     int brightness = map (analogRead(1),10,250,10,255);
     analogWrite(bulb, brightness);
     }
    
    
     
  • danSelden 4:23 pm on October 28, 2011 Permalink | Reply  

    pumpkinROBOT 

    The concept was actually derived from the likes of the Google Chrome icon… a metal sphere with an “eye” in the center. The pumpkinRobot won’t do anything super amazing and at first glance will seem to only have an eye with a pulsating internal light.  However, upon its detection of someone’s physical presence, it’s light will immediately turn flashing red as panels emerge from it’s sides with flashing LEDs.  After some time the panels will recede back into the form of the pumpkin and the internal light will return to its normal state.

    2-3 Sentences about the most challenging and most interesting aspects of the project:
    This has been difficult to build… and while I have built out the circuits for my RGB LEDs (the pulsating interior) and the panel LEDs… the other mechanics have been difficult. I’ve been testing with a button switch but plan on changing the trigger to a sensor once everything works.

    The panel mechanism has been extremely challenging. At first I decided I would need servo motors to push and pull the panels into place… after talking with peers I decided a linear actuator (piston like screw pump) or a solenoid pump would be better since they operate in a single direction and would be easier to integrate into the pumpkin innards. Unfortuantely linear actuators start around $100 and the solenoid pump I picked up is too small to really do what I need it to. Thus, I am back to servo motors… and continuous ones at that, so I need to figure out how to map the range I need and find a way to engineer the push/pull mechanism. (YIKES).

    The only other trouble I ran into was with the RGB light cycle.  While the cycle works fine… breaking out of it mid-cycle to switch into a flashing red display has been difficult and I’m still troubleshooting. Even by including break statements within the cycle code, I was only able to interfere at certain points but would not be able to kill the actual loop.  I hope to resolve this soon or I’ll just include a different mechanism.

     
  • mrcansler 4:22 pm on October 28, 2011 Permalink | Reply  

    Pumpkinstein, eater of pumpkins (Noa and Aaron) 

    Pumpkinstein is a life loving pumpkin that loves to eat and receive a lot of attention.  Pumpkinstein makes happy sounds when you rub his ears, which are connected to pots and speakers.  If you walk away, this is detected by a maxsonar sensor and his eyes turn red and angry, but if you are close, they are peaceful and blue.  If you feed him candy, it interrupts a led/photo resistor circuit and his eyes blink in happiness.

    The challenges so far have been figuring out the timing on potentiometers and speakers that make up the pumpkins ears.  It’s been complicated making them both only react when touched, and not just running all the time.  The other tricky part has been taking the simpler code from all separate sensors and combining them all together to play nice.

     
  • hirumi 4:22 pm on October 28, 2011 Permalink | Reply  

    Harry Potter Pumpkin 

    1. Ze Harry Potter Pumpkin

    2. This magical pumpkin lights up and shoots spells based on how close a person is to the pumpkin. The eyes and wand of the pumpkin are LEDs and a sound recorder plays back 3 different spells.

    3. I was having a lot of issues with the PIR sensor, so I switched to the miniphoto cell. This actually ended up being a good thing, because I can assign different values based on distance instead of just one with the PIR. The RGB LEDs make it more playful and integrates emotionality to the pumpkin; the closer you get to it, the more aggressive the spells get.

    I haven’t had success with the sound recorder just yet. I’m missing the JST female connector, but with the new soddering skills we’re picking up today, I should be able to work around it. There’s also something funky going on with the wand part. It lights up, but its super dim.

     
  • mónica arias. 4:22 pm on October 28, 2011 Permalink | Reply  

    the mac-o-lantern. 

    The mac-o-lantern thinks it has a little core duo heart <3. Hence, it acts just like a computer. It doesn’t have a button to turn it on, so you just need to give it a little shake, and a white light will turn on (simulating an apple computer when it turns on). Then it has a little mouse. When you move it around, it will find the spot and connect to the internet. Then, you need to click the button on the mouse, and it will download the Halloween software. When it finishes downloading… THEN the pumpkin will light on, and it will be ready to light up the night. After it’s on, when people walk in front of it, it flickers its eyes, trying to lure them with its affordance… just like a real apple computer would do.

    This was my inspiration:

    rough sketch of the mac-o-lantern.

    I really wanted to add sound to the project, but all the instructions for the Twig Sound Recorder were so confusing. I thought sound would really add up to the concept (with the sounds of turning on, connecting to the internet, finishing downloading the software), so it was difficult bringing it down to just lights. The code in general was also a bit tricky, since there’s a lot of if’s and a lot of led’s. HOWEVER, the tricky/difficult parts are also the most interesting ones! But the best part overall was coming up with a concept that both makes sense, and makes me happy.

     
  • Jun Sik (Jason) Kim 4:21 pm on October 28, 2011 Permalink | Reply  

    Stupid Pumpkin 

    1) Project title: Stupid Pumpkin

    2) 2-3 Sentences explaining concept.

    My project is entitled Stupid Pumpkin because it is a pumpkin that people want to hit. It uses numerous LEDs using a shift register and uses blink, fade, multicolored, etc. to show its stupidness. It also has a motor that also turns according to the direction the pumpkin is hit to represent the pumpkin “seeing stars” after he gets hit. I’ve also used LEDs to show the pumpkin crying after he is it. Potentiometers are used so that people can change the pumpkin’s eye color.

    3) 2-3 Sentences on most challenging and most interesting parts of your experimentations.

    It was the first time I was using a shift register and a servo motor. I knew I wanted to use a lot of LEDs but my Arduino could only support so many output pins therefore I used the shift register to connect 8 LEDs to represent the mouth. Understanding the concept of the shift register was quite challenging. Another challenging part was working with the servo motor’s angles. I wanted to control the amount and the angle the servo motor turns and I had to work with a code that detected which numbers represented the turning of the servo motor. What is fun about my project is the servo motor turning according to which side the pumpkin is hit and that the pumpkin cries and makes a sad smiley face when it is it.

     
  • Fred Andrade 4:20 pm on October 28, 2011 Permalink | Reply  

    Haloweeeeeeeeee 

    Hi there 🙂

    My pumpkin will henceforth be known as

    Kitteh

    The concept is to explore the reactions of animals to recreate life in my pumpkin. I hope to make it blink naturally and breath steadily during its relaxed state, and make its eyes and breath very irregular when it’s startled.

    The most challenging aspect so far was to unify all four sketches into a single one. The most interesting has been to learn about randomizing numbers and how that works. I used randomizing for the blinking and the breath.

    ~Freddie

     
  • Fred Andrade 6:05 pm on October 26, 2011 Permalink | Reply  

    Fun toy worth looking at 

     

     

    http://www.gosphero.com

     
  • firmread 7:30 am on October 23, 2011 Permalink | Reply  

    This and that on carving pumpkin 

    I’ve never done this before so I did a little bit research,,,

    How to Carve a Pumpkin for Halloween
    (series of how to video)

    How to Make Jack-O-Lanterns Last Longer
    (short tip article)

    Just wanna share, so you know 🙂

     
  • danSelden 8:35 am on October 20, 2011 Permalink | Reply  

    R2D2 Pumpkin!!!! Amazing 

    Had to post this… came across it on youtube while researching sound recording things…

     
    • rachel 4:50 am on October 21, 2011 Permalink | Reply

      okay that makes america’s obsession with halloween 100x cooler!!!!!!

  • Yury Gitman 5:53 pm on October 8, 2011 Permalink | Reply
    Tags: , , cookbook, homework,   

    Arduino Cookbook Reading/Homework 

    Come to Oct 7th’s Class having done and read:

    Review: 1.1-1.5   [Read it for what you don’t know]

    Variables Introduced:  2.0-2.2

    Doing Math to Variables: 3.0-3.2

    Serial Comm Intro: Read 4.0 and don’t worry if over your head. Do pay close attention to 4.1.

    More Fun with Variables, Relational Operators: 2.17

    *Switches Intro, with Pull-Up Resistor and De-bouncing: Read 5.0 and 5.1, Do 5.2 and 5.3

    “If” and “Else If” Statements Intro: 2.12

    *”While” and “For” Loop: Pages 2.13, 2.14

    ———————————————-

    Come to Oct 14th’s Class having done and read:

    2.4:   Arrays Introduced (for Switches and LED’s)

    2.10:   Functions: Pages

    7.1:  LED’s Introduced and Reviewed

    7.6:  Making Knight Rider

    2.15-2.16:  Break and Switch Case:

    5.4:   Switches Intermediate:

    2.19, 2.21:  Logical Operators on Variables:

    Assignment:

    1)  Change LED Blink Delay based on Amount of time Button is pressed.

    2)  Make 6 Different Light Sequences with  3-4 Switches and 4 LED’s.  Use Logical Operator, Knight Rider Effect, Functions and/or Switch Cases.

    ———————————————-

    Come to 21st’s Class having done and read:

    Reading Analog Values: 5.6,

    Map Function: 5.7

    Sensor: 6.0-6.3

    LED Fading, Color, and Control: 7.0, 7.2, 7.4, 7.5, 7.6

    http://wiring.org.co/learning/basics/rgbled.html

    Assignment:

    Show 7.4 and 7.5 in Class.

     
    • hirumi 4:21 pm on October 14, 2011 Permalink | Reply

      Most useful/valuable exercises:
      I found that using the serial input to be the most useful exercise from the homework. It was gratifying to see the computer communicate with the arduino. Functions was a useful read because it made my code more modular and clean.

      Most difficult:
      Both switchTime sketches made me want to bash my head into a wall. I couldn’t get them to work to save my life. I kept getting errors even though it seemed like I had copied the examples exactly from the book. I’m not sure if there was a typo, or if there was some sort of additional code I was supposed to know to include, but regardless I couldn’t troubleshoot the issue.

    • noadol 4:24 pm on October 14, 2011 Permalink | Reply

      Most useful and valuable:

      Functions && Logical Operators on Variables.

      These two exercise really pushed my understanding of code structure
      and expand my options to control conditions.

      Most difficult and confusing:

      (5.4) Determining How Long a Switch Is Pressed:
      I could get the code text and structure, but I was confused about what it’s supposed to do or how it’s functions.. I’m not sure I got the point of this assignment, meaning I won’t be able to apply it and develop it in other projects.

      Formatting Serial Communication:
      It was very technical, a lot of new expressions I’m not sure what’s their value (e.g. ASCII, BYTE, BIN..).

    • mayaweinstein 4:24 pm on October 14, 2011 Permalink | Reply

      I found the section on breaks helpful. It’s good to know how to break a for loop without ending the function. I also found the section on RGB led’s helpful, it was a good introduction on how to use RGB led’s.
      I was really confused by the section covering the switch-case function. I understand what a function is and how it works but I did not understand what was being accomplished through the use of the switch-case. I was completely lost when it came down to the bitwise operations. I have no idea why you would be working with what looked like binary code in arduino. I’m not sure exactly what the code was trying to do or when you would actually use it.

    • Catalina Cortazar 4:25 pm on October 14, 2011 Permalink | Reply

      The codes I found more difficult and confusing were the following:

      The example blink3 on the function part. The function that needs a parameter and gives 1 return value. I couldn’t get it to work at home and also don’t understand how and when do we call the function. Do we need to call it from inside the void loop?

      Another thing that I still found confusing is the pull up button. They always start HIGH ? How do we do it to turn the light off, or maybe is there a way to change the state of the button?

      I also don’t understand what the value >>= 2; means (shift value right to places)

      Most useful or valuable

      The most useful and valuable thing I found was the use of arrays in order to declare more than one element. I also think it’s useful the logical operators and comparison, in order to give “instruction” to what and when to do something.

      Another thing I found useful is the use of break;
      specially when we have lots of information and we don’t want to use infinitive number of if, else if commands.

    • mónica arias. 4:25 pm on October 14, 2011 Permalink | Reply

      MOST HELPFUL ASSIGNMENTS:
      – Both sections regarding logical operators on variables. I had never seen it explained in so much detail, but at the same time in a concise way. They weren’t exercises per se, but it was one of the most helpful chapters. (2.19, 2.21: Logical Operators on Variables)

      MOST DIFFICULT ASSIGNMENTS:
      – 2.4: Arrays Introduced (for Switches and LED’s): The book makes a fine job explaining it, so it might be just a personal issue I have against arrays in general.
      – 2.15-2.16: Break and Switch Case… yeah. I understood the concept, BUT I still don’t feel comfortable explaining it, or doing it. But hey, isn’t experimentation key? I’m sure that if I spend more time on it, I would eventually get it.

    • dss49 4:26 pm on October 14, 2011 Permalink | Reply

      I guess I neglected some of the reading although I found a very helpful tutorial online that sort of walked me through basic input/output using buttons and LED’s. (I’ll be sure to stay on top of it in the future). The link can be found at http://www.ladyada.net/learn/arduino/lesson5.html.

      Essentially they create a problem set starting with basic switch functions… helping build the code ground up for recognizing change in state and output controls. Towards the end they give you a series of problems involving a Bike company that needs help programming a new lighting system. The various stages of the prompt test your abilities and end with the creation of a light system which has 4-5 separate modes activated by the button. This piecemeal way of learning was personally very helpful.

      There were a number of other tutorials that I found helpful, one of which explained the use of millis() instead of delay(). By using millis() as a timer instead of delay(), one is able to nest other functionality within conditionals that otherwise would not be able to run with delay() since delay() stops all processes within the Arduino. A notable example would be having one LED blink 500ms after another has started blinking, creating a sort of Lag effect. Using delay() would prevent you from activating another LED while the former is being delayed. Another use of millis() was creating a stopwatch which blinks as a timer begins… the push of a button turns the timer off, the start and end times are calculated as Serial.println spits out the time.

      • dss49 4:28 pm on October 14, 2011 Permalink | Reply

        debouncing was helpful as well.. making sure both readings of the input were consistent.

    • yonglee2011 4:27 pm on October 14, 2011 Permalink | Reply

      Two Exercise that I like or helpful:
      The custom function for different Blinks are good sample of diverse options we can use. I wish the codes are more detailed, so it is easy to follow on the Arduino. I type the code from the book, but the code didn’t work.

      Conditional section show diverse conditional options. But I wish the conditional section has more sample codes.

      Difficult exercise:

      There are some samples of using arrays. I played with Arrays, and wish there are more samples to look up. I found the book is helpful, but it seems it doesn’t have depth details.

      I really like what While and For Loop do, and wish there are more exercise to help a stater to understand the concepts and samples.

    • mrcansler 4:27 pm on October 14, 2011 Permalink | Reply

      The two readings I found most interesting were 2.10 (Functions), and 2.19 (Logical Operators). Until this point, I was unaware that functions even existed within this programming environment, and they appear to be a useful resource when constructing larger sections of code later. The logical operators sections was useful, as they are actually very basic concepts, but I was not particularly familiar with these basics. Still feel like I’m playing catchup with Syntax.

      I had some difficulty with arrays, as I feel like I completely get them structurally, but whenever I try to implement them I always seem to mess up the for loops associated with counting through them. I’m also having a bit of trouble digesting 2.16 “Switch”, and figuring out when to use these vs if/else statements. Is there a specific number of inputs before it’s best to use SwitchCase?

    • Aneta Genova 4:27 pm on October 14, 2011 Permalink | Reply

      I found most useful the array reading and exercise.It makes working with many variables extremely easy and certainly shortens the code. I developed a project about bouncing animals in a field and the array list was the easiest way to do them.

      I found very easy the functions reading and exercise. The first exercise about blinking and delay was very familiar to sketches we’ve done in class.

      I found challenging the logical operators and logical comparisons and I definitely get confused when we get to compare strings. I was not able to do that assignment.

    • jasonkim1006 4:27 pm on October 14, 2011 Permalink | Reply

      1. Which two exercises or code did you find most useful or valuable from the reading? Be as specific as possible.

      a) The first code I found to be very useful was the case / break code. It was really interesting to get input from the serial monitor and make the LED blink.
      if(Serial.available()){
      char ch = Serial.read();
      switch(ch){
      case ‘1’:
      Serial.println(“blink once!”);
      for(int i = 0; i<4; i++){
      myBlink(i,70);
      }

      Using default, we can set the default input and by using the switch case, we can use any key on the keyboard to create an input and make, for example, an LED blink sequence. Just by using the case '1':, case '2':, etc. we can determine how many different types of sequences we want.

      b) The second code I found very useful were using logical operators such as and (&&), or (||), and not (!). By using logical operators, we can determine diverse situations such as if both switches are pressed, both the switch and the tilt sensor are sending input, either the first button or the last button is pressed, etc. By including logical operators, there can be so many different types of situations with just four buttons. Instead of making one button do one thing, we can make a combination of one, two, three, or four buttons to something else. The logical operators are also good for setting up boundaries or giving certain conditions to inputs.

      2.Which two exercises or code did you find most difficult or confusing from the reading? Be as specific as possible.

      a) The first code that was really difficult to understand was calculating the amount of time using the switchTime() function. It was really hard to understand because whenever I tried it, the counter would increase rapidly or even decrease to a high negative number. I want to try using the "long" and "millis()" more so that I can understand its concept better. Because we used pullup resistors inside the Arduino, the HIGH and LOW was also a bit confusing to understand. The state should be inverted when using different resistors.

      long switchTime(){
      static unsigned long startTime = 0;
      static boolean state;

      if(digitalRead(inPin) != state){
      state =! state;
      startTime = millis();
      }
      if(state == LOW){
      return millis() – startTime;
      }
      else{
      return 0;
      }
      }

      b) Related with the switchTime() function is the debounce code. It took me a long time to understand the debounce code by using booleans of state and previousState. I think it was especially hard to understand because the debounce does not actually give direct feedback. Switch codes worked without having to use the debounce code and therefore it was at first hard to understand what "debouncing" actually did to my code. Later did I find out it was just a check for a few milliseconds to see if the button was stable enough to input and output information. It was a comparison between the current state and previousState and to see if they were equal.

    • litchirhythm 4:29 pm on October 14, 2011 Permalink | Reply

      ● The most useful exercise would be 5.4, the switch timer, for sure. It shows how to use timing (millis() function) to count how long you push the button and make led lit up in relative amount of time.

      And the other one that is interesting is 2.16 on the ‘switch’ logical command which I never know before. It function can be written with a long list of if statement but switch can be really handy on another person (or yourself) to read and understand the code much easier.

      ● The most difficult would also be the 5.4, the switch timer, since the first homework assignment is to tweak this one to make it blink. So I have to know this code inside out to be able to tweak it. In it, I have to apply the concept of custom function that count the time and return the data back to the main loop (the concept from 2.10 the function block), It’s like a wrap up of all exercises.

      Another thing that I find most difficult is Array (2.4). Even we have saw some of them on the example we work on. But to read and understand all of the concept and remember the syntax so that I can think and make it to work in the way I want is still hard. Because you’ll have to use a for loop to run the arrays all the time. But I think I understand it much more now.

    • josefayala 4:33 pm on October 14, 2011 Permalink | Reply

      I liked the vast majority of the tutorials. My favorite was Arrays because in the past I have not been able to properly execute them. There is something gratifying about making 100 ellipses with 3-4 lines of code (otherwise we’d have to hard code each ellipse). With regards to Arduino work it’s nice to know that I can call on a group of pins for one purpose by simply calling an array. What I was surprised to find out is that the array can hold a string of characters. I found that character strings are good possibly for Serial Monitor work. Functions were also a good time, and it was good to get a good look at the use of parameters and returns.

      Switch statements can be difficult, but overall the concept is well embedded into my mind. I understand the importance of using breaks within a switch command but kind of miss the logic of setting it up with what seem to be all the arguments wrapped between the switch (I guess from the purpose of switching). Is it comparable to an array ? Who knows…I guess I have to re-read it.

      -josef

    • aisencc 5:02 pm on October 14, 2011 Permalink | Reply

      10/14 Reading Assignment Response
      The easiest sections from the readings were the Arrays Introduced and Logical Operators. Both of these sections are reviews to the Processing and Arduino IDEs. Both of these sections seemed a bit redundant, since it is crucial to know these in order to create any functions or when working with a variety of pins that are programmed to do similar things. For the homework assignment I used both of these methods in structuring my code. Every time I use these

      The most challenging chapters were Determining How Long a Switch is Pressed and Knight Rider. These are not necessarily hard to understand, but more dense than the practical sections I mentioned above. The Knight Rider was not complicated, but it was dense. Understanding arrays makes this section easy, because the use of for loops with the right amount of delay HIGH and LOW patterns is what makes the LED pins blink one at a time. Determining How Long a Switch is Pressed was the most challenging section of the homework because it introduces a counter and functions. I am still having to read it over and over again, to try to understand exactly what it’s doing.

  • Jun Sik (Jason) Kim 11:08 pm on October 7, 2011 Permalink | Reply  

    Pulse Sensor Group 

    Jun Sik (Jason) Kim

    Rachel Law

    Freddie Andrade

    Amanda Wong

    http://www.pulsesensor.com is the official site for the Pulse Sensor.

    From there, we are going to read:

    1. The startup of the Pulse Sensor on google docs.

    2. Schematics & guidelines to the Pulse Sensor.

    3. And ofcourse the code.

    There are also information regarding the open hardware here.

    It’s going to be real fun learning about the Pulse Sensor!

    This is the video we are going to look at while studying the Pulse Sensor.

    http://www.kickstarter.com/projects/1342192419/pulse-sensor-an-open-source-heart-rate-sensor-that

    Thanks!

     

     

     

     

     

     

     

     
  • hirumi 6:33 pm on October 7, 2011 Permalink | Reply  

    LoL Shield 

    TEAM:
    Josef
    Monica
    Maya
    Hirumi

    Reading list
    Book:

    Web:
    http://www.sparkfun.com/products/9795
    http://jimmieprodgers.com/kits/lolshield/makelolshield/
    http://jimmieprodgers.com/kits/lolshield/programlolshield/
    http://code.google.com/p/lolshield/

    Datasheet:

    2 examples for class( include photos of circuit)

    with – twitter to text
    without arduino – frame by frame animation)

    lol shield theater: http://falldeaf.com/2011/02/the-lol-shield-theatre/

     

     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel