PLC Simulator
PLC field notessensors

NPN vs PNP Sensors: Wiring, Output Type, and PLC Input Connection

NPN sensors sink current (pull signal to 0V when active). PNP sensors source current (pull signal to +24V when active). The mismatch between sensor output and PLC input type is the most common discrete wiring mistake. This explains how to read your sensor datasheet, identify your PLC input type, and wire them correctly.

PLC Simulation Software8 min read

TL;DR: NPN sensors pull the signal wire LOW (to 0V / current sinking) when active. PNP sensors drive the signal wire HIGH (to +24 V / current sourcing) when active. Match the current path shown in the exact PLC module manual: an NPN sensor normally needs an input circuit with its common at +24 V, while a PNP sensor normally needs an input circuit with its common at 0 V. Do not rely on the words “PNP input” or “NPN input” alone—manufacturers do not always use those aliases consistently.

NPN vs PNP sensor wiring — output types and PLC input connection

Almost every discrete sensor on a factory floor — proximity sensors, photoelectric sensors, capacitive sensors, laser sensors — outputs either NPN or PNP. The sensor works perfectly when you test it with a multimeter. The PLC input refuses to change state. Nine times out of ten, the cause is an NPN/PNP mismatch. This is the single most common discrete wiring mistake in industrial electrical work.

The 3-Wire Sensor Cable

Almost all industrial proximity sensors and photoelectric sensors use a 3-wire connection:

Reference tableSwipe
Wire colourFunction
Brown+24 V DC supply (+VCC)
Blue0 V / common (GND)
BlackSignal output

The signal output wire is the one that changes state when the sensor detects a target. Whether it goes high (+24V) or low (0V) when active depends on the output type: NPN or PNP.

(Some sensors add a white 4th wire for a complementary output — if the black wire is NO, the white wire is NC. Same NPN/PNP rules apply.)

NPN Output: Current Sinking (Pull to 0V)

An NPN sensor contains an NPN transistor in the output stage. When the sensor detects a target, the transistor turns ON and connects the signal (black) wire to the 0V (blue) wire internally. The signal wire is pulled LOW — it reads approximately 0V.

When the sensor is NOT detecting: the transistor is OFF, the signal wire floats high (or is pulled high by the PLC input circuit). This is the OFF state.

Who uses NPN sensors: Japanese and Korean manufacturers (Panasonic, Keyence, Omron, Sick in some product families, Chinese manufacturers generally). NPN sensors dominate Asian-manufactured equipment and Asian OEM machine builds.

How to wire an NPN sensor to a PLC input:

The PLC input circuit must provide a path from +24 V through the input and into the sensor—commonly described as a sourcing input, with the input common at +24 V. When the NPN sensor pulls the signal wire to 0 V, current flows and the module registers ON. Confirm the terminal diagram because naming conventions vary.

+24V ──── [Brown wire] ──── NPN Sensor (brown)
                             │
+24V ──── PLC COM ──┐        │ (PLC sources current)
                    │        │
              PLC Input ──── [Black wire] ──── NPN Sensor (black signal)
                                                │
0V ────── [Blue wire] ──── NPN Sensor (blue) ──┘ (transistor pulls to 0V)

PNP Output: Current Sourcing (Pull to +24V)

A PNP sensor contains a PNP transistor in the output stage. When the sensor detects a target, the transistor turns ON and connects the signal (black) wire to the +24V (brown) wire internally. The signal wire is pulled HIGH — it reads approximately +24V.

When the sensor is NOT detecting: the transistor is OFF, the signal wire floats low (or is pulled low by the PLC input circuit). This is the OFF state.

Who uses PNP sensors: European and North American manufacturers (Siemens, Balluff, ifm, Turck, Rockwell, Banner in standard configurations). PNP sensors are the default in Western European and North American industrial practice.

How to wire a PNP sensor to a PLC input:

The PLC input circuit must provide a return path from the input to 0 V—commonly described as a sinking input, with the input common at 0 V. When the PNP sensor drives the signal wire to +24 V, current flows into the input and the module registers ON. Confirm the terminal diagram because naming conventions vary.

+24V ──── [Brown wire] ──── PNP Sensor (brown) ──┐ (transistor switches)
                                                   │
+24V ────                   [Black wire] ──── PLC Input ──── PLC COM ──── 0V
                             PNP Sensor (black signal)                 (PLC sinks current)

0V ────── [Blue wire] ──── PNP Sensor (blue)

