1. Problem Identification: Simoreg DC Master A031 Alarm
The Siemens Simoreg DC Master drive (6RA70 / 6RA80 series and successor SINAMICS DCM) raises alarm code A031 ("Speed controller monitoring") when the closed-loop speed regulator cannot hold the actual motor speed within a configurable deviation band of the active speed setpoint for a configurable minimum time. In a properly commissioned drive this is a diagnostic alarm: the drive is signalling that the inner current/torque loop is saturated, the speed feedback path has a problem (sensor, wiring, mechanical coupling), or both.
By default A031 is non-latching: the drive logs the event, sets the alarm bit, and continues running. If the speed error persists beyond the configured escalation window, A031 may transition to fault F031 depending on the configuration word settings (P390 family in 6RA70 / r390 family in 6RA80). Always treat A031 as a symptom and search for the underlying cause rather than disabling the monitor.
1.1 Drive Platforms and Firmware
- 6RA70 series (SIMOREG DC Master, 15 A to 1200 A, 400 V / 575 V / 690 V / 830 V) — parameter set is index-based (Pxxx.y).
- 6RA80 series (SIMOREG DC Master, second generation, up to 2800 A) — parameter set is BICO-based (r / p).
- SINAMICS DCM (6RA80 successor, firmware 1.4 and later) — same alarm code A031 carried forward.
- Parameter dumps from DriveMonitor save with
.dnlextension; trace exports use.trcor.csv.
Siemens documentation for the Simoreg DC Master 6RA70 / 6RA80 is available through the Siemens Industry Online Support portal. Search for "6RA70" or "SIMOREG DC Master" to retrieve the operating manual, parameter list, and commissioning manual.
2. A031 Alarm Definition and Trigger Logic
The Simoreg firmware continuously executes the speed monitor block. Each scan (cycle time ~ 1-5 ms depending on the signal source) the block computes the absolute speed error and compares it to the threshold:
|n_setpoint - n_actual| / n_rated > threshold (P388) AND duration > t_delay (P389)
When both conditions are true the alarm is raised. Either condition alone is insufficient. A momentary speed dip during a heavy load transient will not raise A031 if the deviation settles within the configured delay.
2.1 Default Trigger Conditions
| Parameter | Description | Default | Range |
|---|---|---|---|
| P388 (r388) | Speed deviation threshold (% of n_rated) | 3.0 % | 0.5 - 50 % |
| P389 (r389) | Speed monitor time delay | 3.0 s | 0.0 - 60.0 s |
| P390.x (r390.x) | Configuration word (alarm / fault routing, monitor enable bits) | per firmware | — |
| P083 (p083) | Speed feedback source selection | 1 (analogue tacho) | 0-3 typical |
| P084 / P085 | Tacho gain scaling for P083 = 1 | per motor | — |
| Drive state | Operating status | Run | A031 suppressed in Standby / No Setpoint |
2.2 P390 Sub-Index Structure
P390 in the 6RA70 firmware is multi-indexed (P390.1 through P390.4, and in some firmware revisions P390.0 for the high word). The exact meaning of each sub-index is firmware-version-specific. If your .dnl file shows P390 sub-index values such as 1, 2, 3, 4, 3, 0, do not edit them blindly — each bit has a specific function. Open the parameter help (F1 in DriveMonitor) to confirm the meaning for the exact firmware version installed in the drive. Typical functions of the bits are:
| Sub-Index | Likely Function |
|---|---|
| P390.0 | High word of configuration (some firmware revisions only) |
| P390.1 | Alarm enable mask (which conditions raise A031 vs. only A034) |
| P390.2 | Fault escalation bit (0 = A031 only, 1 = A031 + F031) |
| P390.3 | Feedback source lock / channel selection (interacts with P083) |
| P390.4 | Hysteresis or recovery band (dead-band before alarm clears) |
3. Root Cause Categories
A031 is a symptom alarm. Three root cause families account for the majority of field incidents. Always classify the cause before changing parameters.
3.1 Speed Feedback Path Problems (most common, ~60 % of cases)
- Tachogenerator commutator wear, glaze, pitting, or uneven surface.
- Carbon brush end-of-life (length < 50 % of new).
- Tacho spring pressure weak or sticking.
- Tacho ripple > 10 % peak-to-peak of nominal DC output.
- Loose or oxidised terminal screws at the drive end or tacho end.
- Encoder cable shield broken or routed near power cables.
- Encoder signal level out of HTL / TTL specification.
- Encoder pulses-per-revolution (PPR) setting wrong for the application.
3.2 Mechanical Coupling Problems (~20 %)
- Flexible coupling elastomer cracked or missing segments.
- Angular or parallel misalignment between motor and feedback shaft.
- Loose mounting feet on tacho or encoder.
- Key or keyway worn, causing micro-slip under load.
- Radial play on the feedback shaft bearing.
3.3 Current / Torque Limit Saturation (~15 %)
- Load demand exceeds configured torque limit (P152).
- Field-weakening region operation (constant-power, reduced torque).
- Mechanical jam (bearing failure, foreign body, product overfill).
- Acceleration ramp shorter than the mechanical system can follow.
3.4 Tuning and Configuration (~5 %)
- Speed controller P gain (P150) too high → oscillation → A031.
- Wrong tacho gain (P084 / P085) → magnitude error.
- Wrong direction wiring (analogue input polarity inverted).
- Encoder direction bit set incorrectly.
4. Pre-Diagnostic Preparation
4.1 Required Tools
- DriveMonitor software (6RA70) or Starter / Startdrive (6RA80 / SINAMICS DCM).
- PC with USB-to-serial converter (RS232) or USB cable for 6RA80.
- Digital multimeter with mV / mA / Ω ranges and diode test.
- Oscilloscope, ideally ≥ 20 MHz bandwidth, with AC coupling.
- Hand tachometer or optical strobe for speed verification.
- Fine-grit polishing paper (P800-P1000) for commutator cleaning.
- Allen keys, feeler gauge, dial indicator for coupling alignment.
- Insulation tester (megger) for cable / winding check (with armature disconnected).
4.2 Safety Precautions
- Lock out and tag the upstream AC supply (3-phase circuit breaker or isolator).
- Wait at least 5 minutes (or measure < 50 V DC at the DC bus) before touching armature terminals.
- Verify zero armature voltage with a meter before any mechanical work.
- The field circuit is typically lower voltage (≤ 325 V DC) but is still hazardous and must be de-energised separately.
- Always use one hand when probing a live DC bus.
- Follow local arc-flash PPE requirements; 6RA70/80 in 800 A+ ratings may require Category 2 PPE.
- Do not disconnect the tacho cable while the drive is running — the floating input can drift and produce erratic speed readings.
4.3 DriveMonitor Connection
- Connect the PC to the drive:
- 6RA70: serial cable from PC to connector
SS52/X300on the CUD1 board. - 6RA80: USB cable to
X300service port, or PROFIBUS / PROFINET to the CUD.
- 6RA70: serial cable from PC to connector
- Launch DriveMonitor. Configure the COM port: Settings → Serial Port → select COMx, baud 9600 (default), parity even, 8 data bits, 1 stop bit (or 19200 for newer firmwares).
- Online → Read All Parameters to upload the live parameter set from the drive.
- Open the
.dnlparameter dump (Parameter List → File → Open). - Set up a four-channel trace on:
n_setpoint,n_actual,I_armature, andP152 (torque limit). Trigger on A031 if available.
5. Tachogenerator Feedback Diagnostics
A DC tachogenerator produces an output voltage proportional to speed (commonly 60 V / 1000 rpm for a 6-pole industrial tacho, or 100 V / 1000 rpm for some European standards). Three diagnostic tests are recommended for any A031 that originates from a tacho feedback path.
5.1 Visual Inspection of the Commutator
- Isolate the drive and lock out the AC supply.
- Remove the tachogenerator cover and lift the brush holders.
- Inspect the commutator surface:
- Light copper colour with a thin brown patina: healthy.
- Heavy black carbon track, grooving, pitting, or uneven wear: brush material contamination, weak spring force, or both. Clean the commutator with fine-grit polishing paper (P800-P1000) by rotating the tacho shaft manually; do not use emery cloth (silicon carbide embeds in the copper).
- Measure brush length: brushes shorter than 50 % of original length are at end of life.
- Check spring pressure: weak or sticky springs cause intermittent contact and ripple.
5.2 Static Resistance Test
- Disconnect tacho leads at the drive terminals.
- Set the multimeter to the Ω range, connect to the two tacho output leads.
- Rotate the tacho shaft by hand through a full revolution.
- Read the resistance at multiple angles (every 30-45°).
| Reading | Interpretation |
|---|---|
| Constant 50-300 Ω throughout the rotation | Tacho OK |
| Varies more than 5 % from the mean | Commutator bars uneven, or shorted turns — replace tacho |
| Open circuit (OL) | Broken lead or brush wire |
| Short circuit (0 Ω) | Winding failure |
5.3 Dynamic Ripple Test (Oscilloscope)
The dynamic test is the most informative. Run the drive at a stable, known speed (e.g. 50 % of rated) and capture the tacho output at the drive terminals — not at the tacho itself, so the cable losses are included.
- Connect scope CH1 to tacho+ terminal, CH2 to tacho− terminal, both referenced to PE.
- Set scope to AC coupling, 100 mV/div, 20 ms/div.
- Run the drive at 50 % speed, hold for 10 s, capture a clean trace.
- Measure peak-to-peak ripple voltage (Vpp) and DC component (Vdc).
- Compute ripple ratio:
η = Vpp / Vdc × 100 %
| Ripple η | Status | Action |
|---|---|---|
| < 3 % | Excellent | None |
| 3 - 7 % | Acceptable | Schedule commutator cleaning |
| 7 - 10 % | Marginal | Clean commutator, inspect brushes, re-test |
| > 10 % | Failed | Replace tachogenerator |
5.4 Tacho Voltage Scaling Check
The Simoreg scaling parameter P084 (and P085 for direction) maps the tacho voltage to the rated speed. If the tacho has been replaced with a different voltage constant, the scaling must be re-entered or the actual speed reading will be wrong, and A031 will fire at high speed even though the mechanical speed is correct.
| Motor n_rated | Tacho V / 1000 rpm | Expected V_dc at n_rated | Required P084 setting |
|---|---|---|---|
| 1500 rpm | 60 V | 90.0 V | scale so 90 V = 100 % |
| 1750 rpm | 60 V | 105.0 V | scale so 105 V = 100 % |
| 2000 rpm | 100 V | 200.0 V | scale so 200 V = 100 % |
| 3000 rpm | 60 V | 180.0 V | scale so 180 V = 100 % |
After any tacho replacement, verify the actual mechanical speed with a hand tachometer and compare to the drive's n_actual reading. A 5 % mismatch is acceptable; more than 10 % means P084 must be re-entered.
5.5 Coupling Check Between Motor and Tacho
- Hand-rotate the assembly and listen for clicks (slipping key).
- Inspect flexible coupling elastomer for cracks or missing segments.
- Measure the gap between the two shafts with a dial indicator; parallel and angular misalignment should be < 0.1 mm.
- Check radial play on the tacho shaft bearing — > 0.05 mm play is a problem.
6. Encoder and Pulse Generator Feedback Diagnostics
When the speed feedback is an incremental encoder (P083 = 2 or P083 in encoder mode in 6RA80), check the following.
6.1 Signal Levels (HTL vs TTL)
| Encoder Type | Expected High | Expected Low | Simoreg Threshold |
|---|---|---|---|
| HTL (10-30 V) | > 14 V | < 6 V | Configurable, P14x range |
| TTL (5 V) | > 2.5 V | < 0.8 V | Fixed 5 V threshold |
6.2 Wiring and Shielding
- Use twisted-pair cable for A / A/ and B / B/ pairs.
- Shield must be bonded to PE at the drive end only (not at the encoder end) to avoid ground loops.
- Maximum cable length: 50 m for HTL at 100 kHz, 25 m for TTL.
- Route the encoder cable at least 200 mm away from VFD or DC armature cables. If crossing is unavoidable, cross at 90°.
- Inspect the connector at the encoder end for bent pins or contamination.
6.3 Direction and PPR Test
- Run the motor in the positive direction at low speed (10 % rated).
- Verify the encoder count increments (DriveMonitor trace on
n_encoder_rawor equivalent). - If
n_actualshows negative whenn_setis positive, swap A and A/ (or B and B/), or invert the count direction bit in the encoder configuration parameter (P083 or p083 depending on platform).
6.4 Encoder PPR Verification
The Simoreg scales the encoder pulse count to the motor's rated speed via a PPR (pulses per revolution) parameter. If the encoder has been replaced with a different PPR, the speed reading will be off by the ratio.
| Motor n_rated | Encoder PPR | Expected f at n_rated | Drive PPR setting |
|---|---|---|---|
| 1500 rpm | 1024 | 25.6 kHz | 1024 |
| 3000 rpm | 2048 | 102.4 kHz | 2048 |
| 1500 rpm | 2500 | 62.5 kHz | 2500 |
Calculate the expected pulse frequency: f_Hz = (n_rpm × PPR) / 60. Measure with a frequency counter on the A channel at rated speed. A 5 % deviation is acceptable; more indicates wrong PPR setting.
7. Back-EMF (EMF) Feedback Operation
In cost-sensitive applications the Simoreg can be run in EMF (armature voltage) feedback mode. The actual speed is derived from the back-EMF, calculated as V_emf = V_armature - I_armature × R_armature. A031 in EMF mode typically indicates one of the following:
- Armature resistance value wrong in the parameter set (P110 series on 6RA70) — re-measure with a Kelvin bridge or calculate from V / I.
- IR compensation mis-tuned (P111 / P112 on 6RA70).
- Field current fluctuating (field supply problem, loose field terminal, weak field stack).
Check field current stability (P260 or trace variable) before assuming a tachogenerator problem in EMF mode. If the field current sags under load, the calculated EMF will sag, the actual speed reading will sag, and A031 will fire even though the mechanical speed is correct.
8. Current and Torque Limit Verification
A drive sitting in current limit cannot accelerate the motor to the demanded speed, so the speed error grows and A031 fires after the configured delay. This is the second most common root cause in production environments.
8.1 Identifying the Limit Condition
- Run the drive from a low speed to rated speed while monitoring the trace.
- Watch
I_armature(P170 / r170) and the torque setpoint (P160 / r160). - If
I_armatureequals the configured current limit (P171 / P172) and the speed error is large, the drive is in torque limit. - Compare the actual torque to the configured limit (P152 / r152). If they match, the limit is the cause.
8.2 Current and Torque Limit Parameters
| Parameter (6RA70) | Parameter (6RA80 / DCM) | Description | Typical Value |
|---|---|---|---|
| P170 | r072 / p064 | System current limit (positive) | 1.0 × I_rated |
| P171 | p064[0] | Positive current limit (motoring) | 1.0 × I_rated |
| P172 | p064[1] | Negative current limit (regen) | -1.0 × I_rated |
| P152 | p150 | Torque setpoint limit | 1.0 pu |
| P153 | p151 | Torque ramp time | 0.5 - 2.0 s |
8.3 Common Load Issues
- Mechanical jam (bearing failure, foreign object in the process).
- Over-loaded product (process transient, batch overfill).
- Field-weakening region: at high speeds the field is weakened, so available torque is reduced.
- High-inertia load with insufficient acceleration ramp time (setpoint ramp too short).
9. Parameter Adjustment: P388 and the P390 Family
P388, P389, and P390 control the A031 monitoring function. They should NOT be changed to mask a fault, but in some commissioning situations a calibrated adjustment is appropriate.
9.1 When Adjustment Is Appropriate
- The drive is operating in a known-good condition but A031 fires during fast acceleration ramps. Widen the deviation band (e.g. 5 - 7 %) or extend the time delay (e.g. 5 - 6 s).
- The application has high cyclic load transients that mimic a tacho error and have been confirmed to be safe for the driven load.
- After a motor / gearbox swap where mechanical dynamics have changed.
9.2 When Adjustment Is NOT Appropriate
- A031 fires at steady-state speed — there is a real problem; do not mask it.
- A031 fires within the first 3 s of start-up with the default values — the load is too high or the speed controller is unstable.
- Tacho ripple is high, or coupling is loose — fix the cause, not the alarm.
9.3 Recommended Conservative Settings
Use these as a starting point only; verify with a full commissioning test.
P388.1 = 5.0 ; widen deviation to 5% (was 3%)
P388.2 = 4.0 ; extend delay to 4 s (was 3 s)
P390.1 = 1 ; keep alarm-only mode
P390.2 = 0 ; disable fault escalation
P390.3 = 0 ; default source routing
P390.4 = 0.5 ; small hysteresis
If A031 still fires after parameter adjustment with no mechanical or electrical fault, the speed controller tuning (P150 / P151 on 6RA70, p150 / p151 on 6RA80) is the next item to inspect.
10. Speed Controller Tuning Interaction
A mis-tuned speed controller can drive the actual speed into oscillation, which looks like a "speed error" to the monitoring block and triggers A031.
10.1 Signs of Tuning Problems
- Speed oscillates with a period of 0.1 - 1 s.
- Drive sounds rough or "hunts".
- Speed error oscillates around zero rather than settling.
10.2 Tuning Reference Values
| Parameter | Description | Conservative | Aggressive |
|---|---|---|---|
| P150 / p150 | Kp (proportional gain) | 0.5 | 5.0 |
| P151 / p151 | Tn (integral time, seconds) | 0.5 | 5.0 |
| P152 / p152 | Output limit (pu) | 1.0 | 1.0 |
| P153 / p153 | Ramp on speed setpoint | 1.0 s | 0.1 s |
Re-tune per the Siemens commissioning manual: increase P150 until the drive starts to oscillate, back off 30 %, then reduce P151 (i.e. increase the integral time constant) until steady-state error is acceptable. For the full procedure see the Simoreg 6RA70 / 6RA80 Commissioning Manual on the Siemens Industry Online Support portal.
11. Verification After Repair
11.1 Static Test
- Power up the drive, clear all alarms, run to 0 setpoint.
- Apply a small step in setpoint (5 % of rated).
- Watch
n_actualfollow with a 200 - 500 ms first-order response, no overshoot, no oscillation. - Run to 50 % rated speed, hold for 60 s, confirm A031 does not appear.
11.2 Dynamic Test
- Program a setpoint profile: 0 → 50 % → 100 % → 50 % → 0, with 5 s dwells.
- Run the profile from DriveMonitor.
- Verify the following in the captured trace:
- No A031 events.
-
n_actualtracksn_setpointwithin 3 % at all times. -
I_armaturedoes not stay at the current limit for more than 0.5 s. - No oscillation of
n_actualaroundn_setpoint.
11.3 Long-Run Test
- Run the drive on the actual production load for at least 1 hour.
- Monitor the alarm log: no A031 events.
- Verify the alarm history is clean: alarm count, last alarm timestamp, total run hours since last alarm.
12. Troubleshooting Matrix
| Symptom | Probable Cause | Diagnostic Step | Action |
|---|---|---|---|
| A031 at start-up, then clears | Acceleration ramp too short, current limit hit | Trace P171 / P172, I_arm | Extend ramp (ramp function generator) |
| A031 steady-state at high speed only | Tacho ripple high | Oscilloscope on tacho terminals | Replace tacho or clean commutator |
| A031 only under load | Current limit hit | Trace I_arm vs P171 | Inspect mechanical load, check bearings |
| A031 with noisy speed reading | Encoder cable shielding / routing | Check shield, routing, ground | Re-route cable, re-shield, check ground |
| A031 after long run, then constant | Tacho brush wear | Visual inspect, dynamic ripple test | Replace brushes / tacho |
| A031 after gear / coupling swap | Misalignment | Dial indicator | Re-align to < 0.05 mm |
| A031 with new motor | Wrong parameter scaling | Check P083, P084, P085 | Re-enter from motor nameplate |
| A031 with reading jumping | Loose terminal | Inspect, re-torque | Re-torque to 0.6 Nm |
| A031 with stable n_actual but wrong magnitude | Tacho gain error | Compare actual speed to tacho voltage | Adjust P084 / P085 |
| A031 with n_actual opposite sign of n_set | Wiring polarity reversed | Check tacho or encoder wiring | Swap A/A/ or invert P083 polarity |
| A031 only when ambient is hot | Tacho drift or field supply sag | Trace field current at temperature | Check field stack, fan, ventilation |
13. Related Alarms and Cross-Reference
| Alarm | Meaning | Co-occurrence with A031 |
|---|---|---|
| F031 | Speed monitor fault (shut-down) | Yes, after A031 escalation |
| A034 | Tacho monitoring (lost feedback) | Yes, when tacho is disconnected |
| A035 | Encoder monitoring | Yes, when encoder channel fails |
| A041 | Standstill monitoring | Sometimes, after A031 trips |
| A067 | Field current too low | Yes, in EMF mode |
| F035 | Encoder open circuit | Yes, encoder failure |
For related procedures, see the Simoreg 6RA70 / 6RA80 parameter list available from the Siemens 6RA70 product page on the Industry Online Support portal.
14. Field Notes and Caveats
- On 6RA70 firmware versions older than 2.5, P388 default is 5.0 % and P389 default is 5.0 s. Verify the default in the parameter help for the firmware loaded in your drive before interpreting the alarm.
- Some retrofit installations replace the original tacho with a digital encoder. If A031 appears only after the retrofit, suspect scaling (P083 / P084 / P085) and direction (A vs A/ swap) before suspecting the encoder itself.
- The Simoreg alarm log retains the last 8 (6RA70) or last 64 (6RA80 / DCM) alarm events with timestamp and frequency counter. Use it to distinguish "A031 fires once per shift" (transient) from "A031 fires every 30 s" (systemic).
- Drives operating above 1000 rpm with marginal tacho ripple can pass bench tests but fail in the field because of vibration-induced brush bounce. Verify ripple at the actual operating speed, not at a bench speed.
- Always check the drive's armature current at the moment A031 appears. If I_armature equals the current limit (P171 / P172) for the entire duration of the alarm, the load — not the feedback — is the cause. This is the single most useful 30-second check before tearing into the tachogenerator.
- If the tachogenerator's commutator has visible carbon deposition, clean it with fine-grit polishing paper (P800-P1000) by rotating the tacho shaft manually. Do not use emery cloth — silicon carbide particles embed in the copper and accelerate wear.
- Brushes shorter than 50 % of their original length, or with chipped / glazed contact faces, must be replaced as a set, not individually. Mixing new and old brushes causes uneven current distribution and accelerates the failure of the remaining old brushes.
What does A031 mean on a Simoreg DC Master drive?
A031 is the "Speed controller monitoring" alarm. It triggers when the magnitude of the speed error (|n_setpoint - n_actual|) exceeds the configured threshold (default 3 % of rated speed, P388) for a configured minimum duration (default 3.0 s, P389). It is a symptom alarm, not a fault by itself, and indicates either a feedback path problem, a mechanical coupling issue, or a current / torque limit condition.
Should I change P388 or P390 to clear A031?
Only as a last resort, after confirming the speed feedback, mechanical coupling, and current limit are all healthy. Increasing the threshold (P388) or extending the time delay (P389) can mask a real problem and lead to a more serious F031 trip or process quality issue. Always fix the underlying cause first, then adjust the monitor only if a documented application requirement justifies it.
How do I test if the tachogenerator is faulty?
Use two methods. (1) Static — disconnect the tacho and measure resistance between the two output leads while rotating by hand; the reading must be constant within ±5 %. (2) Dynamic — run the drive at a known speed, capture the tacho voltage on an oscilloscope at the drive terminals, and compute ripple ratio η = V_pp / V_dc. A reading above 10 % ripple indicates a worn tacho that must be replaced or a commutator that must be cleaned.
Can A031 be caused by a current limit condition?
Yes. If the load requires more torque than the drive can deliver, the motor slows down, the speed error grows, and A031 fires after the delay. Trace I_armature, P171, and P172 during the event. If I_armature equals the current limit for the duration of the alarm, the load demand — not the feedback path — is the cause. Address the mechanical load, raise the current limit (if motor permits), or extend the acceleration ramp.
What is the difference between A031 and F031?
A031 is a non-latching alarm: the drive continues to run, the alarm bit is set, the event is logged. F031 is a latching fault: the drive trips out, the contactor opens, and the drive must be reset. F031 is the consequence of A031 when the configuration word (P390.2 in 6RA70) is set to escalate, or when the speed error persists long enough to trigger the hard fault threshold.
Does A031 apply to SINAMICS DCM (6RA80 successor) as well?
Yes. The alarm code A031 is carried forward in the SINAMICS DCM firmware. The parameter numbering changes (p / r prefix instead of P), but the underlying speed monitoring logic is the same: threshold on r388, time delay on r389, configuration word on r390. The diagnostic procedure described in this article applies to both platforms with appropriate parameter renumbering. See the SINAMICS DCM parameter list on the Siemens Industry Online Support portal for the exact mapping.