Sister article: SINAMICS F codes to 828D display numbers – full Chinese cross-reference. Related: 840D sl / 828D UAFEHL alarm localization, 828D PLC sign-of-life alarm 2000/2001, 828D common machine data quick reference, 828D/840D following error and contour tuning.
1.1 How the numbering maps: manual F3xxxx vs screen 230xxx

Sort by family first, then look up the individual code – it removes half the wasted diagnosis:
| Family | Manual form | 828D/840D display | Class | Owned by |
|---|---|---|---|---|
| Power unit | F3xxxx | 230xxx (six digits) | Fault, stop | Power module / drive object |
| Drive object | F0xxxx | see local diagnostic screen | Fault, stop | One drive object (motor / encoder) |
| Communication | F2xxxx | see local diagnostic screen | Fault, stop | DRIVE-CLiQ link |
| Warning | A3xxxx / A0xxxx | 6xxxxx band (version dependent) | Warning, no stop | Drive object / communication |
Table 1. What each numbering family covers; display numbers follow the system version and the local diagnostic screen
The classic trap: F3xxxx often maps to 230xxx on 828D, but it is not a simple numeric offset – individual codes and firmware versions do not always follow the pattern. Verify every F-code to 230xxx mapping against the manual for your own machine; do not copy another machine’s table. The A/F distinction tells you whether the drive stops, which decides how urgently you must react.
1.2 Power unit family F300xx, code by code

| F code | 828D display | Meaning | First check |
|---|---|---|---|
| F30001 | 230001 | Power unit overcurrent | Check power cable to ground / between phases, motor insulation, current transformer, then the power module last |
| F30002 | 230002 | DC link overvoltage | Check braking resistor and chopper, regenerative settings, supply voltage and DC link monitoring |
| F30003 | 230003 | DC link undervoltage | Check supply phase loss / dip, 24 V supply, fuses and control power |
| F30004 | 230004 | Inverter overtemperature | Check cooling fan, heat-sink airflow, ambient temperature and load |
| F30005 | 230005 | I2t overload | Check load and accel/decel times, whether motor rated current matches parameters |
| F30011 | 230011 | Main circuit phase loss | Check fuses, power cable, line reactor; a leftover star point in a star-delta setup gives the same symptom |
| F30020 | 230020 | Configuration not supported | Check drive-object configuration, firmware, current-loop dynamic request – fix configuration, not hardware |
| F30021 | 230021 | Ground fault | Check power cable, motor insulation, current transformer, brake closing instant, braking resistor short (see r0949 split) |
| F30050 | 230050 | 24 V overvoltage | Check 24 V supply output, external supply feed-in and terminal voltage |
Table 2. Common power-unit F codes, four-way reference (display numbers and fault values follow the local diagnostic manual)
Of these nine, F30011 and F30021 are most often misread as a bad module: for F30011 check the wiring method and any leftover star point first; for F30021 read r0949 to see which branch you are in before deciding between cable and module. Working through these two before swapping hardware avoids a lot of downtime and spare-part waste.
1.3 F30020 configuration not supported: fix configuration, not hardware
F30020 means a requested function is not supported by the current configuration – not a hardware failure. Typical triggers: an excessive current-loop dynamic request, DRIVE-CLiQ timing not permitted, firmware incompatible with the configuration, or initialization not complete.
Field order: note the full alarm number and the drive object that raised it -> look up that entry’s fault value -> decide configuration versus hardware -> isolate power before checking topology and firmware -> after changing configuration do a POWER ON. Configuration changes need a POWER ON to take effect; clearing the alarm does not mean the configuration was applied.
1.4 F30021 ground fault: r0949 decides cable versus module
F30021 has several documented causes: power cable ground fault or short, poor motor insulation, current transformer fault, the transient when the brake closes, a braking resistor short. The r0949 fault value is the fork in the road: r0949 = 0 points more to hardware DC monitoring action or a braking resistor short; r0949 > 0 relates to the total current amplitude.
The exact fault-value conventions must be checked against the manual for your version – definitions are not identical across releases. Check insulation and cabling first, evaluate the power module only after external shorts are ruled out.
1.5 F07011 motor overtemperature: three sensing paths

| F code | 828D display | Meaning | First check |
|---|---|---|---|
| F07011 | see local diagnostic | Motor overtemperature | Check KTY84 / PT1000 sensor, PTC normally-closed contact, additional overload protection – three separate paths |
| F07012 | see local diagnostic | Drive overtemperature | Check drive cooling, fan, ambient temperature |
| F07013 | see local diagnostic | Drive overcurrent | Check motor and power cable, output to ground |
| F07050 | see local diagnostic | Drive parameter error | Check drive-object parameters against firmware version |
| F31100 / F31110 | see local diagnostic | Encoder / measuring system fault | Check encoder cable, DRIVE-CLiQ topology and connectors |
Table 3. Common drive and encoder family F codes (display numbers follow the local diagnostic screen)
The fault value on F07011 carries real meaning (in some versions 200 is the I2t model channel and 400 is the additional overload protection trip), and the two actions are completely different – one is a thermal-model parameter and load issue, the other an external protection circuit. Read the exact fault-value definition on your own machine before acting.
1.6 A30010 sign-of-life lost: swap the cable and see if the alarm follows
A30010 (sign of life lost) is a communication-family warning: common causes are a loose or badly shielded DRIVE-CLiQ cable, a motor module fault, a 24 V dip, or a topology change without re-detection.
The one decisive test: swap a cable and see whether the alarm follows – if it follows, it is the cable or connector; if not, it is the module or topology configuration. Compared with repeated resets or swapping modules, this is the fastest move. A-class alarms do not stop the machine, but they often precede a more serious fault – do not ignore them for long.
1.7 Fault value r0949 quick reference: the configuration versus hardware fork