The Mismatch Trap

What happens when you wire an NPN sensor to an input bank whose common is at 0 V—the wrong current path?

The NPN sensor pulls the black wire to 0V when it detects. The PLC input module is also connected to 0V on its common. When the sensor activates, both the signal wire and the common are at 0V. There is no voltage difference across the input — the PLC sees nothing. The input stays permanently OFF regardless of what the sensor detects.

The reverse mistake—PNP sensor into an input bank whose common is at +24 V—has the same result: both sides of the input are near +24 V when the sensor activates, so no useful current flows and the input stays off.

NPN vs PNP sensor mismatch — why the input never turns on

How to Identify Your Sensor Output Type

From the datasheet: look for "output type" or "switching output." You will see one of: NPN, NPN/NO, NPN-NO, DC NPN, sinking, open collector to 0V, PNP, PNP/NO, PNP-NO, DC PNP, sourcing, solid-state, high-side.

From the part number: most manufacturers encode the output type in the part number. "-1" suffix often means PNP; "-2" means NPN (Balluff, ifm). "P" in the part number usually means PNP. Check the catalogue coding key.

With a meter: connect brown to +24V and blue to 0V. Point the sensor at a target. Measure voltage on the black wire:

  • Black goes to ~0V → NPN
  • Black goes to ~+24V → PNP

How to Identify Your PLC Input Module Type

From the module datasheet: look for "input type," "wiring diagram," or "COM terminal." If the common terminal (COM) connects to +24V in the wiring diagram → sourcing input (use with NPN sensors). If COM connects to 0V → sinking input (use with PNP sensors).

Allen-Bradley: Capability varies by catalog number. Some isolated ControlLogix input modules document both sink-input and source-input wiring, while many other modules have a fixed topology. Use the wiring diagram for the full catalog number; do not generalize from the 1769 or 1756 family name.

Siemens S7-1200/1500: Common 24 V DC digital-input configurations use M/0 V as the input reference and are paired with PNP field devices that supply +24 V when active. Exact CPUs, signal modules, failsafe modules and wiring modes differ, so verify the device manual before landing an NPN sensor.

From the module label: look for "Type 1 IEC" or "Type 3 IEC" — these describe the input circuit topology but you still need the wiring diagram to confirm NPN/PNP compatibility.

Sensors with Selectable NPN/PNP

Many modern sensors offer a selectable output mode via a DIP switch or configuration tool. On Keyence sensors and some Sick models, a small switch on the body selects NPN or PNP. Check the datasheet — this feature eliminates the sourcing/sinking mismatch problem and is worth specifying when buying sensors for a new machine.

NO vs NC Output

Both NPN and PNP sensors come in Normally Open (NO) and Normally Closed (NC) variants — and some sensors switch between NO and NC via a DIP switch. This is separate from NPN/PNP:

  • NO (Normally Open): signal wire is OFF (not active) when no target detected; turns ON when target detected. The most common configuration.
  • NC (Normally Closed): signal wire is ON when no target is detected and turns OFF when the target is detected. This can help a control system notice some open-circuit faults, but the meaning depends on the application and program.

An ordinary NC proximity sensor is not automatically a safety device. Guarding and hazard-zone functions require the risk assessment, safety-rated sensor, monitored wiring, safety controller or relay, diagnostic coverage, and architecture specified for the required performance level. A single NC signal can still leave faults ambiguous.

Frequently Asked Questions

Q: Can I use an NPN sensor with an input bank wired for PNP sensors?

A: Not directly if the module topology is fixed. Use an approved interface relay or signal converter, choose a compatible input module, or rewire a genuinely dual-topology bank exactly as its manual allows. The simplest design-stage solution is to match the sensor output to the module's documented current path.

Q: Is NPN or PNP better?

A: Neither is universally better. PNP (sourcing) is the European/North American standard and matches most Western PLC modules in their default wiring. NPN (sinking) is the Asian standard and is common in equipment from Japan, Korea, and China. The only correct answer is: match the sensor output type to the PLC input type for your specific module.

Q: Why does my sensor light up but the PLC input stays off?

A: The LED indicator on a sensor lights when the sensor's output transistor activates — it is driven from the sensor supply, not from the PLC. So the LED can be on while the PLC input is off. The most likely cause is NPN/PNP mismatch. Verify with a multimeter: measure the voltage on the signal (black) wire relative to 0V when the sensor LED is on. If it reads 0V on an NPN sensor and your module expects PNP, you have a mismatch.

