PLC Simulator
PLC field noteselectrical

Thermal Overload Relay: Wiring & Operation

See how a thermal overload relay protects a motor, how 95-96 and 97-98 work, what trip class means, and test it in an interactive PLC lab.

PLC Simulation Software12 min read

Direct answer: A thermal overload relay protects a motor from overheating during sustained overcurrent or phase loss. Motor current heats three bimetal elements. If the heat accumulates beyond the relay's calibrated limit, a trip mechanism opens the normally-closed 95–96 control contact, the contactor coil drops out, and the motor stops. It does not replace the short-circuit protection supplied by a fuse or circuit breaker.

Thermal overload relay with current-setting dial, trip button and three motor-current paths

That one paragraph explains the complete cause-and-effect chain, but a technician needs to understand each link: why the relay reacts slowly to a modest overload, why it reacts faster to a severe one, why the motor power does not pass through terminals 95 and 96, and why pressing Reset without finding the cause is poor fault-finding.

What a thermal overload relay protects

A motor overload is not the same fault as a short circuit.

Reference tableSwipe
ConditionTypical currentCorrect protection
Normal runningNear motor nameplate full-load currentNo trip
Mechanical overload, jam or failing bearingModerately above full-load current for seconds or minutesThermal/electronic overload relay
Phase lossHigh and unbalanced current in the remaining phasesPhase-sensitive overload relay
Short circuitExtremely high current in millisecondsFuse or circuit breaker

The overload relay is deliberately inverse-time: more current creates heat faster, so a larger overload trips sooner. This allows a motor's brief starting current without nuisance-tripping while still stopping a stalled or overworked motor before its windings exceed a safe temperature.

ABB describes thermal overload relays as motor-protection devices for overload and phase failure that combine with a contactor to form a starter. Schneider's trip-class guidance explains that the class must match the motor's starting characteristic, not a guess made at commissioning. See the primary references at the end of this guide.

What physically moves inside the relay

Cutaway of three heated bimetal paths bending as motor current rises

In a common three-pole thermal overload relay, each motor phase passes through a small heater associated with a bimetal strip. A bimetal is made from two bonded metals that expand at different rates. Heating makes the strip curve.

The sequence is:

  1. Motor current flows through all three power paths.
  2. Each path heats in proportion to current and time.
  3. The bimetal strips bend as their temperature rises.
  4. Their combined movement loads a mechanical trip bar.
  5. At the calibrated point, the mechanism snaps to the tripped state.
  6. The 95–96 contact opens and 97–98 closes.
  7. The open control circuit de-energises the contactor coil.

Mechanical trip linkage changing the overload relay auxiliary-contact state

The trip mechanism is normally snap-action rather than a contact that slowly drifts apart. That provides a decisive change of state and prevents the contactor coil from hovering at an uncertain voltage.

Electronic overload relays estimate the same thermal condition from current sensors and a digital model. They can add phase-loss, current-imbalance and communication diagnostics, but the system job remains the same: interrupt the contactor control circuit before sustained current damages the motor.

How the contactor and overload work together

Three-pole contactor mounted above a thermal overload relay in a motor starter

A direct-on-line motor starter is the combination of:

  • a short-circuit protective device upstream;
  • a contactor that switches motor power on command; and
  • an overload relay that decides when sustained motor current is unsafe.

The contactor handles frequent switching. The overload does not normally switch the motor's main current off by itself. Instead, its small NC auxiliary contact opens the coil circuit, causing the contactor's main poles to open together.

This separation is important. A PLC output may command the contactor coil, but a correctly designed overload contact can still remove that command path if the motor overheats. The PLC should also receive an overload status input so it can explain why the motor stopped and block an inappropriate restart.

What 95–96 and 97–98 mean

IEC overload relays commonly use these terminal numbers:

Reference tableSwipe
TerminalsNormal stateState after tripTypical job
95–96ClosedOpenWired in series with the contactor coil to stop the motor
97–98OpenClosedSignals OVERLOAD_TRIPPED to a PLC input or alarm lamp

