What causes Siemens SINUMERIK alarm 400157?

SINAMICS drive hardware fault requiring investigation. Drive parameter configuration error. Axis motor or feedback system fault triggering drive protection. Communication fault on the drive bus. Power supply issue affecting the drive module.

How do I fix Siemens SINUMERIK alarm 400157?

1. Check the SINAMICS drive for active fault codes in the diagnostics screen. 2. Power cycle the machine to clear transient faults. 3. Review SINAMICS parameters for the affected drive axis. 4. Check the SINUMERIK axis diagnostics for related NC alarms. 5. Consult the Siemens SINAMICS alarm manual for alarm 400157 complete remedy.

Siemens SINUMERIK codes

axismd.ai

Siemens SINUMERIK Controller

Program/G-code · Intermediate · 30-120 minutes

Alarm 400157

Siemens 840D 400157 - Delete DB 57 in the PLC and restart

This alarm occurs when the size of DB 57 in the PLC differs from the one created by the basic program. To fix, delete DB 57 in the PLC and restart the system.

Siemens SINUMERIKProgram/G-codeIntermediate30-120 minutes

400157

Siemens 840D 400157 - Delete DB 57 in the PLC and restart

Delete DB 57 in the PLC and restart

Siemens SINAMICS drive alarm 400157: Delete DB 57 in the PLC and restart. This alarm indicates a fault condition in the SINAMICS servo drive system. Refer to the Siemens SINAMICS fault list documentation for the complete remedy.

Root Cause Summary

This alarm occurs when the size of DB 57 in the PLC differs from the one created by the basic program. To fix, delete DB 57 in the PLC and restart the system.

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Causes and Fixes

1
SAFETY FIRST - Stop machine operations
STOP all machine operations and ensure the machine is in a safe state before accessing PLC data blocks.
2
Access PLC data
Navigate to the PLC data blocks in the Siemens control system interface using appropriate access credentials.
3
Backup current configuration
Create a backup of the current PLC program and configuration before making any changes.
4
Delete DB 57
Locate and delete DB 57 to allow the system to recreate it with the correct size.
5
Restart system safely
Perform a controlled system restart following proper shutdown procedures to regenerate DB 57 and clear the alarm.

Service Recommendedmedium confidence

Call a technician if:

·If you are not trained in PLC programming and data block management
·If the alarm persists after deleting DB 57 and restarting
·If DB 57 cannot be deleted due to access restrictions
·If you are unsure about the function of DB 57 in your specific application

Prevention

Ensure proper shutdown procedures to avoid data corruption
Document program changes affecting PLC data blocks

Common Mistakes

Attempting PLC modifications without proper training
Not stopping machine operations before PLC changes
Failing to backup configuration before deleting data blocks
Restarting without deleting DB 57
Ignoring system logs for root cause clues

Seeing Multiple Alarms?

Seeing another alarm with this one? Enter the code.

Get machine-aware diagnosis

AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.

Start free

Was this guide helpful?

Always verify with your machine manual or a certified technician before performing service procedures.