Q: I have a 2-wire sensor. Does NPN/PNP apply?

A: 2-wire sensors (load-powered sensors, no separate supply wire) are wired in series with the PLC input circuit like a switch. The concept of NPN/PNP does not directly apply, but 2-wire sensors still have a polarity — connect them per the wiring diagram. 2-wire sensors have a voltage drop when on (typically 2–8V) and a leakage current when off — check that the PLC input module's leakage tolerance and minimum on-voltage are compatible.


Put the wiring into practice: work through the interactive PLC wiring lessons, then create a free account to save progress and continue into sensor-driven scenarios. No card is required.

Learn more about the discrete sensors that use NPN/PNP output:

ShareX / TwitterLinkedIn

From reading to running logic

Practice this yourself in the simulator

Start with guided PLC practice in your browser. No install and no credit card required.

Start practising free

Continue learning

Related field notes

All articles
electrical
motor control

Motor Starter vs VFD: When Direct-On-Line Is Enough and When It Is Not

Motor starter vs VFD compared: DOL starting vs variable speed, energy savings, starting current, soft start, mechanical wear, and when the extra cost of a VFD is justified.

9 min read
electrical
motor control

Motor Starter vs Contactor: What the Overload Relay Actually Adds

A motor starter is a contactor plus an overload relay. This post explains what the overload adds, when you need a full starter vs a bare contactor, how the PLC interlocks with both, and wiring to the control circuit.

8 min read
communications
profinet

PROFINET vs EtherNet/IP: Choosing the Right Industrial Ethernet Protocol

PROFINET vs EtherNet/IP: Siemens vs Rockwell, IRT real-time classes vs CIP motion, conformance levels, cable topology, and where Modbus TCP fits when you need something simpler.

10 min read

Software evaluation field guide

NPN versus PNP sensors: implementation, evidence and troubleshooting

Direct answer

NPN versus PNP sensors becomes useful when it connects supply voltage, sensor output type, wire colors and pinout, plc input circuit, input common, load current, leakage, cable, environment and failure state with target detection through transistor output and conventional current path to plc input voltage, logic tag and control response, then proves sensor clear and detected states checked at sensor output, input terminal, module indicator and plc tag under normal, boundary, fault and recovery conditions. The objective is a repeatable engineering or learning result, not merely activity inside a page or tool.

This guide is written for electrical, instrumentation and PLC learners wiring three-wire DC sensors to compatible controller inputs and diagnosing polarity or common-reference errors. The intended result is specific: the reader can trace conventional current, identify sourcing and sinking sides, match the sensor to the input and predict measurements in on and off states.

an instrumentation engineer correlating a process skid, transmitter, calibrator, PLC trend and actuator response while studying NPN sinking and PNP sourcing sensor interfaces
The physical context keeps NPN sinking and PNP sourcing sensor interfaces tied to declared inputs, owned decisions, observable results and evidence that another person can verify.

System map / 02

Six concepts that control the result

Treat these as connected checkpoints. Each checkpoint has an expected state, an observable state and a boundary to the next part of the system. That structure prevents a software indication from being mistaken for physical proof.

NODE 01observable

Define the operating contract

supply voltage, sensor output type, wire colors and pinout, PLC input circuit, input common, load current, leakage, cable, environment and failure state. For NPN sinking and PNP sourcing sensor interfaces, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation.

NODE 02observable

Map the evidence path

target detection through transistor output and conventional current path to PLC input voltage, logic tag and control response. Separate request, internal state, output or service, physical or user-visible result and independent feedback so each boundary can be inspected.

NODE 03observable

Prove normal operation

sensor clear and detected states checked at sensor output, input terminal, module indicator and PLC tag. Run more than one cycle from a known state and retain the values, timings or artifacts that demonstrate repeatability.

NODE 04observable

Exercise a boundary case

reversed polarity, wrong common, mismatched sourcing, leakage ghosting, voltage drop, short circuit, broken conductor and shared reference. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path.

NODE 05observable

Diagnose a controlled fault

a target, sensor supply, transistor, conductor, common, input circuit, threshold, tag or logic defect. Preserve the first symptom, divide the system at a measurable boundary and change one condition only after predicting the result.

NODE 06observable

Transfer and hand over

the interface verified from current data sheets and tested under representative cable, load and environmental conditions. Restore normal state, remove temporary changes, repeat affected checks and document which claims remain limited to the learning environment.

Procedure / 03

A six-step practice and commissioning workflow

