PLC Simulator
PLC field notessensors

How Does an Inductive Proximity Sensor Work? (PLC Wiring + Programming Guide)

How inductive proximity sensors detect metal targets using electromagnetic fields, how to wire PNP and NPN types to a PLC input, and how to use them in ladder logic programs.

PLC Simulation Software8 min read

Inductive proximity sensors are the most common discrete sensor in industrial automation. If there is a metal part moving past a detection point — a shaft rotating, a part on a conveyor, a piston at end of travel — there is almost certainly an inductive proximity sensor counting or confirming it.

Understanding how they work, how to wire them, and how to use their signal in a PLC program is a foundational skill for any automation technician.

How an inductive proximity sensor works: oscillator and coil build an electromagnetic field, a metal target induces eddy currents that damp the oscillation and switch the NPN or PNP output

The Operating Principle

An inductive proximity sensor generates an alternating electromagnetic field from an internal coil (the "active face" or sensing face). When a metallic target enters this field, eddy currents are induced in the surface of the target. These eddy currents absorb energy from the sensor's oscillating circuit, which reduces the oscillation amplitude — a change the sensor's electronics detects and converts to a switching output.

No contact with the target is required. The sensing happens entirely through the electromagnetic field.

Block diagram of how an inductive proximity sensor works: oscillator and coil generate a field, a metal target entering the field induces eddy currents, the oscillation amplitude drops, the trigger stage fires and the NPN or PNP switching output turns on

Key characteristics:

  • Only detects metal (ferrous metals at full range; aluminium, copper, and other non-ferrous metals at reduced range — typically 50–80% of the rated sensing distance)
  • Not affected by dirt, oil, or coolant (the sensing face can be completely submerged in most cases)
  • Very long service life — no moving parts
  • Typical sensing distances: 2mm to 40mm for standard sizes; up to 80mm for specialised large-face models
  • Standard bore sizes: M8, M12, M18, M30 (the number is the thread diameter in mm)

NPN vs PNP Output Types

This is where most beginners get confused. Every proximity sensor is either NPN (sinking) or PNP (sourcing), and you must match the sensor output type to your PLC input type. The terms describe which supply rail the output switches: an NPN sensor switches the 0V (negative) side and sinks current, while a PNP sensor switches the +24V (positive) side and sources current.

NPN vs PNP proximity sensor comparison table showing which rail each output switches, sinking vs sourcing current, the matching PLC input type, output wire state when active, and the regional convention

The two diagrams below show exactly how the current flows in each case so you can match the sensor to your PLC input card.

Sinking versus sourcing explained: an NPN sinking sensor switches the 0V side with current flowing into the sensor, while a PNP sourcing sensor switches the +24V side with current flowing out of the sensor to a sourcing PLC input

PNP (sourcing) sensors

A PNP sensor's output switches the positive supply voltage (+24V DC) to the signal wire when an object is detected. The output sources current.

Wiring: Brown → +24V, Blue → 0V, Black (output) → PLC input terminal

When the PNP sensor detects a target, it connects +24V to the PLC input → the input reads logic HIGH (TRUE).

PNP sourcing proximity sensor wiring diagram: the sensor output sources +24V to a sourcing PLC input, which returns current to the 0V common, with brown to +24V and blue to 0V

NPN (sinking) sensors

An NPN sensor's output connects the signal wire to 0V (common) when an object is detected. The output sinks current.

Wiring: Brown → +24V, Blue → 0V, Black (output) → PLC input terminal

When the NPN sensor detects a target, it connects the input terminal to 0V → current flows from +24V through the PLC input, through the sensor → the input reads logic HIGH (TRUE).

NPN sinking proximity sensor wiring diagram: the sensor output switches to the 0V side and sinks current from a sinking PLC input fed by +24V, with brown to +24V and blue to 0V

Both types give you a logic HIGH at the PLC input when an object is detected — the difference is in how the current flows through the circuit.

Practical rule: Most European and Australian equipment uses PNP sensors. Most Japanese equipment uses NPN. North American practice is split. When in doubt, buy a sensor that specifies which output type it uses, match it to your PLC input card spec, and label the wiring clearly.

Flowchart for choosing NPN or PNP: decide whether the PLC input is sinking or sourcing, then pick an NPN sinking sensor for a sourcing input or a PNP sourcing sensor for a sinking input

Once you have the right type, follow this checklist to land the wiring safely.

Checklist for safely wiring an inductive proximity sensor to a PLC input: confirm the NPN or PNP output type, match it to the PLC input card, connect brown to +24V, blue to 0V and black to the input, share the 24V supply, power off before landing wires, and label the output type

Using a Proximity Sensor in Ladder Logic

Once the sensor is wired, its signal appears at a PLC digital input. In the program it is just a digital bit — TRUE when object detected, FALSE when no object present (for a normally-open output sensor).

Inductive proximity sensor detection timing diagram showing the metal target present signal, a PNP output that switches on with the target, and an NPN output that switches the opposite way

Parts counter example

(* Parts counter — increment CTU each time sensor detects a part *)
R_TRIG_0(CLK := Part_Sensor);   (* Rising edge detection *)
IF R_TRIG_0.Q THEN
    Part_Count := Part_Count + 1;
