Resolving SINAMICS V70 Fault F52985: 1FL6 Absolute Encoder ID

Problem Overview

The SINAMICS V70 servo drive (order code 6SL3210-5DE21-8UA0) raises fault F52985 ("Absolute encoder motor wrong") when paired with a SIMOTICS S-1FL6 high-inertia servo motor equipped with an absolute encoder (for example 1FL6096-1AC61-0LB1). The drive cannot run the motor because the internally stored motor identity record does not match the connected encoder type, or the loaded firmware does not recognize the motor's electronic nameplate.

Field evidence shows the condition is independent of the power cable, signal cable, or drive hardware: swapping the suspect motor to a known-good V70 still raises F52985, and swapping a known-good absolute encoder motor back onto the suspect drive also raises the fault. This narrows the cause to either the motor/encoder electronics or the drive firmware revision.

Affected Hardware and Part Numbers

The fault pattern is documented for the following Siemens part numbers used in the original installation:

The 1FL6096 frame size is 96 mm; the 1AC61 winding produces the medium-inertia constant for this frame. The trailing -0LA1 versus -0LB1 designator distinguishes the encoder option: LA = incremental, LB = absolute multi-turn.

Fault Code F52985: Absolute Encoder Motor Wrong

F52985 is a drive-side fault (off/reaction = STOP2 by default) in the SINAMICS V70/V90 message class for encoder / motor identification. The fault is raised immediately on the first power-on commissioning attempt or on the first enable after a motor swap.

The reference description is published in the SINAMICS V90 PROFINET / SIMOTICS S-1FL6 Operating Instructions (109763150), which covers the same firmware platform as the V70 pulse-train variant.

Related Faults: F52983 and Adjacent Codes

When troubleshooting F52985 you will frequently see the following adjacent faults in the alarm buffer. Treat them as a logical cluster:

If F52983 is present, fix the wiring first. F52985 with F52983 cleared points firmly at the encoder electronics or the firmware compatibility.

Root Cause Analysis

F52985 is raised by the SINAMICS firmware's motor identification handshake. On power-up, the drive reads the electronic nameplate stored inside the absolute encoder over the EnDat / SSI-style protocol. The nameplate contains the motor's part number, the Motor ID, and the encoder resolution. The drive then compares the Motor ID against the internal database shipped with the firmware.

Two failure paths lead to F52985:

1. Database miss (most common on new motors): the motor was manufactured with a Motor ID that is newer than the firmware's database. The drive correctly reads the encoder, but it cannot match the ID to a known motor record, so it raises F52985 to refuse operation with an unknown motor.
2. Encoder electronics failure: the encoder returns a corrupted or default ID (typically 0). p29000 reads 0 even though the nameplate decal is intact, and the drive cannot validate the motor.

Pre-Firmware Diagnostic Procedure

Execute the following steps before requesting a firmware update or replacing hardware. The full sequence takes roughly 15 minutes per drive.

1. Record the alarm buffer. On the BOP, navigate to the alarm history and capture the timestamp, fault number, and fault value of every F5298x event since the last power-on. Cross-check whether F52985 appears once on first enable or repeatedly on every enable.
2. Read p29000 (Motor ID). On the BOP, set the parameter filter to "all parameters" (the default view hides commissioning parameters) and read p29000. Note the value. If p29000 = 0, the encoder is returning a default ID — proceed to the encoder integrity section.
3. Read the drive firmware version. Note the firmware version displayed on the BOP splash screen and in r0018 / r0965. Cross-reference against the SINAMICS V70 firmware release notes for Motor ID support tables.
4. Visually inspect the motor nameplate. Confirm the part number matches the 1FL6096-1AC61-0LB1 designator and note the Motor ID printed in the "MOT ID" field. The expected format on 1FL6 nameplates is a decimal integer that the drive displays in p29000 once initialised.
5. Cross-swap with a known-good drive. Connect the suspect absolute-encoder motor to a different V70 of the same frame size. If F52985 follows the motor, the motor's encoder is the failing element. If F52985 stays with the drive, the drive firmware is the failing element.
6. Cross-swap with a known-good motor. Connect a known-good 1FL6096-1AC61-0LB1 (or compatible absolute-encoder 1FL6) to the suspect drive. If F52985 clears, the original motor is the failing element.

Parameter p29000 Motor ID Verification

Parameter p29000 is the SINAMICS V70/V70 PN parameter for the active Motor ID. It is read/write only on incremental encoder configurations; for absolute-encoder motors the drive writes the value internally during the initial electronic nameplate read and refuses manual writes to prevent corruption of the multi-turn position.

Manual write of p29000 is blocked when an absolute encoder is detected. This is correct behaviour: the multi-turn absolute position is bound to the encoder's electronic nameplate, and rewriting the Motor ID would orphan the absolute position counter. The correct path to clear F52985 is firmware update (database miss) or encoder replacement (EEPROM corruption).