The three large incoming/outgoing paths carry the motor current. The small 95–96 and 97–98 terminals are auxiliary contacts only. Do not confuse those two circuits.

A typical control path is:

+24 V → safety permissives → STOP (NC) → overload 95–96 (NC)
      → PLC/START command → contactor coil A1 → A2 → 0 V

The fault feedback is separate:

+24 V → overload 97–98 (NO) → PLC input OVERLOAD_TRIPPED

What the current dial changes

Overload relay current adjustment, trip indication and reset controls

The current dial calibrates the relay to the motor. It is commonly set from the motor nameplate current and the manufacturer's coordination instructions. It is not a convenient way to “make nuisance trips go away.” Turning the dial above the value required by the motor and installation can remove the protection the relay is meant to provide.

The correct setting depends on the specific relay, motor service factor, ambient compensation, wiring method and applicable standard. Use the relay and motor documentation; do not infer a universal percentage from an online example.

What trip class means

Trip class describes the relay's time characteristic at a stated multiple of its current setting. Schneider's North American guidance describes Class 10, 20 and 30 as tripping within approximately 10, 20 or 30 seconds respectively at six times the setting. IEC coordination uses defined curves and cold/hot starting conditions, so always read the exact relay data.

  • Class 10/10A: typical normal-starting motors.
  • Class 20: longer or heavier starts where the motor and application require it.
  • Class 30: very long acceleration duties, only when the coordinated design calls for it.

A slower trip class is not “better.” It permits more thermal energy during a start and must match the motor and load.

What happens during a real jam

Jammed conveyor motor heating while the thermal overload relay trips the starter

Suppose a conveyor bearing seizes. The PLC output remains true because the sequence still wants the conveyor to run. The motor slows or stalls and current rises. The overload's thermal state accumulates until it trips.

A robust PLC program should then:

  1. see the 97–98 overload input;
  2. remove the motor run command;
  3. latch a clear MOTOR_OVERLOAD diagnostic;
  4. prevent automatic restart;
  5. require the physical cause to clear and an intentional reset/acknowledgement; and
  6. detect a contactor that remained physically closed through auxiliary feedback.

The overload is field protection. The PLC logic supplies sequencing, explanation and restart discipline. Neither replaces the other.

Safe troubleshooting sequence

Safety: motor starters can contain lethal voltage and stored mechanical energy. Apply the site's isolation, lockout/tagout and verification procedure. The browser lab below is for learning; it is not permission to work live.

When an overload has tripped:

  1. Record what the machine was doing and whether the motor was starting, running or mechanically blocked.
  2. Inspect the trip indicator before disturbing the controls.
  3. Verify the overload setting against the motor and approved design.
  4. Check for a jam, tight bearing, blocked pump, phase loss, voltage imbalance or repeated starts.
  5. Allow a thermal device to cool for the manufacturer's required time.
  6. Reset only after the underlying condition is safe.
  7. Run under observation and compare phase currents rather than repeatedly pressing Reset.

Repeated trips are evidence, not an inconvenience to bypass.

Practise the complete cause-and-effect chain

The Thermal Overload lesson lets you energise a motor, raise its simulated load, watch the bimetal mechanism accumulate heat, see 95–96 open, and observe the contactor and PLC state change. The recognition content is public; the interactive cutaway and contextual AI tutor are Pro features.

Then apply it in the Motor Start/Stop scenario, where the overload is one permissive in a complete seal-in and fault-latch program.

Frequently asked questions

What is a thermal overload relay in plain English?

It is a reusable motor-protection device that estimates motor heating from current. When too much current flows for too long, it opens a small control contact that makes the contactor switch the motor off.

Does an overload relay protect against a short circuit?

No. Its response is intentionally slower so the motor can start. A fuse or circuit breaker provides short-circuit protection; the overload relay provides sustained-overcurrent protection.

Why is overload contact 95–96 normally closed?