END_IF;

(* Reset counter on operator reset button *)
IF Reset_PB THEN
    Part_Count := 0;
END_IF;

Note the R_TRIG — edge detection is essential here. Without it, the counter would increment every scan while the sensor is blocked (20–50 counts per part). See Top 5 PLC Programming Mistakes for more on edge detection.

Conveyor jam detection example

(* Timer-based jam detection *)
(* If sensor does not see a part within 10 seconds, trigger alarm *)
TON_Jam(IN := Belt_Running AND NOT Part_Sensor, PT := T#10S);
Jam_Alarm := TON_Jam.Q;

If the belt is running but no parts are detected within 10 seconds, the timer expires and triggers the alarm.

Wiring Faults and How to Find Them

Proximity sensor faults are among the most common field problems. The fault injection module in the simulator includes sensor wiring faults so you can practise finding them.

Common sensor faults:

  1. Open circuit — broken wire, loose terminal. Input reads permanently FALSE. Motor won't start or counter stops incrementing.
  2. Short circuit — input reads permanently TRUE. Counter runs continuously, conveyor won't stop.
  3. Wrong output type — NPN sensor on PLC card expecting PNP (or vice versa). May read inverted or not at all depending on input card design.
  4. Sensing distance exceeded — target too far away. Signal may flicker at edge of range.
  5. Mutual interference — two identical sensors mounted too close together. One sensor's field affects the other's, causing false triggers.

Common inductive proximity sensor wiring faults and their PLC input symptoms: open circuit stuck FALSE, short circuit stuck TRUE, wrong NPN or PNP output type reading inverted, sensing distance exceeded causing flicker, and mutual interference causing false triggers

Use the fault diagnosis module in the simulator to practise finding all of these in a safe environment before you encounter them on an actual machine.

Try the Sensor School

The simulator's Sensor School has an interactive module specifically for inductive proximity sensors — including an animated cross-section showing the eddy-current effect, wiring diagrams for PNP and NPN types, and an exercise where you wire and program a sensor into a running conveyor simulation.


Practice with real sensor simulations — free. The sensor school includes inductive, photoelectric, capacitive, and pressure sensor exercises. All interactive, all in the browser.

Try the sensor school →

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
beginner
debugging

Top 5 PLC Programming Mistakes Beginners Make (and How to Fix Them)

The five most common PLC programming mistakes beginners make: wrong contact type, scan-cycle order bugs, latch coil misuse, timer preset errors, and ignoring edge detection. With examples.

8 min read
dialects
mitsubishi

Mitsubishi vs Allen-Bradley Ladder Logic: A Side-by-Side Guide

Comparing Mitsubishi GX Works and Allen-Bradley Studio 5000 ladder logic syntax, addressing schemes, and programming conventions. Which dialect should you learn first?

9 min read
tutorial
ladder logic

Traffic Light PLC Program: Ladder Logic Tutorial with Timers

Step-by-step traffic light PLC program. Design the Red→Green→Yellow→Red sequence with timers, build the I/O list, draw the state and timing diagrams, and wire the ladder logic — then run it in a free browser simulator.

9 min read

Technical reference and worked-example guide

How an inductive proximity sensor works: implementation, evidence and troubleshooting

Direct answer

How an inductive proximity sensor works becomes useful when it connects electromagnetic field, oscillator, metallic target, eddy currents, amplitude change, threshold, nominal range, correction factor, hysteresis, flush mounting, switching frequency and output type with target approach through field interaction and threshold circuit to transistor output, plc input, logic state and independently observed machine position, then proves representative targets are detected and released repeatedly across required distance, alignment, speed and environmental conditions 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 automation learners and technicians applying inductive proximity sensors to detect metallic targets. The intended result is specific: the reader can explain oscillator and eddy-current detection, relate target material and geometry to range and diagnose mounting, target, wiring and input faults.

an instrumentation calibration bench connecting pressure, temperature, load, level and smart sensors to PLC input channels and reference measurements while studying inductive sensing principle, target effects and PLC input evidence
The scene connects inductive sensing principle, target effects and PLC input evidence 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

electromagnetic field, oscillator, metallic target, eddy currents, amplitude change, threshold, nominal range, correction factor, hysteresis, flush mounting, switching frequency and output type. For inductive sensing principle, target effects and PLC input evidence, 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 approach through field interaction and threshold circuit to transistor output, PLC input, logic state and independently observed machine position. 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

representative targets are detected and released repeatedly across required distance, alignment, speed and environmental conditions. 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

nonferrous target, small target, recessed or nonflush mounting, nearby metal, chips, temperature, vibration, supply loss, leakage and restart. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path.

NODE 05observable

Diagnose a controlled fault

a target-material, geometry, range, mounting, environment, sensor, output, wiring, input or logic 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

the selected sensor verified with current specifications, actual bracket and representative target trials. 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 electromagnetic field, oscillator, metallic target, eddy currents, amplitude change, threshold, nominal range, correction factor, hysteresis, flush mounting, switching frequency and output type 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 approach through field interaction and threshold circuit to transistor output, plc input, logic state and independently observed machine position 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 representative targets are detected and released repeatedly across required distance, alignment, speed and environmental conditions 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 nonferrous target, small target, recessed or nonflush mounting, nearby metal, chips, temperature, vibration, supply loss, leakage and restart 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-material, geometry, range, mounting, environment, sensor, output, wiring, input or logic 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 the selected sensor verified with current specifications, actual bracket and representative target trials and repeat the affected regression cases.

    Evidence: Reference use is complete when inputs, assumptions, units or initial conditions are recorded and the result is independently checked at a useful boundary.

    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 How an inductive proximity sensor works: implementation, evidence and troubleshooting
Observed symptomInspectInterpretationNext proving action
The expected result is unclearRequirement, initial state, actor, stimulus, units and pass conditionThe technician, programmer and reviewer 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 page connects definitions and worked examples to runnable tools, explicit assumptions and repeatable checks so a formula or pattern can be challenged.

Where simulation stops

A general explanation cannot select an exact sensor or guarantee range, speed, environmental or hazardous-area performance; test the current device with representative targets.

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. electromagnetic field, oscillator, metallic target, eddy currents, amplitude change, threshold, nominal range, correction factor, hysteresis, flush mounting, switching frequency and output type. For inductive sensing principle, target effects and PLC input evidence, 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 electromagnetic field, oscillator, metallic target, eddy currents, amplitude change, threshold, nominal range, correction factor, hysteresis, flush mounting, switching frequency and output type 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 technician, programmer and reviewer 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 materials can an inductive proximity sensor detect? A defensible short answer is: It detects conductive metallic targets, with usable range affected by material, size, shape, orientation, mounting and the sensor design.

Case 02

predict → observe → prove

Prove map the evidence path

Engineering context. target approach through field interaction and threshold circuit to transistor output, PLC input, logic state and independently observed machine position. 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 approach through field interaction and threshold circuit to transistor output, plc input, logic state and independently observed machine position 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: Why does sensing distance change with stainless steel or aluminum? A defensible short answer is: Different target materials produce different eddy-current effects, so manufacturers publish correction factors or target-specific ranges.

Case 03

predict → observe → prove

Prove prove normal operation

Engineering context. representative targets are detected and released repeatedly across required distance, alignment, speed and environmental conditions. 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 representative targets are detected and released repeatedly across required distance, alignment, speed and environmental conditions 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 inductive sensing principle, target effects and PLC input evidence? A defensible short answer is: Start with the operating contract and evidence path: electromagnetic field, oscillator, metallic target, eddy currents, amplitude change, threshold, nominal range, correction factor, hysteresis, flush mounting, switching frequency and output type, followed by target approach through field interaction and threshold circuit to transistor output, plc input, logic state and independently observed machine position. Add advanced features only after the baseline is predictable.

Case 04

predict → observe → prove

Prove exercise a boundary case

Engineering context. nonferrous target, small target, recessed or nonflush mounting, nearby metal, chips, temperature, vibration, supply loss, leakage and restart. 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 nonferrous target, small target, recessed or nonflush mounting, nearby metal, chips, temperature, vibration, supply loss, leakage and restart 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 inductive sensing principle, target effects and PLC input evidence 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-material, geometry, range, mounting, environment, sensor, output, wiring, input or logic 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 target-material, geometry, range, mounting, environment, sensor, output, wiring, input or logic 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. the selected sensor verified with current specifications, actual bracket and representative target trials. 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 selected sensor verified with current specifications, actual bracket and representative target trials and repeat the affected regression cases. The acceptance record should show this result: reference use is complete when inputs, assumptions, units or initial conditions are recorded and the result is independently checked at a useful boundary. 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-material, geometry, range, mounting, environment, sensor, output, wiring, input or logic mismatch or nonferrous target, small target, recessed or nonflush mounting, nearby metal, chips, temperature, vibration, supply loss, leakage and restart can expose assumptions that never appear during ideal startup and steady operation.

Answer surface / 07

Questions people ask about How an inductive proximity sensor works

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 materials can an inductive proximity sensor detect?

It detects conductive metallic targets, with usable range affected by material, size, shape, orientation, mounting and the sensor design.

Why does sensing distance change with stainless steel or aluminum?

Different target materials produce different eddy-current effects, so manufacturers publish correction factors or target-specific ranges.

What should I learn first about inductive sensing principle, target effects and PLC input evidence?

Start with the operating contract and evidence path: electromagnetic field, oscillator, metallic target, eddy currents, amplitude change, threshold, nominal range, correction factor, hysteresis, flush mounting, switching frequency and output type, followed by target approach through field interaction and threshold circuit to transistor output, plc input, logic state and independently observed machine position. Add advanced features only after the baseline is predictable.

How do I practise inductive sensing principle, target effects and PLC input evidence 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-material, geometry, range, mounting, environment, sensor, output, wiring, input or logic mismatch or nonferrous target, small target, recessed or nonflush mounting, nearby metal, chips, temperature, vibration, supply loss, leakage and restart 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.