Troubleshooting SINUMERIK 810T GA3 Alarm 1120 X Axis Clamping

David Krause21 min read
Motion ControlSiemensTroubleshooting
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Problem Overview

A Siemens SINUMERIK 810T GA3 controlled lathe presents a recurring alarm 1120 ORD 2 X Clamping Monitoring during production, eventually forcing random mid-cycle stops. After replacement of the X-axis drive module, additional alarms appear:

  • 2000 Emergency Stop (E-Stop)
  • 6034 Turret Not Ok (machine builder alarm)
  • Automatic Stop. Auto Interrupted CH-1 channel message

Simultaneously, the hydraulic unit fails to start, the operator panel intermittently fails to boot, and the operator cannot reference the X-axis. This article decodes the alarm chain, isolates the root cause candidates (drive, encoder, hydraulic interlock, E-stop circuit, turret PLC interface), and provides a field-proven diagnostic and repair procedure for 810T GA3 retrofit and OEM lathes.

Critical safety note: An 810T machine with an unresolved 2000 E-Stop is in a hard-locked state. Hydraulics, spindle drive enable, and clamp release are all conditional on the E-stop chain being healthy. Do not bypass E-stop limit switches, door interlocks, or pressure switches during diagnosis; always meter the chain from the source outward and follow site lock-out / tag-out rules.

SINUMERIK 810T GA3 System Architecture

The SINUMERIK 810T GA3 (Software GA3) is a turning-variant CNC for 2-axis lathes (X, Z) plus spindle. It shares the same NCK/PLC kernel as the 810M GA3 (milling) but uses turning-specific cycle packages (CYC95 stock removal, CYC97 thread, etc.) and lacks the milling-specific cycles. The "GA3" suffix indicates a specific firmware generation; later retrofits used GB, GA1, GA2, and on the 810D platform the SW transition moved to HMI Embedded.

810T GA3 hardware components commonly encountered on retrofit and OEM lathes
Subsystem Typical module Notes
NCU/CCU 6FC3100-0A / 6FC3101-0A CPU + operator panel interface, battery-backed SRAM
Operator panel 6FC3103-0A / OP030 9" CRT or 10" LCD variants, CCFL backlight
X / Z axis drive SIMODRIVE 6SC6100 / 6SC6500 Analog setpoint, 600 V DC link, 3-phase IGBT output
Spindle drive SIMODRIVE 6SC6100 / 6RA23 Analog or digital depending on retrofit
Servo motors 1FT5 / 1FT6 / 1PH series Incremental encoder or resolver feedback
PLC PLC135WB / PLC130WB Integral to CCU, programmed in STEP 5 ladder (S5-DOS)
I/O 6SX700 series Discrete 24 V I/O on the rack

On many 810T lathes the X and Z axes are powered from a single 6SC6100/6SC6500 dual-axis module (commonly 6SC6500-0AB or 6SC6100-0BB). The operator panel is connected to the CCU via coaxial cable on early builds and twin-lead / ribbon on later builds. The PLC program is the same STEP 5 source across most 810T variants; only the user program and machine data change between machine builders.

For deeper architecture detail, refer to the SINUMERIK 810T GA3 Operating Manual and the SINUMERIK 810T GA3 Diagnostics Manual on Siemens Industry Online Support.

Decoding Alarm 1120 ORD 2 X Clamping Monitoring

Alarm 1120 belongs to the Siemens standard alarm set for SINUMERIK 810 / 820 / 840. The structure is:

  • 1120 - alarm number assigned to "Clamping monitoring" in the 810 / 820 / 840 alarm catalog.
  • ORD 2 - axis identifier from the machine data. ORD 2 is the second "logical axis" in the axis configuration. On a 2-axis lathe with spindle the default is X = ORD 2, Z = ORD 1. On a mill this would be Y; on the 810T lathe, ORD 2 is the X axis.

The semantic meaning is: the X-axis clamp release is being requested (or expected) by the NC, but the clamping monitoring signal has not transitioned to the expected state within the configured window.

Alarm 1120 field interpretation
Field Value Meaning
Alarm number 1120 Clamping monitoring
Axis (ORD) 2 Second configured axis = X on 810T lathes
Trigger NC initiated axis motion Axis brake / clamp release expected
Clearance condition Clamp / position-monitoring input transitions or NC reset Time-window depends on machine data

