Resolving Siemens SINUMERIK 802S Alarms 700029, 700016, and 3000 on CNC Milling Machines
When a SINUMERIK 802S base line controller on a CNC milling machine — for example, the ZK7640 built by Jiangsu Douleng CNC Machine Tool Co. — presents three simultaneous alarms (700029, 700016, and 3000), the symptom points to a single cascaded fault rather than three independent problems. The 3000 Emergency Stop is the visible manifestation, while 700016 (MCP Drive Enable) and 700029 (Spindle Inverter Alarm) are user-defined PLC messages generated by the machine builder's ladder program to describe why the controller refused to release the spindle drive.
This reference documents how to interpret these alarms on the 802S base line, isolate the underlying cause on a non-Siemens-built machine, and apply the verification sequence that returns the mill to a serviceable state without removing the spindle drive or replacing the controller.
1. Problem Details
The reported fault on the ZK7640 mill appears as three concurrent messages on the 802S base line HMI:
| Alarm Number | Text Displayed | Origin | Visibility |
|---|---|---|---|
| 3000 | Emergency Stop | Siemens standard PLC | Always displayed at the top of the alarm line |
| 700016 | Key MCP Drive Enable key | OEM (machine builder) PLC | Listed below 3000 in the alarm bar |
| 700029 | Spindle Inverter Alarm | OEM (machine builder) PLC | Listed below 700016 |
The machine had been running normally prior to the fault. No new tooling, no recent program edit, no parameter change. That fact alone removes roughly 60 % of probable causes and tells the troubleshooter to focus on hardware interlocks rather than part program or NCK parameter corruption.
2. Alarm Numbering Convention on the SINUMERIK 802S base line
SINUMERIK controllers separate alarm authorship into two distinct bands:
- Standard Siemens alarms (1 to 6xxxx): Documented in the SINUMERIK 802S base line Lists Manual (6FC5597-3AA10-0BP0). These cover NCK, drive, communication, and PLC runtime issues for which Siemens ships a published explanation and clearance procedure.
- OEM / machine builder alarms (700000 and above): Defined entirely inside the machine builder's compiled PLC program. Siemens neither documents nor recognises the meaning of these numbers. Only the builder's ladder source, the builder's parameter sheet, or a contact at the builder's service desk can authoritatively decode them.
Both 700016 and 700029 fall in the OEM band. That is why Siemens support — and any third party — can only guess at the meaning. The guess below is the most likely interpretation given how 802S base line builders conventionally name their messages; treat it as a working hypothesis until confirmed by the original ladder dump.
3. Alarm 3000 — Emergency Stop: Cause Analysis
Alarm 3000 on the 802S base line is the standard Siemens message raised when the PLC's E_STOP input bit transitions low. The PLC bit is fed from a single hardware chain, which on a typical 3-axis milling machine reads as follows:
- Front panel Emergency Stop mushroom (NC contact)
- Rear cabinet Emergency Stop mushroom (NC contact)
- Door interlocks on each access door (NC contacts in series)
- Drive enable contactors' normally-closed feedback (NC contacts)
- External safety relay output (e.g., Pilz PNOZ, Sick UE10)
All five elements must be closed (conducting) for the PLC to consider the chain healthy. If any one opens — even momentarily — the PLC latches E_STOP active, drops the drive enable relay, and posts alarm 3000 in the alarm bar.
Because 3000 is a latched condition, the operator must clear it explicitly with the Reset key on the MCP once the chain is electrically closed again. Cycling power will not, by itself, clear 3000 if any NC contact in the chain remains open.
4. Alarm 700016 — MCP Drive Enable Key: Cause Analysis
MCP stands for Machine Control Panel — the operator keypad with jog, rapid, feed-hold, cycle-start and reset keys. On the 802S base line, the MCP is connected via a dedicated ribbon to the I/O module and exposes each key as a discrete input bit to the PLC.
The most common builder interpretation of alarm 700016 ("Key MCP Drive Enable key") is one of two scenarios:
- Stuck or shorted key: The drive enable key contact is closed in hardware while the PLC expects it open. This is the more probable cause when 3000 (E-Stop) and 700029 (Spindle Inverter Alarm) are also present, because most builders wire the drive enable key into the same permissive chain.
- Required-action key: The builder's PLC is asking the operator to physically press and release the drive enable key as part of the re-arm sequence after E-Stop recovery.
To distinguish the two, watch the MCP's drive enable LED while the controller is powered and no key is being touched. If the LED is lit without anyone pressing the key, the contact is shorted. If the LED stays dark until you press it, the PLC is requesting the action.
5. Alarm 700029 — Spindle Inverter Alarm: Cause Analysis
The 802S base line does not, by itself, decode spindle drive faults in detail. It relies on a single discrete input from the spindle drive (or its interface card) wired into the PLC's SPINDLE_READY or SPINDLE_FAULT input. When the PLC sees the fault bit active, it raises the OEM alarm 700029 with whatever text the builder chose — in this case "Spindle Inverter Alarm".
The fault bit can be triggered by any of the following at the spindle drive:
| Drive Family (typical for ZK7640 era builds) | Most Common Fault Codes Triggering the Bit | Visual Indicator on Drive |
|---|---|---|
| Siemens SIMODRIVE 611 | OF (overcurrent), OH (overtemperature), EE (encoder) | Two-digit 7-segment on drive front |
| Fuji FVR-E11S / Frenic | OC1, OC2, OU, LU, OH | LED code on front panel |
| Mitsubishi FR-S500 / E500 | E.OC1, E.OV1, E.THM, E.UVT | Two-digit LED on front panel |
| Yaskawa CIMR-J7 / V7 | OC, OV, OH, UV1, PUF | Two-digit LED on front panel |
Because the original poster reports "no error light lit at inverter", either the drive is in a latched-clear state (most modern drives blank the LED when the fault input is acknowledged but the drive is still in a faulted state), or the drive is signalling the fault through a relay contact rather than an LED — that is normal for drives wired to a controller's discrete input.
6. Initial Field Diagnostics — Power Cycle Procedure
Before opening the cabinet, perform the controlled power cycle that 802S base line service technicians use as the first triage step:
- Press Reset on the MCP. If 3000 does not clear, the E-Stop chain is still open electrically — go to Section 9.
- Turn the main disconnect to OFF. Wait 30 seconds for the controller's 24 VDC rail to decay.
- Open the cabinet and confirm zero potential at the 400 VAC bus with a CAT III meter.
- Press and hold the cabinet-mounted Emergency Stop while powering back on. This forces the controller into a safe state on boot.
- Restore the main disconnect. Wait for the 802S base line HMI to fully boot (typical boot time on a 802S base line is 45–90 seconds; older PCU panels can take up to 3 minutes).
- Release the Emergency Stop mushroom.
- Press Reset on the MCP. Observe the alarm bar.
If only 3000 clears but 700016 and 700029 remain, the OEM ladder is correctly reporting that one or both of its monitored interlocks is still false. If all three clear and re-appear within five seconds, the ladder is detecting a steady-state hardware fault and the controller must be observed live with the door open to read the spindle drive LED before the boot sequence erases it.
7. Spindle Drive Inspection Procedure
Perform the following visual and electrical checks at the spindle drive:
- Read the LED or 7-segment display on the drive front. If blank, power the drive off, wait the discharge time, then back on without enabling — many drives will re-display the last fault on power-up even when cleared.
- Check the drive's fault output relay (terminals typically labelled
RA-RB-RCor30A-30B-30C). With the drive in fault state, the relay should be in its alarm position. Measure with a meter on the appropriate terminals. - Check 3-phase input voltage at the drive's L1/L2/L3 terminals. Reading should be within ±10 % of the drive's nameplate voltage (typically 380–400 VAC line-to-line for Chinese-built machines).
- Check the DC bus voltage (terminals P and N) on drives that expose it. On a healthy 400 VAC input, expect ~540 VDC. If the DC bus is below 470 VDC, the input line is sagging — investigate upstream contactor, breaker or supply transformer tap.
- Check spindle motor insulation resistance with a 500 V megohmmeter between any U/V/W terminal and earth. Reading should be >100 MΩ. Lower readings indicate moisture ingress or winding damage, both of which will produce intermittent overcurrent faults even when the drive looks "OK" at rest.
- Check the encoder feedback cable (if fitted) for continuity between the drive end and the motor end. A broken shield or a single broken conductor is the single most common cause of "spindle inverter alarm" on first start-up of a machine that has been idle for weeks.
8. MCP Signal Tracing Procedure
With the controller powered and the door interlock defeated (using the documented maintenance key, never by bridging a safety switch), trace the drive enable key signal:
- Locate the MCP wiring diagram in the machine's electrical drawing set (typically in the back of the cabinet or in the builder's documentation pack).
- Identify the drive enable key's two terminals on the MCP.
- With no key pressed, measure resistance across the contacts. Expect >1 MΩ (open).
- Press and hold the key. Expect <1 Ω (closed).
- If the contact reads shorted with no key pressed, the key switch is mechanically failed and must be replaced as a unit — repair is not field-expedient.
- If the contact is healthy, the builder's ladder is requesting the operator action. Acknowledge by pressing the drive enable key once on power-up, exactly as the builder's commissioning procedure specifies.
Most 802S base line builders use the drive enable key as part of a deliberate re-arm sequence after E-Stop, and they will latch 700016 until they see a clean rising edge on that input. A momentary press and release is normally sufficient.
9. Emergency Stop Chain Verification
Alarm 3000 will not clear while any NC contact in the E-Stop chain is open. Use a meter on each section to localise the break:
- Pull the upstream safety relay (Pilz, Sick, or equivalent) and bench-test its output with a jumper between the two safety input channels — only if you are authorised to defeat the safety circuit and only for the duration of the test.
- Manually depress and twist-release each Emergency Stop mushroom to ensure none is mechanically latched in the depressed position.
- Open and close each cabinet door, listening for the door interlock to click. Sticky interlocks (common in dusty shops) can leave the contact half-open.
- Measure the voltage at the PLC's
E_STOPinput. On a 24 VDC system, expect 24 V when the chain is closed and 0 V when any NC contact is open. - Trace the chain section by section, isolating each NC contact with a temporary jumper until the PLC's
E_STOPbit transitions high again.
10. PLC Ladder Dump — The Last-Resort Method
If the electrical cause cannot be localised by inspection and the machine builder is unreachable, the only authoritative source for the meaning of 700016 and 700029 is the compiled PLC program inside the controller. Extracting it requires a Siemens PG field programmer, the SINUMERIK 802S base line Toolbox (or the older S7-200 / 802S service tool), and a serial connection to the COM port on the controller's I/O module.
The rough procedure is:
- Connect the PG to the controller's MPI/serial service port.
- Start the SINUMERIK 802S service tool.
- Upload the PLC project (
.TEAand compiled binary) to the PG. - Open the ladder in the editor and search for the symbol or constant associated with
700016and700029. - Trace the rung backwards to the input conditions that raise the alarm.
For the alarm text "Key MCP Drive Enable key", search the project for the string literal that feeds the alarm display. For the alarm text "Spindle Inverter Alarm", search for the discrete input mapped to the spindle drive's fault relay. Both will reference the input byte/word and bit position that the builder chose.
This procedure is well documented in the SINUMERIK 802S base line service course materials available through the Siemens lifelong educational advantage program for industrial machinery, but it should only be attempted by personnel already trained on the platform.
11. Diagnostic Decision Matrix
| Observed Combination | Most Likely Root Cause | First Action | Verification |
|---|---|---|---|
| 3000 only after power cycle | E-Stop mushroom mechanically latched | Twist-release all E-Stops | Press Reset; 3000 should clear |
| 3000 + 700016, MCP drive enable LED on without key press | Drive enable key shorted | Measure MCP key contact resistance | Replace MCP key switch |
| 3000 + 700016 only, MCP LED dark | Ladder requesting re-arm action | Press and release drive enable key once after Reset | 700016 should clear within 1 s |
| 3000 + 700029, drive LED shows OV or OC | Spindle drive overvoltage or overcurrent | Check 3-phase input voltage, DC bus voltage | Clear drive fault, re-attempt start |
| 3000 + 700029, drive LED shows EE or encoder fault | Encoder cable or encoder failure | Check encoder continuity and shielding | Replace encoder cable if any conductor >2 Ω |
| 3000 + 700029, drive LED blank, fault relay latched | Drive in latched fault, LED auto-cleared | Cycle drive power only, observe boot-time fault display | Note displayed fault, consult drive manual |
| All three persist after all above checks | Ladder dump required to decode OEM symbols | UPLC project to PG using SINUMERIK service tool | Search ladder for 700016 / 700029 strings |
12. Verification Sequence
After any corrective action, run the following return-to-service sequence:
- Power on with E-Stop depressed.
- Release E-Stop. Confirm no alarm 3000.
- Press Reset on the MCP.
- Press the drive enable key once if the builder's commissioning procedure requires it.
- Confirm alarm bar is empty.
- Jog X and Y at low feedrate (5 %) in manual mode for at least one full axis length each.
- Run the spindle at 500 rpm for 30 seconds in M03. Listen for abnormal noise, watch the drive current display on the HMI.
- Run a no-load part program (an air cut of the last proven program) for one full cycle.
- Reset the machine's hour-meter counter if the fault interrupted a production job, and record the fault and root cause in the maintenance log.
If the alarms re-appear during the verification sequence, the fault is intermittent and the diagnostic cycle restarts from Section 6 with focus on intermittent wiring (door interlock flexing, vibration-loose terminal, thermal trip on a cooling fan).
13. Preventive Measures for Repetitive Occurrence
Three alarms appearing simultaneously on a machine that was running smoothly the day before is rarely a coincidence. Apply the following preventive actions:
- Tighten cabinet terminals annually: Vibration from the spindle and chip conveyor will loosen screw terminals on Phoenix, Wago and Weidmuller blocks. A loose 24 VDC return on a safety input is a classic intermittent cause of phantom 3000 alarms.
- Clean door interlocks quarterly: Coolant mist and chips accumulate on the actuator surface. Worn actuators produce partially-open contacts that look healthy with a meter but fail under vibration.
- Inspect spindle encoder cabling every six months: Drag-chain flexing fatigues encoder conductors long before the cable jacket shows damage. Replace the encoder cable as a wear item, not as a repair.
- Verify drive cooling fans annually: A failed heatsink fan on a SIMODRIVE or Frenic will produce an over-temperature fault that clears on cool-down, only to re-appear hours later under load.
- Archive the PLC project to a labelled USB stick stored in the cabinet: When the next 700000-series alarm appears, the ladder dump is one minute away rather than one support call away.
14. Escalation Path When the Builder Is Unreachable
When the machine builder (in this case Jiangsu Douleng CNC Machine Tool Co.) cannot be contacted and the in-house team has exhausted the inspection-based diagnostics above, escalate in the following order:
- Local Siemens industrial automation distributor service desk. They will not decode the OEM alarm text but they can confirm the controller hardware is healthy.
- SINUMERIK hotline through Siemens Industry Online Support for standard 802S base line platform faults.
- Independent SINUMERIK service integrator listed on the Siemens industrial machinery partner program.
- SINUMERIK 802S base line service training and refresher courses through the educational advantage program — these equip in-house maintenance staff to perform ladder dumps and symbol-table inspections in future.
For sites outside China, the closest Siemens CNC competence centre is typically the regional Siemens office; in Pakistan, the local Siemens office is reachable via the official Siemens country website (linked above). Cross-border support for OEM alarms is limited by the builder's IP, but the controller's hardware health and standard alarm band can always be confirmed.
FAQ
What does alarm 700029 mean on a SINUMERIK 802S base line?
Alarm 700029 is an OEM (machine builder) defined alarm, not a Siemens standard code. On most 802S base line milling machines the literal text "Spindle Inverter Alarm" means the PLC has detected an active fault bit from the spindle drive — typically wired to a discrete input on the I/O module. Confirm by checking the spindle drive's LED or 7-segment display and the fault relay state.
What does alarm 700016 mean on a SINUMERIK 802S base line?
Alarm 700016 is also OEM defined. The text "Key MCP Drive Enable key" indicates either that the Machine Control Panel's drive enable key switch is mechanically shorted (stuck closed) or that the builder's PLC is requesting the operator to press the drive enable key as part of the re-arm sequence after Emergency Stop recovery.
Why do alarms 3000, 700016 and 700029 appear together?
Alarm 3000 (Emergency Stop) is the root condition that prevents the controller from releasing the spindle drive. Once 3000 is active, the builder's PLC refuses to accept drive enable requests (raising 700016) and reads the spindle drive as faulted because the drive enable line has been removed (raising 700029). Treat 3000 as the primary fault and the 70000x alarms as cascaded consequences.
Can Siemens decode alarm 700016 or 700029?
No. Siemens only documents the standard alarm band (1 to 6xxxx). Alarms in the 700000 band are defined inside the machine builder's PLC program; only the builder, or a successful upload and review of that program, can authoritatively explain them.
Can I upload the SINUMERIK 802S PLC program to decode these alarms myself?
Yes, with the SINUMERIK 802S base line service tool, a Siemens PG programmer and the MPI/serial service port. Upload the project, search for the strings "700016" and "700029", and trace the rungs backwards to the input symbols. This procedure is taught in the Siemens lifelong educational advantage program industrial machinery curriculum. Respect the builder's IP — only read, do not modify without authorisation.
Why does the spindle drive LED look clean even though alarm 700029 is active?
Many spindle drives auto-clear their LED indicator as soon as the run command is removed. The fault relay inside the drive remains latched until the drive is power-cycled with no run command present. Power down the drive only, wait the discharge interval, then power back on to see the boot-time fault display.