PLC Simulator
← Back to all lessons
Wiring 2
Free

Wiring 2 — NPN / PNP Sensors (Sinking & Sourcing)

What you'll learn

Industrial 3-wire DC proximity sensors normally use this IEC colour convention (always verify the device datasheet):

Lab time: ~12 minutes.

Lesson briefing

NPN / PNP Sensors — Sinking & Sourcing

Industrial 3-wire DC proximity sensors normally use this IEC colour convention (always verify the device datasheet):

  • Brown (BN) — 24 VDC supply positive.
  • Blue (BU) — 0 V / DC common.
  • Black (BK) — signal output to the PLC input.

The supply wiring (BN and BU) is identical for both NPN and PNP sensors. The only difference is what the black wire does when the sensor detects a target. In the panel wiring that you add in this lab, use red for +24 V, blue for 0 V, black for signal/control, and green/yellow for PE. The brown/blue/black colours above describe the sensor's factory-fitted cable.

NPN — sinking output

When an NPN sensor is active, its output transistor connects the black wire to 0 V: it sinks current. A compatible sourcing PLC input supplies current through its input circuit and the NPN output to 0 V, so that input channel turns ON.

PNP — sourcing output

When a PNP sensor is active, its output transistor sources +24 V onto the black wire. A compatible sinking PLC input returns that current to 0 V, so the input channel turns ON. PNP sensors are common with modern positive-logic IEC control systems.

Wiring both onto the same PLC

This training PLC models X0 as a sourcing input for the NPN sensor and X1 as a sinking input for the PNP sensor. Both sensors share the same +24 V and 0 V distribution buses, and their black wires land on those separate channels.

A real fixed-common input module often cannot mix NPN and PNP devices in one common group. Use separate configurable input groups, a universal input module, or an interface relay as the manufacturer's wiring diagram requires. Never assume that a PLC "handles either" polarity automatically.

Practical tip: always read the sensor nameplate before wiring. A polarity mismatch can let the sensor LED operate while the PLC input never turns on. Also bond DC common to PE only when the machine's documented SELV/PELV and grounding design explicitly requires it.

Hints

Hint 1

Brown wire (+V terminal) always connects to the +24 V supply bus — this is true for both NPN and PNP sensors.

Hint 2

Sign up to unlock the full hint sequence.

Hint 3

Sign up to unlock the full hint sequence.

Hint 4

Sign up to unlock the full hint sequence.

Hint 5

Sign up to unlock the full hint sequence.

This lesson uses 8 placed components on the lab canvas. Components are vendor-neutral (no proprietary trademarks); the wiring rules apply to any equivalent industrial part.

Sign up free to start

This foundation lab is included on Free — sign up takes a minute.

Sign up free to start →

You might also like

Fault 1 — Photoeye Polarity Reversal
Fault 2 — Relay Contact Card Swap
Fault 3 — Rail Short at the Terminal Block

Competency and practice field guide

PLC sourcing and sinking wiring lesson: implementation, evidence and troubleshooting

Direct answer

PLC sourcing and sinking wiring lesson becomes useful when it connects supply polarity, source, load, sink, pnp transistor, npn transistor, input circuit, common terminal, leakage, threshold, conductor function and normal state with positive supply through sourcing element, plc input or load and sinking element to 0 v with corresponding device indication and software state, then proves each target-present and target-absent state produces the predicted current path, input voltage and tag value 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 pLC wiring beginners connecting three-wire sensors and transistor outputs to compatible input and output circuits. The intended result is specific: the learner can draw conventional current from positive to return, identify which side sources and sinks it and wire compatible commons without relying on color alone.

a supervised industrial electrical bench used to trace 24 VDC control power, terminals, relay contacts and PLC I/O with a correctly selected meter while studying PNP, NPN, sourcing and sinking current paths
The scene connects PNP, NPN, sourcing and sinking current paths to declared conditions, safe boundaries, observable evidence and a repeatable result.

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 polarity, source, load, sink, PNP transistor, NPN transistor, input circuit, common terminal, leakage, threshold, conductor function and normal state. For PNP, NPN, sourcing and sinking current paths, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation.

NODE 02observable

Map the evidence path

positive supply through sourcing element, PLC input or load and sinking element to 0 V with corresponding device indication and software state. 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

each target-present and target-absent state produces the predicted current path, input voltage and tag value. 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

wrong common, PNP-to-PNP mismatch, NPN-to-NPN mismatch, reversed supply, open signal, leakage, shared supply, short and power return. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path.

NODE 05observable

Diagnose a controlled fault

a terminology, supply, polarity, transistor, common, wiring, threshold, channel or tag-interpretation mismatch. 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

compatibility verified from current schematics and tested with the intended module and device. 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 polarity, source, load, sink, pnp transistor, npn transistor, input circuit, common terminal, leakage, threshold, conductor function and normal 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 positive supply through sourcing element, plc input or load and sinking element to 0 v with corresponding device indication and software state 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 each target-present and target-absent state produces the predicted current path, input voltage and tag value 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 wrong common, pnp-to-pnp mismatch, npn-to-npn mismatch, reversed supply, open signal, leakage, shared supply, short and power return 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 terminology, supply, polarity, transistor, common, wiring, threshold, channel or tag-interpretation mismatch 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 compatibility verified from current schematics and tested with the intended module and device and repeat the affected regression cases.

    Evidence: A learner completes the surface by explaining the result, passing a changed case and identifying what still requires supervised target-equipment practice.

    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 PLC sourcing and sinking wiring lesson: implementation, evidence and troubleshooting