On most 810T lathes the X-axis slides on a hydraulic-brake slide. The slide is held in position by a spring-applied / hydraulically-released brake (fail-safe design). When the operator selects an axis via the handwheel, MPG, or AUTO, the NC issues "controller enable" and "clamp release" to the PLC. The PLC energises a 24 VDC solenoid that routes hydraulic pressure to the brake-piston cavity, mechanically releasing the brake. A pressure switch or proximity switch then confirms the brake is open. The PLC feeds this confirmation back to the NCK via a dedicated I/O (commonly on a PLC135WB digital input module). The NCK expects the confirmation within a time window configured in the clamping-monitoring machine data (MD 28xx / MD 36xx range on 810 / 820, OEM-specific).

If the confirmation does not arrive, or arrives in the wrong state, the NCK raises 1120 and disables the axis. This is a safety function: it prevents the NC from commanding motion on a slide that the safety logic has not confirmed is movable.

Common root causes for 1120 ORD 2

  1. Hydraulic pressure below the brake-release threshold (pump failure, low oil level, blocked filter, blown seal in the brake piston).
  2. Brake-release solenoid coil open or shorted.
  3. Pressure switch / proximity switch misadjusted, failed, or wired with a broken conductor.
  4. PLC input module channel failure (commonly a stuck-high or stuck-low digital input).
  5. Drive controller-enable signal missing (the drive does not pulse-enable, so the brake release is not requested at all).
  6. NCK-PLC interface data corruption after a power dip, requiring NCK cold restart.

On the failing machine the original X-axis drive was found to be at fault. A failed drive can pull the controller-enable / pulse-enable line low, which keeps the brake released while the NC is still trying to verify a release confirmation - or it can keep the drive in an error state that prevents the NC from issuing the release request at all, causing the monitor to time out and raise 1120.

Cascading Fault Pattern: 2000, 6034, and Hydraulics Lockout

After the drive is replaced, the machine exhibits a different but related set of faults. The alarm chain is a cascade, not a list of independent problems. Treat them as one fault with multiple symptoms.

Alarm 2000 Emergency Stop

Alarm 2000 is the SINUMERIK standard "Emergency Stop" alarm. It is triggered whenever the NCK receives an E-stop signal from the PLC (or loses a controller-enable signal that the PLC interlock chain treats as E-stop). On the 810T the E-stop chain is wired into the PLC via a single input (commonly I33.0 on the 810T PLC convention) and the NCK hardware E-stop line on the CCU. When 2000 is active, the NCK:

  • Disables all drives (pulse and controller enable dropped).
  • Locks the spindle (no CW/CCW, no orientation).
  • Rejects NC Start and M-functions for spindle motion.
  • Prevents reference-point approach (G74 / G75) until E-stop clears.

Critically, 2000 also gates the hydraulic-unlock request at the PLC level on most lathes. The PLC refuses to energise the hydraulic pump contactor (commonly K0) until the E-stop is fully reset. Hence "the hydraulics won't come on" is a symptom of an unresolved 2000, not a separate fault.

Alarm 6034 Turret Not Ok

Alarm 6034 is not in the Siemens standard alarm catalog for 810 / 820 / 840. It is a machine builder (OEM)-defined alarm raised by the turret PLC program. On retrofit and OEM lathes, alarm numbers in the 6xxx range (and sometimes 5xxx) are reserved for user PLC %FC / %FB messages - the same convention that allows the OEM to define its own alarm text. The text "Turret Not Ok" tells you the PLC's turret-in-position-and-locked state machine has not reached the ready state. Causes include:

  • Turret rotation motor contactor not pulled in (aux contactor or overload tripped).
  • Turret clamping proximity switch not made (turret not seated).
  • Tool-count parity error or tool-number mismatch between PLC and NCK tool table.
  • The PLC is itself held in stop because of the upstream 2000 E-stop - meaning 6034 is a child of 2000, not an independent fault.

Operator panel not booting