Firmware Update Methods for SINAMICS V70

The SINAMICS V70 supports a constrained set of firmware update paths. The availability of each path depends on the firmware version currently loaded and on the variant (pulse-train V70 versus PROFINET V90 PN). Always cross-check the update path against the current Siemens Industry Online Support firmware release notes for the exact MLFB 6SL3210-5DE21-8UA0 before proceeding.

1. SINAMICS V-ASSISTANT (commissioning tool) over USB / RS232. Connect a PC running SINAMICS V-ASSISTANT to the V70 X10 service port, perform an online connection, and load the firmware image from the V-ASSISTANT firmware library. This is the most commonly supported path on the pulse-train V70.
2. Webserver (V90 PN variant only). On PROFINET variants the firmware can be loaded via the integrated webserver at the drive's IP address. The pulse-train V70 in MLFB 6SL3210-5DE21-8UA0 typically does not expose a webserver; verify on the drive splash screen.
3. Memory card update. The V70 has an SD card slot that accepts a SIMATIC memory card image (for example 6ES7954-8LB01-0AA0) loaded with the firmware. The card part number is shared with the S7-1200 CPU family; confirm the SINAMICS V70 firmware loader accepts this card family by reading the release notes. The card slot polarisation is standard SD; insert with contacts facing the front display.
4. Factory programming by Siemens Service. If no field path is available, drives can be returned to a Siemens Service Center for firmware programming. This is the most expensive option but is the safest path when the drive is in a critical production line.

SD Card Update Path in Detail

When using the SIMATIC memory card 6ES7954-8LB01-0AA0, follow the manufacturer's documented procedure for a SINAMICS card-based firmware load. The general pattern is:

1. Power down the drive and remove the protective cover from the SD card slot (front of the BOP).
2. Insert the SD card with the firmware image. The card must contain the SINAMICS firmware image in the directory structure expected by the loader (refer to the firmware release notes for the exact path).
3. Power on the drive. The BOP will display a progress bar while the firmware is being written to internal flash. Typical write time is 3 to 8 minutes depending on firmware size.
4. When the BOP returns to the standard status display, power-cycle the drive to activate the new firmware.
5. Re-read p29000 and re-attempt commissioning. The Motor ID for the 1FL6096-1AC61-0LB1 should now be recognised and p29000 should display the nameplate value.

Encoder Hardware Replacement Procedure

If the cross-swap test and p29000 = 0 reading confirm an encoder-side failure, the encoder module can be replaced in the field. SIMOTICS S-1FL6 encoders are modular: the encoder sub-assembly slides out of the rear of the motor and is retained by a locking ring. Use only Siemens OEM encoder modules rated for the 1FL6 family — third-party encoders will fail the Motor ID handshake even if electrically compatible.

1. Isolate and lock out the drive. Wait 5 minutes for the DC bus to discharge below 50 V (verify with a CAT III 600 V meter on the DC+ and DC- terminals).
2. Remove the motor from the machine axis. Lay the motor on a clean, ESD-safe surface with the rear (encoder end) facing up.
3. Remove the encoder cover plate. Two M3 cap screws retain the plate; use a 2.5 mm hex key.
4. Release the encoder locking ring. The ring is a 17 mm spanner nut; rotate counter-clockwise to release. Do not use pipe grips on the encoder body.
5. Withdraw the encoder module straight out of the motor housing. The EnDat / SSI mating connector will disconnect as the module clears the bore.
6. Inspect the encoder mating connector inside the motor for contamination, bent pins, or coolant ingress. Clean with isopropyl alcohol and lint-free swabs if necessary.
7. Insert the replacement encoder module, ensuring the connector seats fully. Tighten the locking ring to 2.5 Nm using a calibrated torque wrench.
8. Refit the cover plate. Refit the motor to the machine.
9. Power on the drive. The first commissioning will re-read the encoder and populate p29000 from the new nameplate. The multi-turn absolute position is now referenced to the new encoder — re-home the axis as a normal commissioning step.

Verification and Commissioning Checks

After the firmware update and / or encoder replacement, validate the repair with the following sequence before returning the axis to production:

1. Power on and verify p29000 now reads the nameplate value (non-zero, matching the decal).
2. Run the BOP jog test at low speed (5 to 10 rpm) in both directions. Listen for abnormal noise and monitor motor current in r0027; current should be within 30 % of the motor's rated continuous current at no load.
3. Verify the absolute encoder retention: power off, wait 30 seconds, power on, and confirm the drive restores the absolute position without requesting a re-home. If the drive requests a re-home, the encoder has not retained the multi-turn count and the replacement module is suspect.
4. Clear the alarm buffer and run a full enable / disable cycle. No F5298x faults should be raised.
5. Run the drive through the axis's commissioning profile and record the results in the machine's validation log.

Related Parameters for Field Engineers

Frequently Asked Questions