Resolving SIMOTION D410-2 F14532 in Web Server Diagnostics

1. Problem Statement

F14532 is reported inside the SIMOTION D410-2 web server diagnostic buffer (Diag buffer) but cannot be located in the connected SINAMICS drive's AlarmHistory. The web server view, accessible through the D410-2 on-board Ethernet port (default URL http://<d410-2-ip>/simotion), exposes the controller-side fault memory. The AlarmHistory tool inside SIMOTION SCOUT or Startdrive exposes only the SINAMICS-side fault memory. Because the two diagnostic surfaces query different memories, a SIMOTION-originated fault never appears in the drive alarm log even when the drive and the controller are physically the same device.

This article resolves the diagnostic gap for engineers who:

• Observe a single F14532 entry in the web server diagnostic buffer with a timestamp but no associated drive-side fault.
• Cannot replicate F14532 in the SINAMICS AlarmHistory for DO1 (CU 320-2 integrated in the D410-2) or DO2 (drive object such as SERVO_02 or VECTOR_02).
• Need to clear F14532, prevent its recurrence, and validate the system on production machines.

2. SIMOTION D4x5-2 Diagnostic Architecture

The D4x5-2 family integrates a SIMOTION controller with a SINAMICS S120 control unit on a single piece of hardware. Diagnostic data is split between three independent fault memories:

SIMOTION faults and SINAMICS faults use overlapping numbering but live in different fault memories. F14532 is a SIMOTION fault and is therefore stored in the SIMOTION diagnostic buffer. The SINAMICS AlarmHistory, which is queried through the drive's own fault memory, will never show F14532 even if the underlying root cause lies in the drive's communication interface.

The D4x5-2 diagnostic buffer is exposed through three interfaces:

• Web server: HTTP access to http://<d410-2-ip>/simotion on the on-board PROFINET interface X150. Shows fault number, timestamp, Info1, Info2, reaction mask, and acknowledgement state.
• SCOUT device diagnostics: Project > right-click device > Diagnostics > Diagnostic buffer. Same data with additional context words.
• SIMOTION IT Diag: OPC UA server exposed by the D4x5-2 at opc.tcp://<d410-2-ip>:4840. Used by HMI panels and SCADA systems.

3. F14532 Fault Definition and Classification

F14532 is a SIMOTION runtime fault in the communication group (14xxx) indicating a configuration error in the SINAMICS Integrated communication path. It is raised when the runtime detects a mismatch between the configured and the actual topology of the SINAMICS Integrated interface, the slot assignment of the SINAMICS drive objects, the PROFIBUS/PROFINET telegram configuration, or the assignment of SIMOTION I/O addresses to SINAMICS telegram words.

The exact message text varies by firmware version. In SCOUT V4.4 SP3 the message reads "Configuration error SINAMICS Integrated". In SCOUT V5.2 and later, additional context words describe the affected sub-system (PROFIBUS, PROFINET, telegram, slot, or topology) and are visible in the Info1 and Info2 fields of the diagnostic buffer entry.

4. Why F14532 is Absent from the Drive AlarmHistory

The AlarmHistory dialog in SCOUT is generated by querying the SINAMICS drive's fault memory directly through the PROFIBUS or PROFINET bus. F14532 is never written to the SINAMICS fault memory because the fault is generated by the SIMOTION runtime, not by the SINAMICS firmware. The drive is the object of the configuration error, not the originator.

The AlarmHistory dialog scope is also limited to a single drive object. The dialog selector in SCOUT shows a dropdown for "DO" with values such as CU, SERVO_02, VECTOR_02, TM31, etc. Only one drive object can be selected at a time, so even if F14532 had a drive-side component, it would not appear in the AlarmHistory of an adjacent drive object. The user must select the correct DO in the AlarmHistory dialog to see drive-side faults. A SIMOTION-level F14xxx fault will still not appear, because it lives in the SIMOTION diagnostic buffer, not the SINAMICS fault memory.

The web server, by contrast, exposes the SIMOTION diagnostic buffer directly. It reads the SIMOTION-side fault memory and lists every F1xxxx fault with timestamp, additional information, reaction mask, and acknowledgement state. This is the reason F14532 is visible in the web server but invisible in the SINAMICS AlarmHistory.

The AlarmHistory dialog also has a known limitation on multi-DO projects: only the selected DO is queried. The D410-2 contains the CU 320-2 (DO1) and one or two drive objects (DO2, DO3). Selecting "CU" in the AlarmHistory dialog shows faults and alarms generated by the control unit firmware, not by the SIMOTION runtime. Selecting "SERVO_02" shows drive-side faults of the SERVO drive object. F14532 is in neither list because the SIMOTION runtime owns it.

