Resolving SINAMICS S120 F01360 Topology Error on CU320-2 DP

1. Problem Statement: F01360 on SINAMICS S120 CU320-2 DP

The fault F01360 is reported by a SINAMICS S120 control unit CU320-2 DP (MLFB 6SL3040-1MA00-0AA0) when the controller is powered up with a DRIVE-CLiQ topology that does not match the expected (commissioned) topology. The fault appears immediately after the control unit boots, even with a clean CompactFlash card and no project loaded, and it persists through normal power cycles.

In a typical field occurrence, the following devices are connected to the CU320-2 DP via DRIVE-CLiQ:

• Control Unit: 6SL3040-1MA00-0AA0 (CU320-2 DP)
• Active Line Module (Smart Line / Active Line): 6SL3310-1TE35-0AA3 (or the related -0AA0 variant)
• Sensor Module or Terminal Module: 6SL3055-0AA00-2TA0
• Optional Communication Board / CF card: 6SL3054-0ED00-1BA0 upgraded to firmware 4.5 / 4.7

When all three DRIVE-CLiQ devices are present, the control unit reports F01360 and the drive will not enter Run state. Disconnecting the Line Module removes the fault, which confirms the Line Module is the trigger component.

2. F01360 Fault Definition and Value (r949)

F01360 belongs to the SINAMICS S120 fault class "Topology / component assignment errors". The fault is raised by the control unit during topology comparison and indicates that the actual DRIVE-CLiQ topology seen on the ports differs from the target topology stored on the CompactFlash card or in the project.

The supplementary fault value is stored in parameter r949 (fault value). Decoding r949 for F01360 follows the standard SINAMICS fault-value convention: it contains an index that points to the affected DRIVE-CLiQ node, the port number, and a reason code identifying the type of topology violation. Always read r949 before clearing the fault so the offending component is positively identified.

Typical r949 sub-reasons in this fault class include:

• 1 – Component at this DRIVE-CLiQ node not equal to target
• 2 – Topology comparison: component type differs
• 3 – Topology comparison: component MLFB / hardware revision not accepted by current firmware
• 4 – Topology comparison: component connected but not configured (or vice versa)

3. Affected Hardware and Part-Number Suffix

The root cause of the F01360 in this case study is the MLFB suffix of the Active Line Module. The 6SL3310-1TE35-0AAx family exists in at least two hardware revisions, identifiable by the final suffix:

The final 4-character suffix encodes the hardware revision, feature level, and release matrix of the module. A CU320-2 DP running firmware V4.5 / V4.7 has an internal allow-list of which Line Module suffixes it will accept in a given DRIVE-CLiQ port. If the connected Line Module's suffix is not on the allow-list, the topology comparison fails and F01360 is reported.

4. Compatibility Matrix Observed in the Field

The following combinations have been observed on a working test bench with firmware V4.5 / V4.7:

From this matrix the line of demarcation is the Line Module suffix combined with the CU320-2 DP variant 1MA. The -0AA0 suffix on the Line Module is not accepted by the 1MA CU320-2 DP at firmware V4.5 / V4.7, while the -0AA3 suffix is accepted. The control unit variant 0MA accepts the -0AA3 Line Module as well.

5. Root Cause Analysis

F01360 in this configuration is a DRIVE-CLiQ topology component-mismatch fault, not a configuration or licensing fault. The firmware of the CU320-2 DP performs a hardware-compatibility check during power-up, comparing the MLFB and hardware revision of every connected DRIVE-CLiQ device against the version of the control unit. The check has three outcomes:

1. Component found in target topology and hardware accepted → no fault.
2. Component found, MLFB matches the family, but hardware suffix is not in the firmware allow-list → F01360.
3. Component missing or not in target topology → F01350 (component missing) or F01360 (depending on reason).

Common contributors that produce the same fault signature and should be excluded first:

• Wrong / corrupt CompactFlash card – a clean card with no project reproduces the fault, which proves the project is not the cause. A correct, freshly formatted CF card is therefore not the fix.
• Missing license – license errors raise F13000-class faults, not F01360.
• Firmware mismatch on the COMM BOARD / SMC30 – would raise F01350 / F01357 on the specific node, not a general topology error.
• DRIVE-CLiQ cable defect – a defective cable prevents the control unit from reading the component and the node shows as missing, not mismatched.

Once those are eliminated, the only remaining cause is hardware-revision compatibility between the CU320-2 DP and the Line Module.

6. Pre-Work: What to Capture Before Power-Down

Before swapping modules or re-commissioning, capture the following so the repair is fully documented:

1. Read the active fault buffer with r949 and write down the fault value.
2. Read the alarm buffer (r2122) for any associated warnings such as A01360, A01350, A01357.
3. Read the actual topology from the CU320-2 DP: r0098[0] (Control Unit order number / MLFB), and the device-identification parameters for every connected DRIVE-CLiQ node (r9781, r9782, r9785 for the Line Module).
4. Photograph the affected Line Module nameplate; record the full MLFB including suffix and the serial number.
5. Verify the firmware version on the control unit: r0018 (firmware version) and r9925 (firmware build).

