Power unit: Configuration not supported
Siemens · DAsl Diagnostics and Alarms
What does 230020 mean?
The system is attempting to use a configuration that the power unit does not support. This can be caused by requesting autonomous operation on an unsupported unit, incompatible DRIVE-CLiQ timing, an older PM260 PS-ASIC version, failed initialization due to premature Control Unit withdrawal, or an unsupported combination of power unit and Control Unit/Adapter. The fault value in r0949 provides specific details on the cause.
Common Causes
- Attempting to operate a power unit in 'autonomous' mode (e.g., P0003=1) that does not support this functionality.
- Incompatible DRIVE-CLiQ telegram configuration (P0922, P0923) between the control unit and the power module.
- Incorrect DRIVE-CLiQ component order (P0927) for the connected power unit, leading to data transfer issues.
- Hardware incompatibility between the specific power module type and the connected control unit (e.g., mismatched series).
- Project configuration in engineering software (e.g., STARTER, TIA Portal) does not match the actual hardware.
Repair Steps & Checklist
Click steps to track your progress.
- 1
Verify the exact model number (MLFB) of the power unit and its technical specifications for supported operating modes.
- 2
Check parameter P0003 (User access level) and P0010 (Control unit configuration) to ensure no unsupported autonomous mode is selected.
- 3
Compare DRIVE-CLiQ configuration parameters (P0922, P0923, P0927) in the drive with the project configuration in STARTER/TIA Portal.
- 4
Perform a DRIVE-CLiQ topology scan (automatic configuration) to re-establish communication and identify modules.
- 5
Ensure the firmware version of the control unit is compatible with the power unit's firmware version, updating if necessary.