Project Traffic Light: Master Arduino Variables & Logic Control

Project: The Code

Let’s write it. Open your IDE. Start fresh.

// Project: Traffic Light Controller
// Day 12

// 1. Declare Variables
int redPin = 12;     // Red LED connected to Pin 12
int yellowPin = 11;  // Yellow LED connected to Pin 11
int greenPin = 10;   // Green LED connected to Pin 10

void setup() {
  // 2. Configure Pins
  // We need to tell the Arduino that ALL these pins are outputs
  pinMode(redPin, OUTPUT);
  pinMode(yellowPin, OUTPUT);
  pinMode(greenPin, OUTPUT);
}

void loop() {
  // --- STATE 1: GREEN ---
  // Turn Green ON, others OFF
  digitalWrite(greenPin, HIGH);
  digitalWrite(yellowPin, LOW);
  digitalWrite(redPin, LOW);
  delay(5000); // Wait 5 Seconds. Cars are moving.

  // --- STATE 2: YELLOW ---
  // Turn Yellow ON, others OFF
  digitalWrite(greenPin, LOW);
  digitalWrite(yellowPin, HIGH);
  digitalWrite(redPin, LOW);

  delay(2000); // Wait 2 Seconds. Slow down!

  // --- STATE 3: RED ---
  // Turn Red ON, others OFF
  digitalWrite(greenPin, LOW);
  digitalWrite(yellowPin, LOW);
  digitalWrite(redPin, HIGH);

  delay(5000); // Wait 5 Seconds. Stop.
}

Analyze the cleanliness

Look at digitalWrite(greenPin, HIGH). It reads like English. “Write the Green Pin High.” Even a non-programmer can look at that and understand the safety logic.

Deep Dive: Global Traffic Logic (US vs UK)

Did you know traffic lights work differently around the world? Our code above mimics the USA/Continental Europe standard. Green -> Yellow -> Red -> Green.

But in the UK (and many Commonwealth countries), there is a “Get Ready” phase. Red -> Red + Amber -> Green. This gives drivers a warning that the light is about to turn green, so they can shift into gear.

Challenge: The UK Sequence

Can you modify your code to simulate a London intersection? You need a 4th state.

• Green (5s)
• Yellow (2s)
• Red (5s)
• Red (HIGH) AND Yellow (HIGH) (1s)

Try it. The beauty of software is that you don’t need to change a single wire on your breadboard. You just type a new digitalWrite. In the hardware age (using 555 timers from Day 5), changing from US to UK logic would have required tearing the circuit apart and rebuilding it. Here, it takes 30 seconds.

Solution: The UK Sequence Code

Here is how you would implement the London-style logic. Notice Step 4. We turn TWO pins HIGH at the same time.

void loop() {
  // 1. GREEN (Go)
  digitalWrite(greenPin, HIGH);
  digitalWrite(yellowPin, LOW);
  digitalWrite(redPin, LOW);
  delay(5000);

  // 2. AMBER (Stopping)
  digitalWrite(greenPin, LOW);
  digitalWrite(yellowPin, HIGH);
  digitalWrite(redPin, LOW);
  delay(2000);

  // 3. RED (Stopped)
  digitalWrite(greenPin, LOW);
  digitalWrite(yellowPin, LOW);
  digitalWrite(redPin, HIGH);
  delay(5000);

  // 4. RED + AMBER (Get Ready)
  digitalWrite(greenPin, LOW);
  digitalWrite(yellowPin, HIGH); // ON
  digitalWrite(redPin, HIGH);    // ON
  delay(1500);
}

This demonstrates the power of the microcontroller. Complex logic (two lights on, then one off) is trivial.

Deep Dive: Fail-Safe Logic

In the real world, “Traffic Controllers” are Life-Safety Systems. If the Microcontroller freezes, people die. Real traffic lights have a hardware monitor called a Conflict Monitor Unit (CMU).

• The Job: It watches the wires.
• The Trigger: If it sees GREEN on Northbound AND GREEN on Eastbound at the same time…
• The Action: It physically cuts power to the Green lights and forces all Red lights to flash. We can’t build a CMU easily, but in code, we write:

