F30020 — Power unit: Configuration not supported

F30020 is raised when the drive is asked to run the power unit in a configuration that this power unit does not support. The exact reason is coded in r0949, so reading the fault value is the starting point of every diagnosis. The two manual entries differ in one point: for the Motor Module the list of causes also contains fault cause 6.

The low word xxxx of the fault value selects one of these causes:

• xxxx = 0: autonomous operation was requested although the power unit does not support it.
• xxxx = 1: the DRIVE-CLiQ timing that was requested is not permissible.
• xxxx = 2: a PM260 power unit with PS-ASIC version 2 was detected; this pairing is not supported.
• xxxx = 3: initialization did not run through completely — possibly the Control Unit was pulled out of the Power Module before or while it was powering up.
• xxxx = 4: this power unit together with this Control Unit or Control Unit Adapter is not a supported combination.
• xxxx = 5: the higher dynamics of the current controller cannot be used in this configuration.
• xxxx = 6: the Motor Module, its Control Unit and the firmware version in use may not be combined in this way; the manual lists this cause for the Motor Module only.

1. xxxx = 0: if required, deactivate the internal voltage protection that is active (p1231).
2. xxxx = 1: bring the Control Unit firmware up to date, or adapt the DRIVE-CLiQ topology.
3. xxxx = 2: swap the power unit for a PM260 with PS-ASIC version 3 or higher.
4. xxxx = 3 or 4: mount a matching Control Unit or Control Unit Adapter (CUAxx) on the Power Module and then perform a POWER ON of that unit.
5. xxxx = 5: use a power unit in booksize format, or — on a Double Motor Module — set an identical current controller sampling time for both drive controls (p0115[0]); the higher dynamics then remain usable only on the drive with the longer sampling time. Alternatively, deselect the higher current controller dynamics (p1810.11 = 0), recalculate the controller gains (p0340 = 4) and, if required, optimize the speed controller afterwards.
6. xxxx = 6: use a Motor Module that suits the setup, or a Control Unit with an approved firmware version.

• The drive stores the value in r0949, which is to be interpreted hexadecimal.
• Format yyyyxxxx hex: the four low digits xxxx hold the fault cause, the four high digits yyyy hold additional information for internal Siemens use.
• The message text mirrors these two parts as placeholders, fault cause and additional information.
• The causes xxxx = 0 to xxxx = 6 are decoded in the causes section above.

• r0949 — read the stored fault value here and separate fault cause from additional information by interpreting it hexadecimal.
• p1231 — for fault cause 0, use it to deactivate the internal voltage protection if it is active.
• p0115 — for fault cause 5 on a Double Motor Module, set an identical current controller sampling time in p0115[0] for both drive controls.
• p1810 — for fault cause 5, setting bit 11 to 0 (p1810.11 = 0) deselects the higher current controller dynamics.
• p0340 — after deselecting, start the automatic parameter calculation with value 4 so the controller gains are recalculated.

First remove the unsupported configuration — the list above names the fix for each fault cause. The drive coasts down when this fault trips; once the cause has been removed, acknowledge the fault and restart the drive. Where the remedy involves the Control Unit or Control Unit Adapter, insert the unit and perform a POWER ON before the restart.