WEEK 1

CODE.
#

int button;
int buttonState = 0;
int prevbuttonState = 0;

void setup() {

  pinMode(15, OUTPUT);
  pinMode(16, OUTPUT);

  pinMode(17, INPUT);
  Serial.begin(9600);  // similar to console.log, we create a communication channel. This sends info.
}

void loop() {
  button = digitalRead(17);  // read, the button: is it on and off, is it 330v or ground.
  Serial.println(button);

  //buttonState = digitalRead(17);

  digitalRead(17);

  if (buttonState == prevbuttonState != button == LOW) {

    Serial.print("Button state changed to: ");
    Serial.println(buttonState);

    analogWrite(15, 255);  // LED 1 OFF
    analogWrite(16, 0);    // LED 2 OFF

    buttonState = button + 1;
  }
   prevbuttonState = buttonState;


  //works 
  if (buttonState == prevbuttonState && button == HIGH) {
    Serial.print("Button state changed to: ");
    Serial.println(buttonState);
    buttonState = button + 1;

    analogWrite(15, 255);  // LED 1 ON
    analogWrite(16, 0);    // LED 2 OFF

    prevbuttonState = buttonState;
  }

  if (buttonState == prevbuttonState && button == HIGH) {
    Serial.print("Button state changed to: ");
    Serial.println(buttonState);

    buttonState = button + 1;

    analogWrite(15, 255);  // LED 1 ON
    analogWrite(16, 255);  // LED 2 ON

    prevbuttonState = buttonState;
  }
  if (buttonState == prevbuttonState && button == HIGH) {
    Serial.print("Button state changed to: ");
    Serial.println(buttonState);
    buttonState = button + 1;

    analogWrite(15, 0);  // LED 1 OFF
    analogWrite(16, 0);  // LED 2 OFF

    prevbuttonState = buttonState;
  }
}

DOCUMENTATION
#

Session 1.

Figuring out the circuit.
- Initially I thought all the components of the circuit had connect with each other but was advised (by Isi and Adrian) that two separate led circuits and the switch can exist as individual circuits, then the code combines everything together.

Session 2.

First pseudocode.
1. Read a momentary switch being pressed
2. serial.println // for button.
3. When the program starts, both LEDs are off
4. if »» button // both off // low
5. When the switch is pressed once, the first LED turns on
6. else if »» Button === led 1 on
7. When the switch is pressed the second time, the second LED turns on (the first one should also still be on)
8. else if »» Button == led 1 || led 2
9. When the switch is pressed the third time, both LEDs turn off
10. else if »» Button == led 1 || led 2 (off)
11. Repeat this same cycle of LEDs turning on and off in sequence (off, one LED, two LEDs, off…)
Results
- Only lit the first bulb.
- The first bulb did not stay on continuously.

Session 3.

Use of conditional statements combining comparison and logical operators to check button and state together. (e.g: if(button == LOW && state == 1 ))
1. Advised (by Oskars) to add another variable that stores button values.
2. Tested using arrays to store the values as a variable named states, but was advised that it was not working as I needed to call the exact number in the array as one way of calling numbers. (e.g. if(button == LOW && state == [1] ))
3. Consulted ai.aalto to explain errors I wasn’t sure of.
4. E.g. Compilation error: ISO C++ forbids comparison between pointer and integer [-fpermissive]

Session 4.

Advised (by Matti and the tips tutorials) to add a variable that checks and stores the previous button state number, comparing it with the current button state and previous button state and whether the button is pressed or not. (e.g. if (buttonState == prevbuttonState && button == HIGH))
- Also to add a calculation that +1 from the previous buttonstate.
Results.
1. Only three conditions worked in different scenarios or changing the logical operators between “ ! = ” and == . The code seemed okay but I could be missing the addition part where the loop adds + 1 to the previous buttonstate number.
2. Both LED’s off.
3. One LED on.
4. Both LED on, but only on button click and not continuously.

Reflection.

The logic was simple, but yet hard at the same time.
I tried different solutions as mentioned in the sample examples above.
I was good at debugging for common errors first, clearing that up before revisiting the logic of the code.
I didn’t check for final code, or consult for final answers and I see this as the foundation for understanding states which is important in various use cases.

CODE. #

DOCUMENTATION #

CODE.
#

DOCUMENTATION
#