Observed symptomInspectInterpretationNext proving action
The expected result is unclearRequirement, initial state, actor, stimulus, units and pass conditionThe learner, instructor and assessor 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 browser platform can retain programs, scenario results, attempts and observable machine state so practice is attached to evidence rather than seat time alone.

Where simulation stops

Terminology and circuit details vary by manufacturer and region; the lesson cannot guarantee compatibility without exact device and module diagrams.

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 polarity, source, load, sink, PNP transistor, NPN transistor, input circuit, common terminal, leakage, threshold, conductor function and normal state. For PNP, NPN, sourcing and sinking current paths, 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 polarity, source, load, sink, pnp transistor, npn transistor, input circuit, common terminal, leakage, threshold, conductor function and normal 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 learner, instructor and assessor 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 sourcing and sinking? A defensible short answer is: A sourcing side supplies conventional current toward a load; a sinking side provides the return path toward the lower potential.

Case 02

predict → observe → prove

Prove map the evidence path

Engineering context. positive supply through sourcing element, PLC input or load and sinking element to 0 V with corresponding device indication and software state. 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 positive supply through sourcing element, plc input or load and sinking element to 0 v with corresponding device indication and software state 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: Is PNP always sourcing? A defensible short answer is: A PNP sensor output is commonly described as sourcing current, but verify the complete device and input circuit instead of relying on a label alone.

Case 03

predict → observe → prove

Prove prove normal operation

Engineering context. each target-present and target-absent state produces the predicted current path, input voltage and tag value. 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 each target-present and target-absent state produces the predicted current path, input voltage and tag value 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 PNP, NPN, sourcing and sinking current paths? A defensible short answer is: Start with the operating contract and evidence path: supply polarity, source, load, sink, pnp transistor, npn transistor, input circuit, common terminal, leakage, threshold, conductor function and normal state, followed by positive supply through sourcing element, plc input or load and sinking element to 0 v with corresponding device indication and software state. Add advanced features only after the baseline is predictable.

Case 04

predict → observe → prove

Prove exercise a boundary case

Engineering context. wrong common, PNP-to-PNP mismatch, NPN-to-NPN mismatch, reversed supply, open signal, leakage, shared supply, short and power return. 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 wrong common, pnp-to-pnp mismatch, npn-to-npn mismatch, reversed supply, open signal, leakage, shared supply, short and power return 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 PNP, NPN, sourcing and sinking current paths 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 terminology, supply, polarity, transistor, common, wiring, threshold, channel or tag-interpretation mismatch. 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 terminology, supply, polarity, transistor, common, wiring, threshold, channel or tag-interpretation mismatch 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. compatibility verified from current schematics and tested with the intended module and device. 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 compatibility verified from current schematics and tested with the intended module and device and repeat the affected regression cases. The acceptance record should show this result: a learner completes the surface by explaining the result, passing a changed case and identifying what still requires supervised target-equipment practice. 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 terminology, supply, polarity, transistor, common, wiring, threshold, channel or tag-interpretation mismatch or wrong common, pnp-to-pnp mismatch, npn-to-npn mismatch, reversed supply, open signal, leakage, shared supply, short and power return can expose assumptions that never appear during ideal startup and steady operation.

Answer surface / 07

Questions people ask about PLC sourcing and sinking wiring lesson

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 sourcing and sinking?

A sourcing side supplies conventional current toward a load; a sinking side provides the return path toward the lower potential.

Is PNP always sourcing?

A PNP sensor output is commonly described as sourcing current, but verify the complete device and input circuit instead of relying on a label alone.

What should I learn first about PNP, NPN, sourcing and sinking current paths?

Start with the operating contract and evidence path: supply polarity, source, load, sink, pnp transistor, npn transistor, input circuit, common terminal, leakage, threshold, conductor function and normal state, followed by positive supply through sourcing element, plc input or load and sinking element to 0 v with corresponding device indication and software state. Add advanced features only after the baseline is predictable.

How do I practise PNP, NPN, sourcing and sinking current paths 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 terminology, supply, polarity, transistor, common, wiring, threshold, channel or tag-interpretation mismatch or wrong common, pnp-to-pnp mismatch, npn-to-npn mismatch, reversed supply, open signal, leakage, shared supply, short and power return 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

NPN versus PNP sensorsContinue from supply polarity, source, load, sink, pnp transistor, npn transistor, input circuit, common terminal, leakage, threshold, conductor function and normal state.NPN polarity faultContinue from positive supply through sourcing element, plc input or load and sinking element to 0 v with corresponding device indication and software state.PLC wiring simulatorContinue from each target-present and target-absent state produces the predicted current path, input voltage and tag value.Photoeye guideContinue from wrong common, pnp-to-pnp mismatch, npn-to-npn mismatch, reversed supply, open signal, leakage, shared supply, short and power return.Explore modbus exception 04 server-device failure guideContinue from a terminology, supply, polarity, transistor, common, wiring, threshold, channel or tag-interpretation mismatch.PLC training in Singapore evaluation guide field guideContinue from compatibility verified from current schematics and tested with the intended module and device.

Motor, wiring and VFD path

Connect the control command to physical motor behavior

Move from safe control wiring and contactors into VFD parameters, measurements, faults and PLC command paths.