How to Define Boolean Expression Logic for Microcontrollers and Relay Circuits

To accurately define boolean expression in electronics and embedded programming, it is a logical statement combining variables and operators that evaluates to exactly one of two states: true (1/HIGH) or false (0/LOW). In a physical circuit, this expression is the exact decision-making boundary that changes a system's state—dictating whether a 5V logic pin sources current to trigger a relay, whether a PLC ladder rung energizes a motor contactor, or whether a MOSFET gate receives the threshold voltage to switch a high-power load.

The Core Mechanics: Evaluating Logic States

At the bench, boolean logic strips away analog ambiguity. A sensor might output 2.47V, but a microcontroller's comparator or ADC threshold reduces that to a binary 1 (TRUE) or 0 (FALSE). We combine these binary states using three fundamental operators:

• AND (&&): Output is TRUE only if all inputs are TRUE.
• OR (||): Output is TRUE if at least one input is TRUE.
• NOT (!): Inverts the input state (TRUE becomes FALSE).

Worked Numeric Example: ADC Thresholds and Binary Translation

Let us look at a real numeric example using an ESP32 reading a 10k NTC thermistor via a voltage divider. The ESP32's 12-bit ADC maps the 0V to 3.3V range to integer values between 0 and 4095.

Suppose we want a cooling fan to turn on when the temperature exceeds 80°C. Through bench calibration, we know 80°C corresponds to an ADC reading of 1250. Because the thermistor's resistance drops as temperature rises, a higher temperature yields a lower ADC value. We also want a manual override switch (GPIO 12) to force the fan on regardless of temperature.

The Expression:
fanState = (adcValue < 1250) || (manualOverride == true);

Plugging in bench numbers:

1. The thermistor is at 85°C. The ADC reads 1100.
2. The manual override switch is OFF (GPIO 12 reads 0).
3. Evaluate the left side: (1100 < 1250) evaluates to TRUE (1).
4. Evaluate the right side: (0 == 1) evaluates to FALSE (0).
5. Combine with OR: 1 || 0 evaluates to TRUE (1).

The microcontroller sets the fan control pin HIGH, energizing the relay. For a deeper look into how microcontrollers handle these GPIO states, refer to the Espressif ESP-IDF GPIO documentation.

Where You Meet This in Practice

You will encounter boolean expressions in three primary domains on the jobsite or in the lab:

Real-World Scenario Walkthrough: The Greenhouse Heater Failure

Abstract logic is easy; physical hardware is unforgiving. Here is a scenario where a perfectly defined boolean expression failed in the real world.

The Setup:
A maker builds an automated greenhouse heater using an ESP32, a DHT22 temperature/humidity sensor, and a 4-channel 5V relay module to switch a 1500W resistive heater via a 30A contactor. The code defines the expression: if (tempF < 50 && humidity < 85). If true, the ESP32 sends a HIGH signal to GPIO 26, which is wired to the relay module's IN1 pin.

The Numbers:
A winter night drops the greenhouse to 42°F. The DHT22 reads 42°F and 60% humidity. The expression evaluates: (42 < 50) is TRUE. (60 < 85) is TRUE. TRUE && TRUE yields TRUE (1). The ESP32 sets GPIO 26 to 3.3V (HIGH).

The Outcome:
The relay does not click. The contactor remains open. The heater stays off, and the plants freeze.

What Went Wrong:
The builder failed to account for Active-LOW hardware logic. Most cheap optocoupler-isolated relay modules require the control pin to be pulled to GND (0V / FALSE) to complete the circuit through the internal LED and energize the coil. Sending a logical TRUE (3.3V) to the IN1 pin resulted in zero potential difference across the optocoupler. The software boolean expression was mathematically flawless, but the physical boolean state was inverted.

The Fix:
Invert the output in the firmware: digitalWrite(RELAY_PIN, !heaterState); or physically rewire the circuit to use a non-isolated high-side MOSFET driver that triggers on a HIGH signal.

Common Pitfalls: What People Confuse It With

When troubleshooting logic circuits, builders frequently conflate software syntax with physical wiring states.

Bitwise vs. Logical Operators

In C/C++, a single ampersand (&) is a bitwise AND, while a double ampersand (&&) is a logical AND. If you write if (adcValue & 1024), the compiler performs binary math on the bits themselves, not a true/false evaluation of the whole number. This leads to phantom triggers where the expression evaluates to a non-zero integer (which C treats as TRUE) even when the logical condition was meant to be false. Always use && and || for control flow decisions. For more on digital logic foundations, see the All About Circuits Digital Electronics textbook.

Normally-Open (NO) vs. Logical TRUE

A physical Normally-Open (NO) switch does not mean the logical state is always TRUE. A NO float switch wired to a pull-down resistor reads FALSE (0V) when the water is low, and TRUE (5V) when the water rises and closes the contacts. Confusing the physical resting state of the hardware with the logical variable name in your code is the root cause of 90% of 'my circuit does the exact opposite of what I want' bench headaches.

FAQ: Quick Answers on Boolean Logic in Electronics