| Alarm | Typical r0949 | Points to | Action |
|---|---|---|---|
| F30020 | low four bits 0-6 | Configuration / timing / firmware | Change configuration, check firmware, POWER ON |
| F30021 | = 0 | Hardware DC monitoring or braking resistor short | Check braking resistor and DC circuit |
| F30021 | > 0 | Related to total current amplitude | Check cable, motor insulation, ground |
| F07011 | version dependent (e.g. 200 / 400) | Thermal model channel / additional overload protection | Parameter-load issue versus external protection circuit |
Table 4. How to read fault value r0949 (exact definitions follow the manual for your version)
Remember this: the fault value decides the branch between configuration, hardware and wiring. Copying only the alarm number and ignoring the fault value throws away half the diagnostic information.
1.8 Encoder family and supplementary codes
Field-circulated SINAMICS diagnostic lists include encoder-family codes F31100 / F31101 / F31110 / F31112 / F31117 / F31130 / F31150, plus a supplementary set F07403 / F7452 / F7453 / F7491 / F7492 / F7493. These come from third-party field lists and must be checked entry by entry against the manual supplied with your machine before being used as a criterion. Note that F7452 / F7453 belong to EPOS and limit functions, a different function domain from the main drive alarms – do not read them on the same table.
The common entry point for encoder-family faults: is the DRIVE-CLiQ topology consistent with the installed hardware -> encoder cable and connectors -> reading head / encoder itself -> whether 24 V dipped at the moment of the fault.
1.9 Reset and POWER ON rules
| Alarm class | POWER ON needed | Key point |
|---|---|---|
| A-class warning | Usually POWER ON to confirm | After clearing, watch for recurrence |
| Configuration fault (e.g. F30020) | POWER ON after change | Reset is not the same as configuration applied |
| Hardware / wiring fault | Reset after root cause removed | Remove the root cause before reset, never run with a latent fault |
Table 5. When to reset and when to POWER ON (follow the local diagnostic manual)
Three checks before replacing any module: is the DRIVE-CLiQ topology consistent with the hardware, what firmware version is fitted, and did the 24 V dip at the moment of the fault. Rule these out before deciding to swap a module.
1.10 Sources, version and compliance note
This page only summarizes number mapping, fault-value reading direction and first checks. It does not reproduce Siemens diagnostic manual text and provides no manual mirrors or download links. Codes, display numbers and fault values come from common field diagnostic frameworks, compiled 2026-11-19. Display numbers and fault-value definitions can differ across system versions and drive objects – on site, the official diagnostic manual for the matching version and the machine’s own diagnostic screen are authoritative.
For the full troubleshooting method, see the sister article on SINAMICS F-code diagnosis (230020 on 828D) and the guide to layering 828D / 840D servo alarms 25000 / 25010 / 25201, listed in further reading at the end.
Frequently Asked Questions
How do SINAMICS F codes map to the six-digit numbers shown on SINUMERIK?
On most 828D systems F3xxxx corresponds to a 230xxx display number, but it is not a simple numeric offset – individual codes and firmware versions differ. Verify each entry against the manual for your own version; do not copy another machine’s table.
Are F30020 and 230020 the same fault?
Yes – the same fault written two ways: the manual says F30020, the 828D screen shows 230020. It is a “configuration not supported” case, so the action is to fix configuration, check firmware and do a POWER ON, not to replace the power module.
Why include fault value r0949 in an F-code table?
Because the fault value decides the diagnostic direction: it is the fork between configuration, hardware and wiring faults. For F30021, r0949 = 0 versus greater than 0 points respectively to the braking resistor / DC circuit and to external cabling / insulation. Exact definitions follow the manual for your version.
Last updated: 2026-11-19
Beyond the cross-reference: F-code troubleshooting and r0949 reading
Where to go next
- FANUC Troubleshooting — the full guide library: alarms, diagnosis numbers, servo, spindle, PMC and electrical faults, organised by symptom.
- CNC Repair Tools — which instrument measures what: multimeters, clamp meters, insulation testers and oscilloscopes, with the specification that actually matters.
- Remote Technical Support — have the readings reviewed with you: alarm reverse lookup, PMC ladder analysis and servo tuning advice by call. Repair companies and integrators welcome.
- Buying & Ownership Decisions — refurbished vs new, used-machine checks, software licensing and manuals: spend with the field facts in hand.
Read the guide, get the right instrument, or walk the diagnosis through with someone — pick whichever you need.










































暂无评论内容