The contact must conduct during healthy operation. A trip opens it and breaks the contactor coil circuit. That fail-to-open action is why 95–96 is placed in series with the coil command.

What is 97–98 used for?

It is normally open and closes when the overload trips. It is commonly wired to a PLC digital input or alarm indicator so the control system can state the real stop reason.

Can I reset an overload relay immediately?

Only after the device has cooled enough to reset and the cause has been made safe. A reset without diagnosis can restart a jammed, single-phasing or otherwise damaged motor.

Primary technical references

ShareX / TwitterLinkedIn

From reading to running logic

Watch the overload trip the motor starter

Open the component lesson, raise the simulated load and follow 95–96 from healthy to tripped before you build the PLC response.

Open the overload lesson

Continue learning

Related field notes

All articles
electrical troubleshooting
fault finding

Electrical Troubleshooting: A Systematic 7-Step Guide

Learn a repeatable electrical troubleshooting method: establish the safe energy state, read the schematic, half-split the circuit, interpret voltage patterns, diagnose common motor-control faults, and verify the repair.

13 min read
electrical
motor control

Motor Starter Wiring Diagram: DOL Circuit

Understand a DOL motor starter wiring diagram: breaker, contactor, overload, start/stop seal-in, PLC command and feedback—with a live lab.

14 min read
vfd
motor control

How a VFD Works: Rectifier to Motor

Follow power through a VFD from AC rectifier to DC bus and PWM inverter, then see how a PLC commands speed in an interactive motor lab.

13 min read

Technical reference and worked-example guide

Thermal overload relay guide: implementation, evidence and troubleshooting

Direct answer

Thermal overload relay guide becomes useful when it connects motor nameplate, service and load, current setting, trip class, ambient effect, phase sensitivity, auxiliary contact, reset mode, short-circuit protection and coordination with motor load through phase current and thermal model to trip mechanism, auxiliary circuit, contactor release, plc status, alarm and physical stop, then proves balanced rated operation followed by a controlled overload case with predictable trip and deliberate reset 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, maintenance and PLC learners interpreting overload settings, auxiliary contacts, motor current, trip class, reset and starter behavior. The intended result is specific: the reader can distinguish overload protection from short-circuit protection and diagnose a trip using current, phase, load and control-circuit evidence.

an instructor and adult learner tracing contactors, protection, emergency stopping and actuator response in a guarded diagnostic cell while studying motor thermal-overload protection, trips and control response
The scene keeps motor thermal-overload protection, trips and control response attached to declared conditions, observable results, diagnostic boundaries and evidence another person can reproduce.

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

motor nameplate, service and load, current setting, trip class, ambient effect, phase sensitivity, auxiliary contact, reset mode, short-circuit protection and coordination. For motor thermal-overload protection, trips and control response, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation.

NODE 02observable

Map the evidence path

motor load through phase current and thermal model to trip mechanism, auxiliary circuit, contactor release, PLC status, alarm and physical stop. 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

balanced rated operation followed by a controlled overload case with predictable trip and deliberate reset. 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

phase loss, repeated starts, high ambient, jam, low voltage, cooling failure, manual reset, remote reset 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 load, supply, phase, setting, thermal, device, auxiliary-contact, control, reset or mechanical 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

settings and coordination verified by qualified personnel using current motor, starter and protective-device documentation. 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 motor nameplate, service and load, current setting, trip class, ambient effect, phase sensitivity, auxiliary contact, reset mode, short-circuit protection and coordination 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 motor load through phase current and thermal model to trip mechanism, auxiliary circuit, contactor release, plc status, alarm and physical stop 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 balanced rated operation followed by a controlled overload case with predictable trip and deliberate reset 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 phase loss, repeated starts, high ambient, jam, low voltage, cooling failure, manual reset, remote reset 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 load, supply, phase, setting, thermal, device, auxiliary-contact, control, reset or mechanical 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 settings and coordination verified by qualified personnel using current motor, starter and protective-device documentation 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 Thermal overload relay guide: 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 guide cannot select protection, conductor sizes, trip class, coordination, reset policy or motor settings for a real installation.

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. motor nameplate, service and load, current setting, trip class, ambient effect, phase sensitivity, auxiliary contact, reset mode, short-circuit protection and coordination. For motor thermal-overload protection, trips and control response, 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 motor nameplate, service and load, current setting, trip class, ambient effect, phase sensitivity, auxiliary contact, reset mode, short-circuit protection and coordination 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 does a thermal overload relay protect? A defensible short answer is: It is intended to protect a motor circuit from sustained overload and related conditions; it does not replace required short-circuit protection.

