Siemens fault record

KTY/PTC TEMP: Motor Temperature Sensor Warning or Trip Boundary

The MASTERDRIVES system reports a motor-temperature warning/trip, or the temperature input behaves inconsistently after wiring, motor or board work.

MASTERDRIVES protection route7 min read

Scope of this technical record

KTY84/PTC motor-temperature warning or trip on SIMOVERT MASTERDRIVES 6SE70/6SE71 systems, separating true motor heating from sensor and terminal evidence.

Safety boundary

Do not bypass motor thermal protection. Hot motors, cooling fans and process loads create mechanical and thermal hazards; inspect only under approved lockout and machine-safety procedure.

6SE70 KTY/PTC thermal route

1Sensor type
2Cold / hot timing
3Terminals
4Cooling
5Configured response

Thermal trips are separated into sensor-route evidence and true motor heating before bypass or board replacement.

6SE70 KTY/PTC thermal evidence map

6SE70 KTY PTC thermal route sensor type cold hot timing terminals cooling configured response
The image separates sensor route faults from real motor heating.

Why a thermal trip is not automatically a hot motor

MASTERDRIVES can evaluate motor temperature through KTY84 or PTC protection paths. A warning may be real overheating, but it may also be an open sensor circuit, wrong sensor type, terminal expansion issue, damaged cable, shielding/grounding problem or misconfigured warning/fault response.

The most useful split is cold-start versus load-related. A warning on a cold motor usually begins at wiring, sensor or parameter evidence. A warning after load or high ambient begins with cooling, motor fan, bearing, airflow and machine duty cycle.

KTY/PTC evidence split

TimingFirst boundaryDo not do
Cold-start warningSensor wiring / terminal / parameterBypass the sensor
After loadCooling, fan, motor temperatureAssume the drive board failed
Intermittent with vibrationCable/terminal connectionChange thermal thresholds first
After motor workSensor type and reconnectionRun before identity is confirmed

Service record requirements

A credible request identifies the sensor type, terminal or option-board route, fault/warning timing, motor cooling condition and parameter response. Photos of the motor terminal box and drive-side terminal path are often more useful than a general cabinet photo.

Preserving the protection function is part of the repair. If a production line cannot run because of thermal protection, the responsible route is evidence capture and correction, not disabling the input.

Field record checklist

  • KTY84 or PTC identity
  • Cold/hot timing
  • Motor terminal-box photo
  • Drive terminal/option-board photo
  • Cooling fan and airflow evidence
  • Configured warning/fault response

Technical basis and reference documents

This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.

SIMOVERT MASTERDRIVES Vector Control Operating InstructionsSiemens Industry Support

OEM basis for 6SE70 / 6SE71 safety, control connections, motor temperature evaluation and option context.

SIMOVERT MASTERDRIVES brake and thermal protection evidence notesIndustrialDriveData editorial extraction

Internal technician note set used only to structure public diagnostic routes around KTY/PTC thermal protection and brake-control evidence.

Diagnostic workflow

Evidence intake

Turn this record into a qualified service request

A repair decision is much more reliable when the request includes the exact identity of the drive, the first fault evidence and the machine condition when the symptom appeared.

  • Complete drive type code / MLFB or nameplate model
  • Fault code, fault value and first event before reset
  • When the event appears: power-up, enable, ramp, run, decel or stop
  • Motor/cable connected or isolated during the symptom
  • Visible board, option-card, module and connector identifiers
  • Previous repair history, replacement parts and repeat-failure pattern
Prepare request →