Run the steps in order the first time. Later, the same structure becomes a diagnostic loop: define the expected condition, observe the boundary, interpret the difference and choose one proving action.

  1. 01

    Write the acceptance case

    Convert supply voltage, sensor output type, wire colors and pinout, plc input circuit, input common, load current, leakage, cable, environment and failure state into initial conditions, one stimulus and observable pass criteria.

    Evidence: Another person can repeat the case without guessing the intended result.

    Avoid: Using page completion or an animation as the acceptance criterion.

  2. 02

    Build the map

    Document target detection through transistor output and conventional current path to plc input voltage, logic tag and control response and name who owns each state or decision.

    Evidence: Every request and result has a source, destination and useful inspection point.

    Avoid: Using the same value as command, status and independent feedback.

  3. 03

    Run the baseline

    Apply sensor clear and detected states checked at sensor output, input terminal, module indicator and plc tag from a clean start and record the expected evidence.

    Evidence: Repeated runs produce the same bounded result.

    Avoid: Changing several parameters before a baseline exists.

  4. 04

    Challenge assumptions

    Test reversed polarity, wrong common, mismatched sourcing, leakage ghosting, voltage drop, short circuit, broken conductor and shared reference without changing the acceptance contract.

    Evidence: Limits, timing and restart behavior reach defined states.

    Avoid: Testing only one ideal sequence.

  5. 05

    Isolate one failure

    Introduce or analyse a target, sensor supply, transistor, conductor, common, input circuit, threshold, tag or logic defect and locate the first disagreement.

    Evidence: The proving action distinguishes the leading hypotheses.

    Avoid: Resetting, forcing or replacing before evidence is retained.

  6. 06

    Close the evidence loop

    Complete the interface verified from current data sheets and tested under representative cable, load and environmental conditions and repeat the affected regression cases.

    Evidence: An evaluation is complete when the same representative job is tested in each candidate and differences are recorded as evidence rather than inferred from feature labels.

    Avoid: Treating an acknowledged message or one successful rerun as handover.

Diagnostic matrix / 04

Symptoms, proving points and next actions

The table is a reasoning aid, not a parts-replacement chart. Preserve the initial symptom, inspect the named boundary and use the interpretation to choose the next controlled test. Site safety procedures and equipment manuals remain authoritative.

Diagnostic symptoms, inspection points, interpretations and next actions for NPN versus PNP sensors: implementation, evidence and troubleshooting
Observed symptomInspectInterpretationNext proving action
The expected result is unclearRequirement, initial state, actor, stimulus, units and pass conditionThe evaluator, instructor and technical buyer may be solving different versions of the task.Rewrite one observable acceptance case before continuing.
Internal state changes but the outcome does notRequest, final owner, output or service boundary and independent feedbackA software or interface indication proves intent at one layer, not the complete outcome.Trace the first boundary after the changing state.
Normal case passes but an edge case failsLimits, timing, simultaneous events, reset and restart assumptionsThe implementation contains a hidden assumption exposed by the changed condition.Add the failed boundary as a permanent regression case.
The failure disappears after resetOriginal symptom, histories, diagnostics, timestamps and active causeReset changed evidence or state without proving the initiating cause.Reproduce under a controlled condition and preserve pre/post-event data.
Simulator and target disagreeModel boundary, software version, task timing, I/O behavior, data types and configurationA learning model and the intended target do not share one of the recorded assumptions.Reduce the case and verify against current target documentation.
The result cannot be explainedPrediction, observation, proving action, alternative hypotheses and limitationsActivity occurred but the evidence is not yet transferable or reviewable.Have the learner defend the signal path and repeat a changed case.

Product evidence / 05

What the browser practice can actually demonstrate

The public product surface exposes runnable examples, capability boundaries, pricing context and test-harness behavior that can be checked before a purchasing decision.

Where simulation stops

Regional convention, input circuits, leakage, voltage, pinout and protection vary; always use current sensor and module diagrams before wiring.

Commissioning notebook / 06

Six cases that turn the concepts into evidence

Use these as written briefs rather than click-through instructions. For every case, state the expected condition before acting, retain the first useful observation and explain why the final result proves the requirement. A different program or component choice can still be correct when it produces the same bounded behavior and evidence.

Case 01

predict → observe → prove

Prove define the operating contract

Engineering context. supply voltage, sensor output type, wire colors and pinout, PLC input circuit, input common, load current, leakage, cable, environment and failure state. For NPN sinking and PNP sourcing sensor interfaces, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.

