Did you know that a robot’s button can be called “normally closed” even while the robot is switched off? That sounds like a contradiction until we notice what the word normally means in a switch diagram. One small vocabulary difference can decide whether a student’s drawing, program and physical model all describe the same thing.
The short answer: for a simple mechanical contact, normally open (NO) means its electrical contacts are open when the switch is at rest, and normally closed (NC) means the contacts are closed when the switch is at rest. “Normally” refers to the switch’s ordinary unpressed or unactuated condition—not whether the whole robot is on, the door is open, or the classroom is using the device. When pressed or actuated, the relevant contact can change state.
First imagine a paper switch, not an electrical circuit
Draw two dots on a card and put a gap between them. Label it open. Move a paper bridge so it touches both dots. Label that closed. In this simple model, open describes a broken electrical contact path; closed describes a continuous one. These are descriptions of a contact, not instructions to switch on a motor.
Now draw a spring-loaded button. If its contact path is open before anyone pushes, it is an example of normally open. If its contact path is closed before anyone pushes, it is an example of normally closed. A single device can also provide both types through different terminals.
For Primary learners, these cards are enough. There is no reason to connect wires to mains power or improvise a laboratory experiment. Upper-primary and secondary pupils can use a teacher-approved low-voltage demonstration or simulator to see how a physical state becomes a computer-readable signal.
The core comparison: a four-cell truth table
Use this as a contact-state table, not a table of what a motor will do. When the switch is at rest, a normally open contact is open and a normally closed contact is closed. When the switch is actuated in the relevant manner, the normally open contact closes and the normally closed contact opens.
- At rest, NO contact: open; the pair of contacts does not complete that path.
- Pressed or actuated, NO contact: closed; that pair completes its contact path.
- At rest, NC contact: closed; that pair completes its contact path.
- Pressed or actuated, NC contact: open; that pair no longer completes its contact path.
The SparkFun Button and Switch Basics tutorial describes this distinction in accessible engineering language. Treat it as a starting model: switches vary, mechanical bouncing happens, and a complete circuit or program can contain more than one component. Real products must be understood using their own schematics.
A robot bumper experiment on paper
Imagine a fictional classroom robot that needs to detect when it touches a cardboard barrier. The team wants a bumper button that springs back when contact ends. The button has three labelled terminals: COM (common), NO and NC. In an elementary changeover arrangement, COM is connected to NC at rest and connects to NO when the switch is pressed. The team must choose which pair it intends to observe.
Team A chooses COM and NO. At rest, that contact path is open. When the bumper presses the button, the path closes. If the input circuitry and software are designed to respond to that change, the team can tell the robot to stop. But the physical “closed” state alone is not the same statement as “stop”: the program and wiring must actually implement that action.
Team B chooses COM and NC. At rest, the contact path is closed. When the bumper presses the button, it opens. The team can also design an input and program to detect this different change. If pupils blindly copy Team A’s condition without checking which contact they wired, the robot may react at the wrong moment.
These are fictional teaching teams. They do not describe an actual eduKate class or student outcome. The exercise explains vocabulary and logic, not an approved design for a real collision-protection or machine-safety system.
Why ‘closed’ does not automatically mean ‘motor on’
Suppose a diagram shows a contact connected to a microcontroller input. That device may use a pull-up resistor, a pull-down resistor, inverted logic or another interface. Depending on the arrangement, a pressed button might produce a digital HIGH or LOW. The relation between contact state and a software value is not universal. A beginner who translates “NO means zero and NC means one” without reading the circuit diagram has introduced a new mistake.
A robust explanation has three layers: physical contact (open or closed), electrical input (the signal measured by the electronics) and software action (what the program decides to do). Treat them as three separate sentences before connecting them. This is the same discipline children use in Science when they separate an observation, a measurement and an inference.
The five words that keep a robotics team coordinated
- Contact: a conductive interface that may connect or disconnect part of a circuit. “Contact closed” tells you about continuity at that point, not necessarily the whole machine.
- Actuate / actuation: to cause a mechanism to change state, for example by pressing a button or moving a lever. A contact can change when actuated and return when released.
- Rest or unactuated: the reference position used to interpret “normally”. For an ordinary spring-return pushbutton, it is typically the not-pressed position.
- Common (COM): on a basic changeover switch, the shared terminal that connects to one or another contact depending on switch position. Confirm the actual device’s pin arrangement; labels can differ.
- Debounce: a technique for coping with rapid repeated transitions caused by physical contacts settling. A single press can create several very short electrical changes, which software may need to handle.
These words have useful families: actuate / actuator / actuation, connect / connection / connected, conduct / conductive / conductor, detect / detected / detection. For natural technical writing, practise press the button, release the lever, measure continuity, read the input state and verify the wiring against the diagram. A pupil who uses these combinations can explain a failure far more clearly than someone who says “the robot is weird”.
An easy test for a confused instruction
Compare these statements. “The button is normally closed, so the robot should start running when the button is not touched.” This jumps from one contact description to a whole-system behaviour with no circuit or program. The safer technical statement is: “According to the switch diagram, the NC contact is closed when the switch is unactuated; we still need to verify how that state is read and what action the program assigns.” The longer statement is more precise because it makes the missing evidence visible.
Notice the register change. Among teammates a child might ask, “Are we using NO or NC?” In a formal project log the same question becomes, “Which pair of switch terminals is connected, and what continuity state is expected before and after actuation?” Both are useful. The formal question leaves less room for misunderstanding when another person checks the work later.
Practice sequence: from words to logic without wiring
- Begin with gesture cards. Give each pair two cards marked OPEN and CLOSED. Read “NO at rest” aloud. Children raise OPEN. Read “NC at rest.” Children raise CLOSED.
- Draw a two-row state table. For each contact type, write states under “unpressed” and “pressed”. Ask students to explain why “normally” belongs to the first column.
- Add a fictional program condition. Say “our input is defined as bumper detected when the contact changes from its baseline state.” Does that describe NO or NC uniquely? No: both may be used with appropriate input interpretation.
- Change the equipment label. One team finds terminals COM, NO and NC. Another has only two terminals. What information does the second team need from the product documentation to know which contact type it has?
- Ask for a test plan. Without touching live hardware, have pupils write what they would verify under approved supervision: label the terminal pair, compare the diagram, note the at-rest state, then check the actuated state using appropriate approved tools.
The point is not to build a machine that works once by accident. It is to build a shared language so every team member can predict, test and explain what should happen.
Three plausible mistakes and how to repair them
Mistake 1: “Normally closed means the door is usually shut.” That mixes the everyday word closed with the electrical contact meaning. A switch on a door can have a different physical and electrical state. Draw the electrical contacts instead of guessing from the door.
Mistake 2: “An NO switch is always off.” NO refers to the resting condition of the named contact. When actuated, that contact may close. And the meaning of off for the larger circuit still requires a system diagram.
Mistake 3: “Using an NC contact makes any robot automatically safer.” No. Safety depends on an engineered system, its failure modes, correct components, wiring, software and testing. A school project should never be promoted as a certified protective stop. Never bypass interlocks or experiment with equipment that can injure someone.
Diagnostic questions with worked answers
- Question 1: A normally open button is not being pressed. What is the contact state? Answer: open.
- Question 2: A normally closed contact is actuated. What changes in the simple model? Answer: its relevant contact path opens.
- Question 3: Does “NC” prove a microcontroller pin is HIGH at rest? Answer: no. You need the input circuit and logic conventions.
- Question 4: What does COM often mean on a changeover switch? Answer: common terminal; inspect the exact schematic to see which contact it connects to in each condition.
- Question 5: Why might a single press cause more than one short signal transition? Answer: mechanical contact bounce; the system may need debouncing.
Connect the language to English, Mathematics and Science
English: students learn that a technical word has a precise meaning in context. They practise qualifying a claim: “in the unactuated state”, “for this contact pair”, “according to the diagram”. These clauses prevent ambiguity in reports, instructions and discussions.
Mathematics: a two-state table introduces logical conditions and systematic checking. Learners can practise “if”, “and”, “not” and “otherwise” in paper-based examples before coding. Make sure a truth-table entry describes the stated physical variable, not a guessed program output.
Science and technology: the same observation–hypothesis–test discipline helps with electrical circuits, simple robots, sensors and engineered systems. Primary children can use cards; secondary G1, G2 and G3 students can progress to labelled diagrams and safe simulation. Nothing here claims that a particular contact type will appear in a specific PSLE or SEC examination paper.
Learning pathway: the distinction becomes useful in later technical education, automation, equipment maintenance and engineering. This is not a claim that an individual student has been trained for industrial electrical work; school-level vocabulary is a foundation, not a professional qualification.
Try a transfer exercise tomorrow and next week
Tomorrow, have a learner explain the difference between normally open and normally closed in one breath without looking at this page. If they say “open means on” or “normally means every day”, ask them to redraw the contact pair and explain the resting position.
Next week, give them a fictional drawing of a lid sensor, a printer cover button or a model railway end stop. The new question is not “Which robot from today has this?” but “Where is the switch’s resting state, what are the contact labels and what additional system information is needed?” That is transfer: a learned term helps solve a new problem.
For students troubleshooting their program, a related eduKate guide explains how to distinguish syntax, runtime and logic errors. A perfectly written program can still have wrong assumptions about a sensor; the two articles answer different questions.
Frequently asked questions
Does a light switch always have NO and NC terminals? No. Switch designs vary; a simple household wall switch is not necessarily a changeover device exposing separate NO and NC contacts. Read the actual component specification and do not work on household mains circuits.
Can children measure a real switch? Only in an appropriate teacher-supervised low-voltage learning activity using approved equipment and procedures. Printed schematics and safe simulations are enough to learn the distinction.
What is the difference between a momentary and a maintained switch? A momentary switch returns after the action is released; a maintained switch remains in its selected position until it is moved again. That describes its operating behaviour, which is separate from the contact labels NO and NC.
Why isn’t this just a coding vocabulary lesson? The same terms appear in mechanical components, electrical diagrams, testing procedures and the language a team uses to trace a fault. Their value is precisely that words can connect physical observations and software explanations.
Does NC mean a certified fail-safe emergency stop? No. Some engineered safety circuits monitor specially designed NC contacts, but safety-rated protection requires suitable components, design and validation. A simplified classroom contact diagram is not a safety specification.
Verified further reading
- SparkFun: Button and Switch Basics — beginner-friendly definitions of normally open and normally closed switches.
- Schneider Electric: Normally Open and Normally Closed Contact Terminology — an industrial supplier’s terminology context; always interpret the specific device correctly.
- eduKateSG Vocabulary Articles and Knowledge Hub — follow-up practice on precise meanings and word families.
- eduKateSG: Syntax, Runtime and Logic Errors in Student Code — a separate guide for the software side of technical problem-solving.
A simple sentence is worth remembering: “Normally describes the contact at rest.” From that clear starting point, a curious learner can ask better questions, write a more useful test and collaborate without confusing what a button is with what a whole robot should do.