5. Root Cause Categories for F14532

F14532 is a configuration error, so the underlying cause is a mismatch between the project configuration in SCOUT (or TIA Portal) and the actual installed hardware or programmed structure. The following categories, in descending order of frequency observed on production machines, cover approximately 90% of F14532 incidents on D4x5-2 systems:

6. Pre-Diagnostic Checklist

Before changing configuration, gather the following facts to localise the cause. The checklist is designed to be completed in 10 minutes with no production impact.

1. Capture the timestamp of the F14532 entry from the web server diagnostic buffer (column TimeStamp).
2. Cross-check the timestamp against any logged change of project, hardware, firmware, or wiring.
3. Open SCOUT, navigate to the affected D4x5-2 device, and select right-click > Diagnostics > Diagnostic buffer. Note the F14532 context words (Info1, Info2 fields).
4. Check the SIMOTION firmware version: Device > Properties > Device Version. Confirm it matches the SINAMICS Integrated firmware reported under Online > Accessible nodes > SINAMICS_Integrated > Properties > Firmware.
5. Verify that the target device on the D4x5-2 matches the actual hardware. In SCOUT, the device description is read from the controller on first online connection; if the description was hand-edited or imported from a different project, the comparison may fail.
6. Export the project archive (Project > Archive) before any change, to allow rollback.
7. Export the online SINAMICS parameter set (Target system > Upload to PG) for backup.

7. Step-by-Step Diagnostic Procedure

The following procedure isolates F14532 in approximately 10 minutes. Menu paths are stable from SCOUT V4.4 SP3 to V5.4; adapt as required for your version.

Step 1 - Confirm the diagnostic buffer entry

Open the web server at http://<d410-2-ip> with the default user simotion and the configured password. Navigate to Diagnostics > Diagnostic Buffer. Locate F14532 and capture the timestamp, Info1, Info2, reaction mask, and acknowledgement state.

Cross-check in SCOUT: right-click device > Diagnostics > Diagnostic buffer. The entries must match the web server view. If SCOUT shows additional F14532 entries that the web server does not show, the SIMOTION-IT OPC UA server is exposing a fresh log while the web server is showing a cached page; refresh the web server view.

Step 2 - Decode Info1 and Info2

The Info1 and Info2 fields in the diagnostic buffer contain the parameter number and sub-index that triggered F14532. Common decodings on D4x5-2:

The exact mapping is documented in the SIMOTION D4x5-2 manual "Communication faults" appendix. Use the values to direct the next diagnostic step.

Step 3 - Validate the device assignment

In the SCOUT project tree, right-click the D4x5-2 device and select Target system > Compare.... The "Compare" dialog lists every property whose online value differs from the offline value. A difference in Device type or Article number confirms a topology mismatch. Capture the article number of the actual hardware from the front panel label of the D4x5-2 and compare with the offline value.

Step 4 - Validate the SINAMICS Integrated assignment

Expand the D4x5-2 node in the project tree. The child node SINAMICS_Integrated must be present. Click Target system > Compare on the SINAMICS_Integrated node. Missing drive objects, wrong DO types, or duplicate drive objects on this node are the most common F14532 causes. Confirm the list of DOs matches the online view under Online > Accessible nodes > SINAMICS_Integrated > Drive objects.

Step 5 - Validate the PROFIBUS or PROFINET configuration

Open HW Config for the D4x5-2. Select the SINAMICS_Integrated node and view the slot assignments. Each drive object must be on a unique slot, and the configured telegram (Standard Telegram 1, 2, 3, 4, 5, 6, 7, 9, 102, 105, 106, 116, 118, 125, 126, 136, 138, 139, etc.) must match the telegram selected in the drive's parameter p0922 and in the SIMOTION axis configuration. A mismatch raises F14532 on ramp-up and on the first configuration download.

Step 6 - Validate the I/O address mapping

Compare the I/O addresses of the SINAMICS telegrams against the addresses used by the SIMOTION application. The addresses are listed in HW Config under Properties > Addresses of the telegram slot. Duplicate or overlapping addresses (commonly I/O address 0..63) cause F14532 on first access to the axis. Use the SIMOTION process image browser (Project > Process image) to check for collisions.

Step 7 - Validate the firmware versions

In SCOUT, Online > Accessible nodes lists the D4x5-2 and the SINAMICS_Integrated with their firmware versions. Compare with Device > Properties > Firmware version in the offline project. Mismatched firmware (for example SIMOTION V4.5 with SINAMICS V4.4) is documented as incompatible on D4x5-2 and is a known F14532 trigger.

8. Configuration Validation Table

Use the following table to cross-check the offline configuration with the online device. A "match" in every row is a prerequisite to a clean ramp-up after a project download.