Controlled setup. Use the “Write the acceptance case” stage of the workflow: convert supply voltage, sensor output type, wire colors and pinout, plc input circuit, input common, load current, leakage, cable, environment and failure state into initial conditions, one stimulus and observable pass criteria. The acceptance record should show this result: another person can repeat the case without guessing the intended result. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.

Fault challenge. Introduce or analyse “The expected result is unclear” as one bounded deviation. Inspect requirement, initial state, actor, stimulus, units and pass condition The working interpretation is that the evaluator, instructor and technical buyer may be solving different versions of the task. The next proving action is to rewrite one observable acceptance case before continuing. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.

Review and recovery. The most common trap here is using page completion or an animation as the acceptance criterion. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.

Explain it aloud: What is the difference between NPN and PNP sensors? A defensible short answer is: A PNP output typically sources positive current to a sinking input, while an NPN output sinks current toward zero volts from a sourcing input.

Case 02

predict → observe → prove

Prove map the evidence path

Engineering context. target detection through transistor output and conventional current path to PLC input voltage, logic tag and control response. Separate request, internal state, output or service, physical or user-visible result and independent feedback so each boundary can be inspected. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.

Controlled setup. Use the “Build the map” stage of the workflow: document target detection through transistor output and conventional current path to plc input voltage, logic tag and control response and name who owns each state or decision. The acceptance record should show this result: every request and result has a source, destination and useful inspection point. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.

Fault challenge. Introduce or analyse “Internal state changes but the outcome does not” as one bounded deviation. Inspect request, final owner, output or service boundary and independent feedback The working interpretation is that a software or interface indication proves intent at one layer, not the complete outcome. The next proving action is to trace the first boundary after the changing state. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.

Review and recovery. The most common trap here is using the same value as command, status and independent feedback. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.

Explain it aloud: Can an NPN sensor connect to any PLC input? A defensible short answer is: No. The input circuit and common must be compatible with the sensor output, voltage, current and leakage characteristics.

Case 03

predict → observe → prove

Prove prove normal operation

Engineering context. sensor clear and detected states checked at sensor output, input terminal, module indicator and PLC tag. Run more than one cycle from a known state and retain the values, timings or artifacts that demonstrate repeatability. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.

Controlled setup. Use the “Run the baseline” stage of the workflow: apply sensor clear and detected states checked at sensor output, input terminal, module indicator and plc tag from a clean start and record the expected evidence. The acceptance record should show this result: repeated runs produce the same bounded result. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.

Fault challenge. Introduce or analyse “Normal case passes but an edge case fails” as one bounded deviation. Inspect limits, timing, simultaneous events, reset and restart assumptions The working interpretation is that the implementation contains a hidden assumption exposed by the changed condition. The next proving action is to add the failed boundary as a permanent regression case. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.

Review and recovery. The most common trap here is changing several parameters before a baseline exists. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.

Explain it aloud: What should I learn first about NPN sinking and PNP sourcing sensor interfaces? A defensible short answer is: Start with the operating contract and evidence path: supply voltage, sensor output type, wire colors and pinout, plc input circuit, input common, load current, leakage, cable, environment and failure state, followed by target detection through transistor output and conventional current path to plc input voltage, logic tag and control response. Add advanced features only after the baseline is predictable.

Case 04

predict → observe → prove

Prove exercise a boundary case

Engineering context. reversed polarity, wrong common, mismatched sourcing, leakage ghosting, voltage drop, short circuit, broken conductor and shared reference. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.

Controlled setup. Use the “Challenge assumptions” stage of the workflow: test reversed polarity, wrong common, mismatched sourcing, leakage ghosting, voltage drop, short circuit, broken conductor and shared reference without changing the acceptance contract. The acceptance record should show this result: limits, timing and restart behavior reach defined states. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.

Fault challenge. Introduce or analyse “The failure disappears after reset” as one bounded deviation. Inspect original symptom, histories, diagnostics, timestamps and active cause The working interpretation is that reset changed evidence or state without proving the initiating cause. The next proving action is to reproduce under a controlled condition and preserve pre/post-event data. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.

Review and recovery. The most common trap here is testing only one ideal sequence. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.

Explain it aloud: How do I practise NPN sinking and PNP sourcing sensor interfaces effectively? A defensible short answer is: Use short cases with known initial conditions, a written prediction, one action and an observable result. Then alter a boundary or fault and explain why the evidence changed.

