RAC / TDA / KDA fault-clearance guidelines
Edition: WAR1 · publication 270218
Manufacturer fault-clearance guideline for AC main spindle drives. Match the installed controller and edition before using the procedures.
Diagnostic reference library / Indramat & Rexroth
Find the reference behind the fault code.
Start with the equipment family and firmware. Browse diagnostic indexes, original troubleshooting excerpts and fault-clearance guidelines—then match the document to your machine.
Machine down?Preserve the display, then send the label and cabinet photos.Mon-Fri, 8am-6pm CT. After hours, upload the evidence for review when the team returns.
Choose the document, not just the number
One display. Different generations.
The same code can appear in more than one firmware family. These references help you locate the applicable documentation; a search match does not establish the cause of a fault.
What is included?
Guide / excerpt Supplied troubleshooting content; check the listed scope.
Diagnostic index Code titles and page pointers, not the full procedures.
Find the right fault reference.
Search by family, firmware, document number or a listed fault code.
1references shown
Punctuation and spaces are optional. Fault-code search finds exact F/E/A/C/P/D codes in searchable PDF text, not a diagnosis. Scanned pages, numeric-only and hexadecimal codes are not fully indexed. Match the hardware and firmware before using any reference.
These reference copies preserve their original source attribution. Index page numbers point to the parent manual, not necessarily a page in the supplied PDF. This is a selected library, not an exhaustive list of every fault or firmware edition. Electrical troubleshooting must be performed by qualified personnel using the complete applicable safety and machine documentation.
Four-part fault record
Capture what the machine knew at the moment of failure.
Preserve the message
Photograph the complete display, indicator pattern and any secondary message before it is cleared.
Identify the exact unit
Record the complete DKC, DDS, HDS, RAC, supply or control type code - including design generation and suffix.
Record the release
Capture firmware, software module, function ID/version, option hardware and removable-memory labels.
Describe the sequence
State what the machine was doing, what changed recently and whether the fault returns consistently.
Use the correct manual family
A displayed code should be interpreted only inside the documentation for the installed hardware and firmware generation. Start with the product family, then choose the edition-specific official record.
Describe evidence, not an assumed cause
Include loss of motion, overtemperature, communication loss, audible noise, intermittent behavior or a trip during a specific machine event. Do not turn one code into a board-level diagnosis before the system is reviewed.
Fault-code questions
Preserve first. Interpret second.
Why is the hardware code needed with the fault code?
The same displayed number or letter sequence can belong to different product and firmware families. The complete unit and firmware identify the applicable manual.
Should I reset the drive before taking photos?
Preserve the displayed information first. Follow only the machine builder and applicable official manual procedures through qualified personnel.
Can a fault code prove which component failed?
Not by itself. A code is diagnostic evidence that must be interpreted with the exact hardware, firmware, machine state and observed behavior.
Availability · repair · exchange
Send the complete code.
The suffix can change electrical and mechanical compatibility. Include every character and a clear nameplate photo.