Case 02

predict → observe → prove

Prove map the evidence path

Engineering context. motor load through phase current and thermal model to trip mechanism, auxiliary circuit, contactor release, PLC status, alarm and physical stop. 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 motor load through phase current and thermal model to trip mechanism, auxiliary circuit, contactor release, plc status, alarm and physical stop 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 an overload relay keep tripping? A defensible short answer is: Possible causes include excessive mechanical load, phase loss, voltage imbalance, repeated starts, poor cooling, incorrect setting or a motor fault; preserve current evidence before resetting.

Case 03

predict → observe → prove

Prove prove normal operation

Engineering context. balanced rated operation followed by a controlled overload case with predictable trip and deliberate reset. 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 balanced rated operation followed by a controlled overload case with predictable trip and deliberate reset 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 motor thermal-overload protection, trips and control response? A defensible short answer is: Start with the operating contract and evidence path: motor nameplate, service and load, current setting, trip class, ambient effect, phase sensitivity, auxiliary contact, reset mode, short-circuit protection and coordination, followed by motor load through phase current and thermal model to trip mechanism, auxiliary circuit, contactor release, plc status, alarm and physical stop. Add advanced features only after the baseline is predictable.

Case 04

predict → observe → prove

Prove exercise a boundary case

Engineering context. phase loss, repeated starts, high ambient, jam, low voltage, cooling failure, manual reset, remote reset 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 phase loss, repeated starts, high ambient, jam, low voltage, cooling failure, manual reset, remote reset 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 motor thermal-overload protection, trips and control response 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 load, supply, phase, setting, thermal, device, auxiliary-contact, control, reset or mechanical 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 load, supply, phase, setting, thermal, device, auxiliary-contact, control, reset or mechanical 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. settings and coordination verified by qualified personnel using current motor, starter and protective-device documentation. 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 settings and coordination verified by qualified personnel using current motor, starter and protective-device documentation 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 load, supply, phase, setting, thermal, device, auxiliary-contact, control, reset or mechanical mismatch or phase loss, repeated starts, high ambient, jam, low voltage, cooling failure, manual reset, remote reset and power return can expose assumptions that never appear during ideal startup and steady operation.

Answer surface / 07

Questions people ask about Thermal overload relay guide

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 does a thermal overload relay protect?

It is intended to protect a motor circuit from sustained overload and related conditions; it does not replace required short-circuit protection.

Why does an overload relay keep tripping?

Possible causes include excessive mechanical load, phase loss, voltage imbalance, repeated starts, poor cooling, incorrect setting or a motor fault; preserve current evidence before resetting.

What should I learn first about motor thermal-overload protection, trips and control response?

Start with the operating contract and evidence path: motor nameplate, service and load, current setting, trip class, ambient effect, phase sensitivity, auxiliary contact, reset mode, short-circuit protection and coordination, followed by motor load through phase current and thermal model to trip mechanism, auxiliary circuit, contactor release, plc status, alarm and physical stop. Add advanced features only after the baseline is predictable.

How do I practise motor thermal-overload protection, trips and control response 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 load, supply, phase, setting, thermal, device, auxiliary-contact, control, reset or mechanical mismatch or phase loss, repeated starts, high ambient, jam, low voltage, cooling failure, manual reset, remote reset 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.