1. Problem Definition
The Sinumerik 840C is a Siemens CNC platform released in the late 1980s and used widely through the mid-1990s on gear-cutting, grinding, and special-purpose machines. On a Gleason Hurth SRS 405 shaving cutter grinder, the controller raises alarm 20190 Parameterization error NC MD on cold start. The alarm indicates that one or more machine data (MD) values the NC read from non-volatile storage on the MMC (Man Machine Communication) PC are out of range, internally inconsistent, or have been corrupted. Because the 840C will not enable any axis or spindle while this alarm is active, the machine is fully down.
This article consolidates the field-proven recovery sequence for the 20190 alarm, the related 300714 (power section code) and 13401 (axis enable) faults that typically appear alongside it on transferred machines, and the special considerations that apply when the original machine builder — here Gleason Hurth — has installed a customer-specific MD set that does not match Siemens defaults.
2. Affected Hardware and Configuration
| Subsystem | Component (840C Generation) | Notes |
|---|---|---|
| NCU | Sinumerik 840C, MMC 103/ MMC 110 PC | NC-MD stored on 3.5" HDD or MFM drive |
| Drive bus | SIMODRIVE 611A with 6SN1122 / 6SN1118 modules | Power sections report 6SN11xx-1AA0x firmware codes |
| Main spindle drive | 6SN1122-1BA11 / 6SN1122-1CA11 family | Alarm 20190 frequently tied to spindle MD block 2xxx |
| Operator panel | OP030 / OP031 with 9" or 12" CRT | Displays the 20190 error text and alarm clear key |
| Machine-specific layer | Gleason Hurth SRS 405 application MD set | Customer-defined, locked behind service password |
3. Alarm 20190 — Technical Definition
Alarm 20190 is a generic parameterization error in NC machine data. The 840C internally evaluates MD values in a fixed sequence on each NCK (NC kernel) boot:
- Load
NCMAC.COMand the boot block from the boot partition. - Read the active MD image from
\NCK\MD\MDxxxxx.DAT. - Validate MD against min/max ranges and inter-MD consistency rules.
- Hand off the validated set to the drive initialization routine.
If step 3 fails, the NCK raises 20190 and writes the offending MD number(s) into the alarm extension. To read the extension on an OP030/OP031:
- Press the
ALARMkey on the OP. - Select line
20190. - Press the
DETAILsoftkey (orHELPon later MMC versions) to display the failing MD number.
Common failing MD groups on gear-grinding 840C installations:
| MD Group | Function | Typical Trigger on SRS 405 |
|---|---|---|
| MD 2xxx — Axis MD | Encoder, leadscrew pitch, drift compensation | Drift/compensation table cleared after battery swap |
| MD 3xxx — Spindle MD | Gear stages, encoder PPR, M19 position | Main spindle drive module replaced or coded wrong |
| MD 5xxx — Channel MD | Axes-per-channel, G-code defaults | Backup image from a different channel config |
| MD 7xxx — Compile cycles | Gleason Hurth gear-grinding cycles | Compile cycle not loaded on a fresh HDD |
| MD 9xxx — OEM MD | Reserved for machine builder | Password-locked; blank after HDD swap |
4. Related Alarms on the SRS 405
Field experience on transferred 840C machines shows 20190 rarely appears in isolation. The two alarms in the source case are typical:
4.1 Alarm 300714 — Power Section Code
On the 840C this corresponds to a SIMODRIVE 611A power section coding plug mismatch. Each 6SN1122 / 6SN1123 power module carries a 10-position DIL switch or coding plug that declares its current rating. The drive firmware compares the plug reading to the value stored in MD 1xxx (drive configuration MD) at power-up. Mismatch = 300714.
Clear procedure:
- Power off the cabinet, wait 5 minutes for DC bus discharge.
- Verify each 611A module's coding plug against the SRS 405 wiring diagram (e.g.,
8A → 8A,25A → 25A). - If a module was replaced with a different rating, either install the correct plug or update the corresponding drive MD to match the new module.
4.2 Alarm 13401 — Axis Enable / Command Channel
13401 indicates the NC has commanded an axis to move but the controller-side enable chain is open. On the 840C this usually means the controller enable, drive enable, or axis-specific feed/rapid stop signal in PLC interface DB31..DB38 is missing. On the SRS 405 the signal "Achse freigegeben" (axis released) is gated by the Gleason Hurth PLC program, which requires:
- Reference point acknowledgement for all axes (
DB31-R1.4bit, etc.). - Hydraulic pressure OK (group signal).
- Door interlocks closed.
- Spindle encoder OK.
If 13401 persists after pressing the acknowledge key and the signal shows green on the diagnostics screen but no axis moves, suspect PLC-side enable logic — most often a corrupted @SPF or .SPF PLC program file on the HDD.
5. Root Cause Analysis on a Transferred Machine
When a 840C is disassembled, moved, and re-energized at a new site, alarm 20190 typically has one of the following root causes — in order of frequency observed in field service:
| Probability | Root Cause | Diagnostic |
|---|---|---|
| High | Battery-backed SRAM or HDD has lost the active MD image | Boot screen shows "Load default MD" |
| High | Backup loaded from wrong machine generation (840C vs 840CE) | MD dates in \BACKUP directory mismatch |
| Medium | Drive module swapped during commissioning but coding plug not transferred | Alarm 300714 in log; 20190 references MD 3xxx |
| Medium | PLC program file corrupt or from wrong machine builder version | 13401 present; axis enable bits not updating |
| Low | NCK EPROM / firmware mismatch after a board swap | Boot screen shows wrong SW version |
| Low | Compile cycles for the gear-grinding cycle pack missing | Cycle pack alarms after MD reset |
6. Pre-Recovery Checklist
Before clearing the alarm, capture the current state so you can roll back if a step makes things worse:
- Connect a service laptop to the MMC PC (VGA + keyboard + DOS-bootable 3.5" disk if the original).
- Copy the entire
\NCK,\PLC, and\BACKUPdirectories to a USB-attached DOS-readable drive. - Use
SETMDor the service screen to dump the current MD image to a printer or serial port. - Document the battery-backup voltage on the NCU (nominal 3.6 V lithium). If < 3.0 V, expect MD loss on next power-down.
7. Step-by-Step Recovery Procedure
Step 1 — Identify the Failing MD
Read the alarm extension as described in Section 3. Note the MD number and current value. Example extension text: 20190 MD 3220 GRRAX1 = 0 — meaning main-spindle gear-stage-1 encoder PPR is 0, which is below the legal minimum.
Step 2 — Enter Machine Builder Menu
- Press
MENU SELECT→SERVICE. - Enter the Gleason Hurth service password (machine-specific; request from Gleason).
- Navigate to
MD DISPLAY→AXIS/SPINDLE.
Step 3 — Compare Current MD to Backup
From the DOS prompt on the MMC:
C:> DIR C:\BACKUP\*.DAT /O-D
C:> TYPE C:\BACKUP\MD200105.DAT | MORE
Identify the most recent backup that originated on this exact SRS 405 serial number. The matching serial is typically embedded in the filename header.
Step 4 — Load Backup
- From the SERVICE screen, select
MD LOAD→FROM FILE. - Choose the backup file identified in step 3.
- Confirm with the softkey
YES. - Wait for the <MD LOAD COMPLETE> banner — typically 60-180 seconds for a full MD set.
Step 5 — NCK Warm Restart
- Press
RESETon the OP. - Hold
SHIFT+RESETfor 3 seconds to force a warm restart. - Observe the boot screen for "MD CHECK OK" or a new 20190 with a different extension.
Step 6 — Re-reference All Axes
If 20190 clears but 13401 remains, drive the machine to reference each axis in sequence:
- Mode switch to
JOGorREF. - Select axis X, press
+, axis travels to reference cam. - Repeat for Y, Z, and any rotary axes (A, B, C) on the SRS 405.
The reference acknowledgement bit must be set for every axis before the controller will release the spindle enable.
Step 7 — Confirm Spindle Encoder
For the main spindle, run a short M3 S100 M19 and verify the position readback in the SPINDLE diagnostics screen stabilizes within ±0.1°. If not, the spindle encoder zero offset stored in MD 3xxx was lost — re-teach it via MD SET in the SERVICE menu with the spindle mechanically indexed to a known reference notch.
8. Backup Loading — Best Practices
| Practice | Rationale |
|---|---|
| Verify backup serial number matches machine | Prevents cross-machine contamination |
| Keep at least three dated backups on different media | Protects against single-media degradation |
| Document battery replacement date on a label inside the cabinet | Future technicians know retention risk |
| Never load a backup taken with the wrong drive configuration | Avoids re-triggering 20190 / 300714 |
After every MD change, run MD SAVE immediately |
Ensures volatile changes survive a power-down |
9. HDD Replacement Procedure
When the original MFM or early-IDE HDD is suspected of media degradation, replacement with a reconditioned or CF-IDE adapter is acceptable:
- Clone the original HDD sector-by-sector using a DOS tool such as
DISKCOPYorHDCloneonto a same-or-larger drive. - Install the clone, power up, verify boot screen reports the original serial and SW version.
- If cloning is not possible (old drive dead), install a blank HDD, boot from a 840C installation floppy set, and reload MD + PLC from backup per Section 7.
10. Machine Builder-Specific Configuration
The SRS 405 uses a customer-defined MD set installed by Gleason Hurth. Field evidence from multiple units shows:
-
R parameters in the range
R0-R99are reserved for Gleason Hurth internal calculations and are not user-editable. - Compile cycles for shaving-cutter dressing, wheel profiling, and tooth-by-tooth indexing are loaded via the machine builder menu and stored in MD 7xxx.
- Some axis-pair MD blocks define synchronous following between the dresser and the workpiece spindle. The 20190 alarm frequently points to one of these blocks because their dependency chains are long and sensitive.
Gleason Hurth (now part of Gleason Corporation) still supports many legacy machines via their German service organization. When MD and backup recovery fails, contact Gleason Service with the machine serial number and the SW version shown on the boot screen — typically SW x.y on the line below the 840C banner.
11. Verification Checklist After Recovery
- No alarm present on the ALARM screen.
- All axes referenced and the
REFLED on the OP is lit for each. - Main spindle runs forward and reverse via M3 / M4 at multiple S-values.
- Tool-change cycle (if present) completes without 13401.
- One full dry-run of the gear-shaving cycle in single-block mode, watching the ALARM screen throughout.
- Save the now-working configuration as a new dated backup on at least two media.
12. Quick-Reference Troubleshooting Matrix
| Symptom | Most Likely Cause | First Action |
|---|---|---|
| 20190 with MD 3xxx extension | Spindle drive / encoder MD lost | Reload backup; re-teach spindle zero |
| 20190 with MD 7xxx extension | Compile cycle missing | Reinstall Gleason Hurth cycle pack |
| 20190 with MD 9xxx extension | OEM MD blank after battery loss | Request OEM MD set from Gleason |
| 300714 simultaneous | 611A coding plug mismatch | Verify plugs against wiring diagram |
| 13401 after 20190 cleared | PLC enable chain not closed | Check reference and interlock bits |
| Alarm returns after every boot | Battery backup dead or HDD media loss | Replace lithium battery; re-evaluate HDD |
13. Long-Term Recommendations
- Maintain a small stock of known-good 840C NCU batteries, 611A coding plugs, and a verified CF-IDE adapter pre-loaded with the machine's MD/PLC image.
- Keep a printed copy of the most recent MD dump and the machine wiring diagram in the cabinet.
- Schedule a quarterly backup-and-verify cycle even when the machine is running faultlessly; bit rot on 1990s MFM/IDE media is common.
- For higher availability, evaluate a bridge upgrade to a Sinumerik 840D sl or 828D with a Gleason Hurth cycle migration kit — though most sites retain the 840C as long as spare parts hold out.
What does Sinumerik 840C alarm 20190 mean?
Alarm 20190 is a parameterization error in NC machine data. The NCK has read an MD value from non-volatile storage that is out of range or inconsistent with other MD values. Read the alarm extension (DETAIL softkey) to see which MD number failed, then reload a valid backup or correct that specific MD.
Why does alarm 20190 appear on a transferred 840C machine?
Most often the active MD image has been lost because the NCU battery discharged during transport, or because the loaded backup originates from a different physical machine. On gear-grinding machines like the Gleason Hurth SRS 405, MD groups 3xxx (spindle) and 7xxx (compile cycles) are particularly sensitive.
Can I clear 20190 with the CANCEL / RESET key?
No. The 20190 alarm is a startup error and cannot be cleared until the underlying MD is corrected or a valid backup is loaded. RESET performs a warm restart which re-evaluates the MD and will re-trigger 20190 if the issue is not resolved.
Should I replace the HDD to clear 20190?
Only after first verifying that the MD and backup files on the existing drive are uncorrupted. If the drive is mechanically healthy, an MD reload from backup is faster and safer than an HDD swap. Replace the HDD only if sector read errors are reported during the backup verification step.
Where can I get the original Gleason Hurth MD set for an SRS 405?
Contact Gleason Service directly with the machine serial number and the SW version displayed on the 840C boot screen. They maintain legacy support for many SRS-series machines, though lead times can be several weeks for non-standard MD sets.