// Safety Check
if (digitalRead(greenNorth) == HIGH && digitalRead(greenEast) == HIGH) {
    emergencyShutdown();
}

This is Defensive Programming. You assume your code will fail, and you plan for it.

Day 12 Challenge: The Intersection

Can you simulate a FULL intersection? Imagine North-South Logic vs East-West Logic.

• When North is Green, East MUST be Red.
• When North turns Yellow, East is still Red.
• When North turns Red, East turns Green. Hardware: Add 3 more LEDs (Pins 7, 6, 5). Software: Write the digitalWrite commands to synchronize them. Safety Check: Ensure Green never overlaps! This is your homework for tonight.

The Trap: The delay() Function

I have a confession. The code we wrote today has a fatal flaw. It relies on delay().

delay(5000) tells the processor: “Go to sleep for 5 seconds. Do nothing. Ignore the world.” What if we wanted to add a Pedestrian Button? If a pedestrian presses the button while the light is Green (during the 5000ms delay), the Arduino won’t see it. It is asleep. It will only check inputs after it wakes up.

This is called “Blocking Code”. For a simple traffic light, it’s fine. But for a robot or a game, it is a disaster. In a few days (Day 15), we will learn the professional solution: millis(). millis() allows the Arduino to “multitask” (check a watch) instead of sleeping. But for today, enjoy the simplicity of the delay.

Troubleshooting

• Yellow is too dim: Yellow LEDs often need slightly more voltage than Red ones, or your resistor value might be too high. Try swapping for a lower value resistor (e.g., $220\Omega$ instead of $330\Omega$).
• All ON at once: Did you forget to copy the LOW commands? Remember, digitalWrite is “Sticky”. If you turn a pin HIGH, it stays HIGH until you explicitly tell it to go LOW.
• Compilation Error ‘redPin was not declared’: Check your spelling. C++ is case sensitive. RedPin is different from redPin.

The Engineer’s Mindset: The Pedestrian Problem

This simple project exposes a massive flaw in linear programming. Imagine we added a button to Pin 2. We want the light to turn Green IMMEDIATELY when the button is pressed. With our current code (delay(5000)), if you press the button 0.1 seconds after the delay starts, the Arduino ignores you for 4.9 seconds. This is unacceptable for safety. In a real traffic controller, there is no “delay”. There is a State Machine. It constantly checks:

• Is time up?
• Is button pressed?
• Is sensor triggered? If ANY of those are true, it changes state. We will build this advanced version in Day 15 (Multitasking). For now, understand that delay() is a training wheel. Eventually, we must take it off.

Advanced Troubleshooting: Why is my circuit weird?

• Ghosting: The Green LED glows faintly when Yellow is on.

Cause: You inserted the resistor into the wrong row, bridging the connection. Check your breadboard rows (a-e and f-j are separated by the ravine).

• Flickering: The LEDs are unstable.

Cause: Your USB cable might be loose, or your laptop port is providing low current. Try a different USB port.

• The “Upload” Error: “avrdude: stk500_recv()”.

Cause: You selected “Arduino Uno” but you have a “Nano” or “Mega” selected in the Tools menu. Double check!

The Engineer’s Glossary (Day 12)

• Variable: A named storage location in memory.

• Integers (int): Whole numbers.

• Hardcoding: Using specific values (like ‘13’) directly in logic code. Bad practice.

• Sequence: A specific order of operations.

• State Machine: A system that relies on distinct phases (Green, Yellow, Red).

The Bill of Materials (BOM)

Conclusion

You have modeled reality. You took a physical concept (Safety logic) and translated it into C++. You learned that Variables are not just for math—they are for legibility. They make your code human-readable.

Tomorrow, on Day 13, we are going to revisit an old friend. Remember the Knight Rider Scanner from Day 10? It required two chips and a mess of wires. Tomorrow, we will build it with the Arduino. We will learn about Arrays and For Loops to create complex animations with just a few lines of code.

See you on Day 13.