An operator panel that "sometimes won't come on" after a drive fault usually points to one of three causes on the 810T GA3:

  1. DC link sag on the 24 V logic supply. A shorted drive module can pull the 24 V rail down. After the new drive is installed, confirm that the 24 V supply is clean and within +/-10 % at the OP power terminals.
  2. Corrupt NCK / PLC startup because the NCK was powered off mid-cycle. Perform a full NCK cold restart (described in the procedure below).
  3. Loose coaxial / twin-lead connection between the CCU and the OP. With the new drive installed the cabinet may have been moved; check the ribbon cable seating on the back of the OP030.

Fault cascade diagram

The relationship between the alarms can be visualised as a fault tree. The SVG below summarises the dependency - the goal is to recognise that 1120, 6034, and the hydraulic lockout are all downstream of 2000.

2000 Emergency Stop Hydraulics OFF Drives disabled 6034 Turret Not Ok Clamp release denied No reference / no NC Start Tool change blocked 1120 X Clamping causes drives drop pulse-enable

Dual-Encoder X-Axis Configuration on 810T Lathes

The failing machine is described as having two encoders on the X axis: one on the servo motor, one on the opposite side of the motor. This is a standard Siemens dual-encoder setup for semi-closed / closed-loop lathes. The roles are distinct and the NCK uses both.

Encoder roles on a 810T X-axis
Encoder Mounting Function MD assignment
Motor encoder (M) On servo motor rear Commutation, speed, indirect position (semi-closed loop) MD 22xx / 24xx on 810 / 820 (axis-specific)
Measuring system encoder (S) On the slide / screw end of the axis Direct position feedback (closed loop) MD 23xx / 25xx on 810 / 820 (axis-specific)

On most turning machines both encoders are wired back to the drive (motor encoder on X311, direct measuring system on X321 on the 6SC6100 / 6SC6500 family) and the NCK reads the position through the drive's serial or parallel position interface. The two are used for:

  1. Cross-check: the NCK compares the two actual-position values; if they diverge beyond a tolerance (configured in MD), an alarm in the 25xx range "Position control" or 1040 "Contour monitoring" will fire.
  2. Slip compensation: any constant offset between the two is treated as ballscrew torsion / pitch error and compensated, which improves contouring accuracy on turning.

For alarm 1120 the relevant encoder is the motor encoder, because the drive must be able to report speed / position before the brake-release sequence can be confirmed. If the motor encoder is faulty, the drive will not pulse-enable, and the cascade described above follows. Field replacement of the X drive therefore required that the encoder signals be re-checked at the new module's X311 / X321 terminals - a mis-pinned cable produces follow-up alarms 1040 (contour monitoring) or 1680 (encoder defective) rather than 1120, but both are interpreted by the NCK as "axis not safe to move".

Drive Module Replacement: SIMODRIVE 610 / 650 Considerations

On 810T systems the drive is typically a SIMODRIVE 610 or SIMODRIVE 650 module. The replacement must be of the same MLFB (Siemens machine-readable part number) or a clearly listed successor, otherwise the parameter set, current rating, and command structure will not match the original NCK configuration.

Common 810T X / Z drive MLFB references (verify against machine BOM)
MLFB prefix Function Notes
6SC6100-0A... Single-axis module, 4 / 8 / 15 A variants Older 810 / 820 retrofit
6SC6500-0A... Two-axis module, 8 / 15 / 25 A variants 810T GA3 with X + Z on one chassis
6SC6100-0B... Single-axis module, higher current Heavier lathes, large X-axis motors
6SN1123-1A... SIMODRIVE 611 successor Used only with explicit NCK cross-compile

When replacing a drive on a 810T GA3:

  1. Verify the MLFB exactly. A 6SC6500-0AB and 6SC6500-0AC differ in current rating; a 6SC6100-0AB is a different module than 6SC6100-0BB. Cross-check against the as-built BOM in the cabinet before applying power.
  2. Copy the encoder cable pin-out. The X311 (motor encoder) and X321 (optional direct measuring system) pin assignments must match the original. A swapped or crossed pair produces a follow-up alarm (1040 contour monitoring or 1680 encoder defective) and may keep 2000 active.
  3. Set the axis address. On dual-axis 6SC6500 modules, the address jumper selects which axis is the master and which is the slave. X should be the master (address 1) and Z the slave (address 2) for the standard 810T topology.
  4. Re-load the drive parameters. Drive parameters for 810T are stored on the CCU's battery-backed SRAM; if the battery is weak, parameters may be lost. Verify by entering the drive's parameter menu and comparing against the commissioning sheet.