7. Step-by-Step Resolution Procedure

Use the following sequence to clear F01360. Each step is verified before proceeding.

7.1 Confirm Topology in STARTER / SINAMICS Startdrive

1. Connect a PG / PC to the CU320-2 DP service interface (X127) or to PROFIBUS / PROFINET.
2. Open STARTER (legacy, recommended for V4.x) or SINAMICS Startdrive in TIA Portal.
3. Go online with the drive unit. Accept any topology mismatch prompts.
4. Open Drive Unit > Topology. The right-hand pane shows the actual topology detected by the control unit, the left-hand pane shows the target topology from the project / CF card.
5. Note the MLFB of the Line Module on the actual side. If the suffix on the actual Line Module is -0AA0 and the firmware on the CU is V4.5 / V4.7, the topology will be highlighted red on the actual side and F01360 is the expected reaction.

7.2 Check the Allow-List and Replace the Line Module

1. Compare the actual Line Module MLFB suffix against the compatibility matrix in section 4.
2. If the actual suffix is -0AA0 on a CU320-2 DP 1MA at firmware V4.5 / V4.7, the supported suffix is -0AA3.
3. Replace 6SL3310-1TE35-0AA0 with 6SL3310-1TE35-0AA3. Confirm the full MLFB on the nameplate before mounting.
4. Reconnect the DRIVE-CLiQ cables exactly as before, paying attention to the port order: CU320-2 DP port X200 typically goes to the Line Module.

7.3 First Power-Up with New Line Module

1. Power up the control unit. The actual topology in STARTER should now show 6SL3310-1TE35-0AA3 at the Line Module slot.
2. Read r949 – the F01360 should be replaced by a message indicating a new component has been detected, typically A01360 "Topology comparison: component inserted" or a similar alert.
3. Acknowledge the fault, then perform a full topology commissioning (see section 8).

7.4 Fallback: Revert to a Compatible CU320-2 DP

If replacing the Line Module is not possible, the alternative path is to swap the control unit so the combination falls inside the allow-list. The matrix in section 4 shows that the 0MA variant of the CU320-2 DP accepts the -0AA3 Line Module. If the Line Module must remain at -0AA0, identify a CU320-2 DP firmware / variant that has it on its allow-list, or downgrade the control-unit firmware to a revision that includes -0AA0.

8. Commissioning After Module Replacement

1. With the new Line Module in place, perform Commissioning > Automatic configuration from STARTER / Startdrive. This step reads the actual topology and writes it as the new target topology.
2. Verify the new target topology matches the actual topology: p9906 = 0 (target = actual) after the automatic configuration runs.
3. If the project on the CF card contains a manual topology that no longer matches, reissue a factory reset of the control unit: p0976 = 1 followed by power cycle. This clears all parameters, the topology, and the fault buffer. Reload the project from PG/PC afterwards.
4. Run the drive system identification: p1910 = 1 (motor identification) and p1960 = 1 (speed-controller optimization) on the active motor module.
5. Save the project to the CF card: p0977 = 1 (save all parameters to non-volatile memory).

9. Verification Checklist

Use the following table to confirm F01360 is fully resolved and the drive is ready to run:

10. Related Faults to Distinguish from F01360

11. Key Parameters and Their Roles

12. Field-Proven Notes and Caveats

• Clean card does not mean correct card. A factory-empty CF card will not bring an incompatible Line Module into the firmware allow-list. The hardware check is performed by the control unit firmware regardless of the project on the card.
• License and F01360 are unrelated. If your drive requires a license, missing licenses produce F13000-class faults, not F01360. Do not purchase a license to clear F01360.
• COMM BOARD firmware version. The optional 6SL3054-0ED00-1BA0 at firmware 4.5 / 4.7 is independent of the Line Module suffix. The compatibility problem lies only between the control unit and the Line Module.
• Why disconnecting the Line Module clears the fault. With the Line Module removed, the topology comparison has nothing to compare against for that node, so F01360 is not raised. This is a useful diagnostic trick: remove one DRIVE-CLiQ device at a time to isolate the offender.
• Spare-part procurement. When ordering a replacement Line Module, always quote the full 18-character MLFB including the suffix (6SL3310-1TE35-0AA3), not a shortened form, to avoid receiving a different hardware revision.

13. Quick Diagnostic Flowchart

[Power up CU320-2 DP]
         |
         v
[F01360 present?]--No-->[Drive is fine, exit]
         |
        Yes
         v
[Read r949 - component / port index]
         |
         v
[Read r9781 at the index in r949]
         |
         v
[Component is a Line Module?]--No-->[Go to specific node repair]
         |
        Yes
         v
[MLFB suffix = -0AA0 and CU firmware = V4.5/V4.7?]
         |                       |
        Yes                      No
         |                       |
         v                       v
[Replace with -0AA3]    [Check other causes:
         |                cable, SMC30, COMM BOARD]
         v
[Power up, read r949]
         |
         v
[Run automatic topology config]
         |
         v
[Save and verify - F01360 gone]

14. FAQ