Case 05

predict → observe → prove

Prove diagnose a controlled fault

Engineering context. a target, sensor supply, transistor, conductor, common, input circuit, threshold, tag or logic defect. Preserve the first symptom, divide the system at a measurable boundary and change one condition only after predicting the result. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.

Controlled setup. Use the “Isolate one failure” stage of the workflow: introduce or analyse a target, sensor supply, transistor, conductor, common, input circuit, threshold, tag or logic defect and locate the first disagreement. The acceptance record should show this result: the proving action distinguishes the leading hypotheses. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.

Fault challenge. Introduce or analyse “Simulator and target disagree” as one bounded deviation. Inspect model boundary, software version, task timing, I/O behavior, data types and configuration The working interpretation is that a learning model and the intended target do not share one of the recorded assumptions. The next proving action is to reduce the case and verify against current target documentation. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.

Review and recovery. The most common trap here is resetting, forcing or replacing before evidence is retained. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.

Explain it aloud: What counts as proof of competence? A defensible short answer is: A repeatable artifact or system result plus an explanation of the signal path is stronger than time spent, screenshots or a copied answer. Physical competence requires separate supervised evidence.

Case 06

predict → observe → prove

Prove transfer and hand over

Engineering context. the interface verified from current data sheets and tested under representative cable, load and environmental conditions. Restore normal state, remove temporary changes, repeat affected checks and document which claims remain limited to the learning environment. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.

Controlled setup. Use the “Close the evidence loop” stage of the workflow: complete the interface verified from current data sheets and tested under representative cable, load and environmental conditions and repeat the affected regression cases. The acceptance record should show this result: an evaluation is complete when the same representative job is tested in each candidate and differences are recorded as evidence rather than inferred from feature labels. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.

Fault challenge. Introduce or analyse “The result cannot be explained” as one bounded deviation. Inspect prediction, observation, proving action, alternative hypotheses and limitations The working interpretation is that activity occurred but the evidence is not yet transferable or reviewable. The next proving action is to have the learner defend the signal path and repeat a changed case. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.

Review and recovery. The most common trap here is treating an acknowledged message or one successful rerun as handover. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.

Explain it aloud: Why test faults and restart behavior? A defensible short answer is: Because a target, sensor supply, transistor, conductor, common, input circuit, threshold, tag or logic defect or reversed polarity, wrong common, mismatched sourcing, leakage ghosting, voltage drop, short circuit, broken conductor and shared reference can expose assumptions that never appear during ideal startup and steady operation.

Answer surface / 07

Questions people ask about NPN versus PNP sensors

These concise answers define the operating, training and product boundaries most often missed in broad summaries. The full workflow and diagnostic table above provide the evidence behind them.

What is the difference between NPN and PNP sensors?

A PNP output typically sources positive current to a sinking input, while an NPN output sinks current toward zero volts from a sourcing input.

Can an NPN sensor connect to any PLC input?

No. The input circuit and common must be compatible with the sensor output, voltage, current and leakage characteristics.

What should I learn first about NPN sinking and PNP sourcing sensor interfaces?

Start with the operating contract and evidence path: supply voltage, sensor output type, wire colors and pinout, plc input circuit, input common, load current, leakage, cable, environment and failure state, followed by target detection through transistor output and conventional current path to plc input voltage, logic tag and control response. Add advanced features only after the baseline is predictable.

How do I practise NPN sinking and PNP sourcing sensor interfaces effectively?

Use short cases with known initial conditions, a written prediction, one action and an observable result. Then alter a boundary or fault and explain why the evidence changed.

What counts as proof of competence?

A repeatable artifact or system result plus an explanation of the signal path is stronger than time spent, screenshots or a copied answer. Physical competence requires separate supervised evidence.

Why test faults and restart behavior?

Because a target, sensor supply, transistor, conductor, common, input circuit, threshold, tag or logic defect or reversed polarity, wrong common, mismatched sourcing, leakage ghosting, voltage drop, short circuit, broken conductor and shared reference can expose assumptions that never appear during ideal startup and steady operation.

Can browser practice replace official software or hardware?

No. It can build concepts and diagnostic reasoning. Exact firmware, I/O electrical behavior, networking, safety and commissioning require current official tools, documentation and target equipment.

How should progress be documented?

Keep the requirement, initial state, program or configuration, observed values, fault hypothesis, proving action, recovery result and a concise limitations statement.

Continue the signal path / 08

Related practice and reference pages