Important: If the replacement drive is from a different machine, the parameter set inside the drive must be cleared and re-loaded from the commissioning sheet. A mismatched drive parameter set is a common cause of post-replacement 2000 E-Stop and 6034 turret faults on the 810T, because the drive will refuse to pulse-enable, the E-stop chain reads "open", and every downstream fault appears.

Hydraulic Interlock and Clamping Circuit Diagnostics

The "hydraulics won't come on" symptom must be diagnosed in this order, because the hydraulic start is gated by the E-stop chain and by axis controller-enable logic on most 810T lathes.

  1. Verify 2000 E-stop is clearable. Reset the E-stop push-button, then attempt an NC reset (CANCEL or RESET key). If 2000 returns immediately, the E-stop chain is still open - go to the chain-tracing section.
  2. Verify the hydraulic pump contactor (K0) is pulled in. Listen for the contactor. Use a multimeter on the coil terminals (24 VDC). If 24 V is present and the contactor does not close, the contactor coil is open.
  3. Verify the pressure switch. Many 810T lathes have a low-pressure switch on the hydraulic manifold that must close within 2-3 s of K0 pulling in. If the pump runs but the pressure switch does not close, investigate the pump, the relief valve, the filter, and the suction line.
  4. Verify the brake-release solenoid. When the NC requests axis motion, the PLC should energise the brake-release solenoid. If the solenoid does not pull in, the brake stays applied, the proximity switch never closes, and 1120 fires within 0.5-1 s of the motion request.
Hydraulic interlock on a typical 810T lathe (OEM-specific)
Signal PLC address (typical) Function
E-stop OK I33.0 NCK E-stop chain clear
Hydraulic pump start Q40.0 Energises K0 contactor
Pressure OK I40.0 Pressure switch feedback
X brake release Q41.0 Brake-release solenoid on X
X clamp confirmed released I41.0 Proximity switch feedback
Z brake release Q41.1 Brake-release solenoid on Z
Z clamp confirmed released I41.1 Proximity switch feedback

The exact I/O addresses depend on the OEM PLC program. Always refer to the machine builder's PLC source or the commissioning sheet for the canonical addresses on a given retrofit. The naming convention (I33.x, Q41.x) is consistent across most 810T OEM builds, but not universal.

E-Stop Circuit Tracing for Alarm 2000

The E-stop chain on a 810T lathe typically consists of:

  1. Hard-wired E-stop push-button (NC contact in series with the safety chain).
  2. Cabinet door interlock switches (if used).
  3. Drive "ready" relay contact in series - the 6SC6100 / 6SC6500 has a relay contact that opens when the drive is in a fault state.
  4. Spindle drive "ready" relay contact.
  5. Axis module "pulse enable" feedback.

If the new drive module has not been correctly configured (or its ready-relay contact is wired differently from the original), the safety chain will appear open even though the E-stop push-button is released. The 810T will raise 2000 and refuse all motion. This is the single most common reason that 2000 reappears immediately after a drive replacement.

Field procedure to trace the chain:

  1. With the machine powered and E-stop released, measure the E-stop chain voltage at each break point. The chain is typically 24 VDC sourced from a safety relay or from a hard-wired loop. A "low" reading at any segment indicates the break is downstream of that point.
  2. Confirm the new drive's "ready" relay contact closes when the drive is in standby. If the relay contact is open, the drive itself is still in a fault state - check the drive's seven-segment display for the active fault code (common codes: F001 overcurrent, F015 encoder, F031 power module, F041 IGBT desaturation).
  3. Confirm the door interlocks are closed and that no auxiliary contact is stuck.
  4. Confirm the spindle drive "ready" contact is closing. A spindle drive left in a fault state from before the retrofit will also hold 2000 active.

Machine Builder Alarm 6034 - Turret Diagnostic

Alarm 6034 is OEM-defined. To diagnose, you need the OEM PLC source or the OEM's alarm-list PDF. The typical turret ready state machine on a 4-station or 8-station wedge-tool-post or disk-turret lathe is:

  1. Turret unclamped (proximity switch 1 made).
  2. Turret rotated to the requested pocket.
  3. Turret clamped (proximity switch 2 made).
  4. Turret "turret_ok" flag set in the PLC status word (and visible to the NCK as bit 7 / 6 in the axis / channel status word).