9. Resolution Procedures

Apply the resolution that matches the root cause identified in Section 8. After each change, perform a complete download of the project to the D4x5-2 and a power cycle of the controller. The SINAMICS Integrated line of the controller may also require an independent power cycle on the X124 connector.

9A - Topology mismatch

1. Open the device catalog in HW Config (View > Catalog).
2. Drag the correct D4x5-2 (matching the actual article number on the front panel) into the project from the catalog.
3. Re-assign the SINAMICS_Integrated and its drive objects from the old device to the new one.
4. Compile HW Config (Station > Consistency check), then compile the SCOUT project.
5. Download the project to the controller and perform a power cycle.

9B - Slot or telegram mismatch

1. Open HW Config and select the SINAMICS_Integrated node.
2. Double-click the affected drive object slot and select the correct telegram. The dropdown lists all standard telegrams plus Siemens-specific telegrams (e.g. 102, 103, 105, 106, 116, 118, 125, 126, 136, 138, 139).
3. Open the drive's parameter list (in SCOUT expert list) and set p0922 to the same telegram number.
4. Compile, download, power cycle.

9C - Missing SINAMICS Integrated assignment

1. In the SCOUT project tree, right-click the D4x5-2 and select Insert SINAMICS Integrated if the option is available.
2. If the option is greyed out, the project was created against a different controller variant. Re-create the project from the current device's Insert SIMOTION D4x5 template.
3. Insert the required drive objects (SERVO, VECTOR, CU) and configure their telegrams.
4. Compile, download, power cycle.

9D - Address overlap

1. Open HW Config and select the SINAMICS_Integrated node.
2. For each telegram slot, set unique address ranges. Convention on D4x5-2: SIMOTION I/O starts at 0, SINAMICS telegrams start at 256 or higher.
3. Update the address references in the SIMOTION application (for example TO axis I/O mapping, _getAxisWord/_setAxisWord accesses) to match the new range.
4. Compile, download, power cycle.

9E - Firmware mismatch

1. Identify the firmware package matching the project: SIMOTION firmware is delivered as a .zip archive containing the SINAMICS firmware and the SIMOTION runtime.
2. Place the firmware package on a Siemens CF card (article number 6ES7648-2xxxxx) and reboot the controller, or use SCOUT Online > Accessible nodes > Firmware update through the Ethernet port.
3. After firmware update, repeat the validation in Section 8.

9F - Hot-plug or module change

1. Power down the SINAMICS line modules and the motor modules.
2. Verify the article numbers on the modules match the project configuration. Replace any mismatched modules.
3. Power up in the correct sequence: line module first, then motor modules, then the SIMOTION D4x5-2.
4. Acknowledge F14532 and run the verification procedure in Section 10.

9G - GSD/GSDML version conflict

1. Identify the SINAMICS firmware version on the controller (Online > Accessible nodes > SINAMICS_Integrated > Firmware).
2. Open the Siemens Product Support page for the SINAMICS Integrated device and download the matching GSD or GSDML file.
3. In SCOUT, Options > Install GSD file and import the new GSD/GSDML.
4. Update the device in HW Config and re-assign the slots.
5. Compile, download, power cycle.

10. Verification and Commissioning Checks

After applying a resolution, perform the following checks. F14532 must not reappear in the diagnostic buffer during a 30-minute observation window with the drive running under normal load.

1. Power cycle the D4x5-2 (CPU run/stop switch to STOP, then RUN, or full power cycle).
2. Open the web server diagnostic buffer and confirm F14532 is no longer present at the top of the list.
3. Run the SIMOTION application and exercise each axis: enable, jog, reference, move to absolute position. Verify the axis status word (TO.AxisState) reaches Standstill and Motion without intermediate errors.
4. Open the SINAMICS AlarmHistory and confirm no drive-side faults have appeared at the same timestamps as the previous F14532 events.
5. Run the SCOUT trace on the SINAMICS_Integrated bus and verify telegram timing is steady (no retries, no late telegrams, life-sign counter increments).
6. Force an error condition (e.g. unplug the encoder cable momentarily) and verify the system reports the expected drive-side fault and recovers correctly after reconnection.

11. Related SIMOTION F14xxx Faults

Use this table to disambiguate F14532 from nearby fault codes in the communication group. All entries below are SIMOTION-side faults and will not appear in the SINAMICS AlarmHistory.

For deeper reference, the SIMOTION D4x5-2 Manual lists F14532 in the communication fault group, and the SIMOTION SCOUT online help links each F1xxxx fault to the configuration parameter that triggered it. The manual is available from the Siemens Industry Online Support portal at https://support.industry.siemens.com.

12. Frequently Asked Questions