236-A211

Check drive hardware status indicators

Examine the physical drive unit for LED fault indicators or display messages. Most Heidenhain-compatible drives (EIB, UVR, UM, UR series) have multi-segment displays showing fault codes.

Ensure machine power is locked out before opening cabinet doors. High voltage present even when axis drives are disabled.

Read drive-specific fault code

Access MOD > System Diagnostics > Drive Diagnostics and locate the drive corresponding to %1. Read the 'Drive Status Word' and 'Drive Fault Code' fields which contain the manufacturer-specific fault information.

Cross-reference the drive fault code with the drive amplifier documentation (EIB/UVR/UM manual) - the TNC alarm 236-A211 is generic, but the drive fault code is specific.

Check DC bus voltage and temperature

In Drive Diagnostics, monitor 'DC Bus Voltage' (should be ~565-590V for 400VAC systems) and 'Drive Temperature' values. Compare against acceptable ranges in machine parameter MP7310.x (axis-specific voltage limits).

Intermittent overvoltage faults often indicate regenerative braking issues or missing/undersized brake resistors.

Verify cooling and environmental conditions

Check cabinet cooling fans, air filter condition, and ambient temperature. Verify drive heat sink temperature by observation. Check that cabinet temperature monitoring (if equipped) shows normal values in PLC diagnostics.

Heat sinks can reach temperatures exceeding 70°C during normal operation - do not touch without protective equipment.

Check encoder monitoring status

Navigate to MOD > System Diagnostics > Position Display and verify that the affected axis shows valid position values. Also check MOD > System Diagnostics > Drive Diagnostics for 'Encoder Status' flags indicating signal errors.

If position values freeze or jump erratically, this confirms encoder signal loss rather than drive electronics failure.

Verify encoder parameters match hardware

Check MOD > Machine Parameters > CfgAxisGeo MP100.x (axis name) and CfgEncoders MP6xxx series. Verify encoder type (EnDat 2.2, 1Vpp, etc.), resolution, and direction match the installed motor encoder specifications.

Incorrect encoder type settings can cause drive commutation errors that appear as drive faults.

Inspect encoder cable and connections

Power down and inspect encoder cable for damage, particularly at cable carriers and motor connection. Verify encoder connector seating at both drive and motor ends. Check cable shield continuity and proper grounding at drive end only.

EnDat encoder cables are particularly sensitive to shield breaks - use ohmmeter to verify shield continuity from drive connector to motor connector housing.

Test encoder power supply voltage

Using drive diagnostics or multimeter at motor encoder connector, verify encoder supply voltage (typically 5VDC or 3.3VDC for EnDat). Check MP6210.x for configured encoder supply voltage and compare to actual measured value.

Measure encoder supply voltage with axis disabled to avoid potential short circuit hazards during measurement.

Verify ProfiNet device configuration

Access MOD > System Setup > ProfiNet Configuration (or PLCsoft > ProfiNet > Device Configuration). Verify the drive at address corresponding to %1 shows correct GSDML file, telegram type, and device operational state is 'Running'.

After control startup, wait 30 seconds before checking - ProfiNet device parameterization occurs during startup and may briefly show configuration states.

Check cyclic data exchange quality

In PLCsoft > ProfiNet > Device Diagnostics, select the affected drive and review 'Telegram Counter', 'CRC Errors', and 'Data Exchange Status'. Any non-zero CRC error count indicates network data corruption.

Use the 'Record' function in ProfiNet diagnostics to capture telegram data during fault occurrence for analysis.