Introduction: A Real Case from the Field
During a packaging line commissioning project in a food factory, we encountered a typical but frustrating issue:
The entire bagging line could not enter automatic mode.
At first glance, it looked like a system-level problem:
- Manual mode worked
- Individual actuators (cylinders, motors) were fine
- No obvious hardware faults
However, the system was stuck at:
👉 “Safety conditions not satisfied”
The team spent nearly 3 hours checking:
- PLC logic
- Relay outputs
- VFD run permission signals
- Pressure switches
Everything seemed normal.
Finally, an experienced technician walked to the safety door, took a multimeter, and measured the sensor directly.
The result?
👉 Signal ON when the door was open, but OFF when the door was closed.
After checking the drawing, we found:
- PLC required a “door closed = run permission” signal
- But the installed sensor logic was exactly the opposite
✔ Program was correct
✔ Device was not faulty
❌ The issue was simply: NO/NC logic misunderstood from the beginning
Fixing it took less than 20 minutes.
But we had already lost half a shift.
Common Symptoms of NO/NC Mistakes in Industrial Systems
When NO (Normally Open) and NC (Normally Closed) are confused, you often see:
- Start button is wired correctly, but the machine doesn’t start
- System loses run condition immediately after wiring a stop signal
- Relay or contactor feedback doesn’t match PLC logic
- Sensors trigger at the wrong time (or fail to trigger)
- Safety signals (door, level, pressure) never satisfy interlock conditions
- Engineers suspect PLC, modules, or signal noise — but miss the real cause
👉 These issues often look complex, but the root cause is extremely simple.
Why Engineers Keep Making This Mistake
1. Confusing “Current State” with “Normal State”
Many people judge based on what they see right now:
- Relay is energized → contact is closed → assume NC
- Button pressed → circuit is closed → assume NC
This is incorrect.
👉 NO/NC is defined by the state BEFORE any action.
2. No Unified Reference Across Different Devices
Different devices behave differently:
- Push buttons (manual action)
- Relays (coil energized)
- Proximity sensors (target detection)
- Limit switches (mechanical force)
Without a consistent reference, engineers:
👉 Use different logic for each device → leading to confusion
3. Difficulty Translating Drawings into Real Conditions
Many engineers can read schematics.
But in the field:
👉 They struggle to convert logic diagrams → physical signal states
This is where most mistakes happen.
4. Knowing Definitions, But Not the Purpose
It’s easy to memorize:
- “Normally open = open at rest”
- “Normally closed = closed at rest”
But more important is:
👉 Why certain signals are designed as NO or NC
Without this understanding, wiring decisions become guesswork.
Practical Method to Avoid NO/NC Errors
Instead of guessing, follow this simple method:
Step 1: Define the “Normal State”
Ask yourself:
👉 What is the state when the device is NOT activated?
- Button not pressed
- Relay not energized
- Sensor not triggered
- Limit switch not actuated
- Pressure/level not reached
This is your reference point.
Step 2: Think About the Control Purpose
In real industrial design:
- Start / trigger signals → usually NO
- Stop / emergency / safety signals → usually NC
Why?
👉 Two key principles:
- Fail-safe (loss of power = safe condition)
- Fault detection (broken wire = alarm condition)
Step 3: Measure Before and After Action
The most reliable method:
- Measure signal in normal state
- Apply action (press, trigger, energize)
- Measure again
👉 If it changes state → you know the truth
👉 No guessing needed
Key Takeaway: How to Identify NO vs NC
NO/NC is NOT about whether the signal is ON or OFF right now.
👉 It is defined by the normal (inactive) condition:
- Open in normal state → Normally Open (NO)
- Closed in normal state → Normally Closed (NC)
Why This Small Detail Matters So Much
In real projects, many “complex faults” are actually caused by:
👉 A wrong assumption at the very beginning
Once the base logic is wrong:
- Wiring goes wrong
- PLC logic appears wrong
- Troubleshooting goes in the wrong direction
And engineers end up:
👉 Wasting hours chasing non-existent problems
Practical Advice from Real Projects
In our experience working with:
- Flow meters
- Pressure switches
- Level instruments
- Safety interlock systems
👉 One of the first things we always confirm is:
Signal logic (NO or NC)
Because a mismatch between:
- Instrument output
- PLC expectation
👉 Can easily lead to commissioning delays and system faults.
Need Help with Signal Logic or Instrument Selection?
If you are:
- Unsure about NO/NC selection
- Facing signal mismatch in your system
- Selecting flow, level, or pressure instruments
👉 Feel free to contact us.
We can help you:
- Review your signal logic
- Recommend suitable configurations
- Avoid unnecessary troubleshooting time on site