On a machine held in 2000 E-stop, the PLC processing of the turret may be suspended, leaving the "turret_ok" flag cleared. This is why 6034 appears alongside 2000 - it is a downstream symptom, not an independent turret fault. Clear 2000 first, then re-evaluate 6034.

If 6034 persists after 2000 is cleared, the actual turret is suspect. Investigate:

  • Turret rotation motor contactor and overload.
  • Turret clamp / unclamp solenoid(s).
  • Turret encoder or proximity switches (count, index, clamped).
  • Tool table mismatch between PLC and NCK (compare tool pocket numbers in the tool table with the PLC's expected mapping).

Step-by-Step Diagnostic and Repair Procedure

The following procedure assumes the drive has been replaced. If it has not been replaced, do that first, observing the notes in the previous section.

  1. Power down completely. Main disconnect off, wait 5 minutes for the DC link to discharge. Lock-out and tag-out per site safety rules.
  2. Inspect the new drive's part number and parameter label. Verify the MLFB matches the BOM. If the label is illegible or missing, treat the drive as suspect and source a known-good unit.
  3. Re-check the encoder wiring at the new drive. X311 (motor encoder) and X321 (direct measuring system) pin-for-pin against the original wiring diagram. Use a multimeter on the encoder cable to verify continuity end-to-end (each pair, plus shield continuity to chassis ground at one end only).
  4. Re-check the drive address jumper and bus termination. On a 6SC6500 dual-axis module, the master / slave jumper must match the X = master, Z = slave configuration.
  5. Re-check the "ready" relay contact wiring. Confirm the new drive's relay contact is wired into the E-stop safety chain at the correct terminal - this is the most common cause of post-replacement 2000.
  6. Apply power, but do not enable drives yet. Observe the 7-segment display on the new drive. It should reach standby state (e.g., "0" or blank) without showing a fault code.
  7. Bring up the operator panel. If the panel does not boot, check 24 VDC at the OP, the ribbon cable, and the backlight fuse. If still no display, perform an NCK cold restart (described below).
  8. Clear the alarm stack. Use the CANCEL / RESET keys to clear the visible alarms. If 2000 re-appears, the E-stop chain is still open - go back to the chain-tracing section.
  9. Confirm the hydraulic pump starts. If it does not, verify Q40.0 (or the equivalent PLC output) is being driven, K0 contactor coil is receiving 24 V, and the contactor is closing. Then verify the pressure switch closes within the configured time.
  10. Try a manual axis motion in JOG. Select the X axis, attempt a small jog. The NCK will request the brake release. Verify the brake-release solenoid is energised (Q41.0 or equivalent), the brake physically releases (you should hear a soft click and see the slide move), and the clamp-confirmed input (I41.0 or equivalent) transitions to the released state within 0.5-1 s.
  11. Approach the reference point. With both axes responding to JOG, perform a G74 / reference approach. The 1120 alarm should not recur. If it does, the clamp-confirmed input is not reaching the NCK - re-trace from the proximity switch to the PLC input card to the NCK-PLC interface.
  12. Run a dry part program. Single-block, dry-run, no coolant. Confirm spindle, turret, and axes all behave as expected. Then a full program with the part loaded.

Verification, Commissioning, and NC Reset

Verification on a SINUMERIK 810T GA3 follows a standard sequence. The matrix below is the canonical commissioning checklist for the fault class described here.

Verification matrix
Test Expected result Alarm expected if test fails
E-stop released, NC reset 2000 clears, no other alarms 2000 / 1120 / 6034
Hydraulic pump start Pump runs, pressure switch closes within 2-3 s None (PLC-level alarm, OEM-defined)
JOG X-axis Brake releases, X moves, position feedback matches command 1120 / 1040 / 1680
JOG Z-axis Z moves, position feedback matches command 1120 (Z ORD 1) / 1040
Reference point approach Both axes reach reference, REFP marker active 1120 / 1040 / 1680
M06 tool change Turret rotates and clamps on the requested pocket 6034 (OEM) / 2000
Dry-run part program All motions execute, no alarms Various
Production part program All motions execute, dimensions in tolerance Various

If a full NCK cold restart is required, power down the NCU / CCU, hold the CANCEL key during power-up, and continue to hold until the NCK requests the cold-start confirmation. Then confirm. This is necessary when the alarm stack is corrupted or when the battery-backed SRAM has lost machine data. The same procedure is used to recover from a soft PLC fault after a drive module replacement.

Preventive Maintenance Schedule

Recommended 810T preventive maintenance
Interval Action
Monthly Verify the operator panel boots cleanly; check 24 VDC rail at the OP and the NCU; visually inspect cabling.
Quarterly Inspect the E-stop push-button and door interlocks for mechanical wear; cycle-test the safety chain end-to-end.
Semi-annual Replace the NCU backup battery (typically a 3.6 V lithium cell, e.g., Renata CR2032 or a Siemens 6FC5247-series equivalent). A weak battery causes SRAM loss and the 2000 cascade on next power-up.
Annual Inspect the drive's cooling fan, clean the heat sink, and re-torque the power terminals to the specified torque. Inspect encoder cables for chafing along cable carriers.
Annual Replace hydraulic oil and filter; verify brake-release pressure and clamp pressure-switch setpoints with a calibrated gauge.
Two-year Replace the operator panel backlight (CCFL on early 810T, LED module on late 810T / 810D conversions).
Field note: After any drive replacement, always cycle the E-stop and re-test the safety chain before returning the machine to production. A miswired ready-relay contact will pass a static test and only fail under dynamic conditions, which is a known root cause of intermittent 2000 faults on retrofitted 810T lathes. Also confirm the drive's parameter set matches the commissioning sheet, not the donor machine's set, before any production run.

FAQ

What does alarm 1120 ORD 2 X Clamping Monitoring mean on a SINUMERIK 810T GA3?

Alarm 1120 is the Siemens standard "Clamping monitoring" alarm. ORD 2 is the second configured axis, which on a 810T lathe is the X axis. The NC has requested that the X-axis hydraulic brake be released (or confirmed released), but the PLC feedback signal indicating the brake state has not transitioned within the configured window. Common causes are low hydraulic pressure, a failed brake-release solenoid, a misadjusted proximity switch, a failed PLC input, or a drive that is not releasing the controller-enable signal.

Is alarm 6034 Turret Not Ok a Siemens standard alarm?

No. Alarm 6034 on a SINUMERIK 810 / 820 / 840 system is a machine-builder (OEM)-defined alarm raised from the PLC program, not from the NCK standard alarm catalog. The text "Turret Not Ok" indicates the PLC's turret ready state machine has not completed. On machines held in 2000 E-stop, 6034 often appears as a downstream symptom because PLC processing is suspended - clear 2000 first, then re-evaluate 6034.

Why does the operator panel sometimes not boot after a drive replacement on a SINUMERIK 810T?

Three causes account for the majority of cases: a sag on the 24 VDC logic rail caused by the failing or newly installed drive, an NCK / PLC startup corruption from a mid-cycle power interruption that requires a full NCK cold restart, and a loose coaxial or ribbon-cable connection between the CCU and the OP030 panel. Measure the 24 VDC rail at the OP, reseat the ribbon cable, and perform a cold restart before deeper investigation.

Can a single drive module control both X and Z axes on a SINUMERIK 810T lathe?

Yes. The 810T frequently uses a SIMODRIVE 6SC6500 dual-axis module to power both X and Z from one chassis, with the X axis as master (address 1) and Z as slave (address 2). When replacing such a module, verify the master / slave address jumper, the encoder pin-out on both axes, and the parameter set loaded from the commissioning sheet - a mismatched parameter set is a common cause of post-replacement E-stop and clamp alarms.

How do I clear a persistent alarm 2000 Emergency Stop on a SINUMERIK 810T GA3?

Alarm 2000 will not clear while the E-stop safety chain is open. Trace the chain from the E-stop push-button through the door interlocks, the drive "ready" relay contacts, and the spindle drive "ready" relay contacts. Identify the open segment with a multimeter (the chain is typically 24 VDC). Repair the open contact - commonly a miswired drive ready-relay, a stuck door interlock, or a drive still in a fault state - then perform a CANCEL / RESET on the NC. If the chain is healthy but 2000 still appears, perform an NCK cold restart to clear a corrupted alarm stack.

Back to blog