What causes Okuma OSP alarm 1153?

Faulty MCS controller. Mismatch between MCS data and NC data. Corrupted servo data after a software or file change. Fatal internal error in the MCS disabling DIFF monitoring.

How do I fix Okuma OSP alarm 1153?

1. Read the code number shown with the alarm: code value = Absolute value of CON-APA deviation in hexadecimal (reference unit). 2. Read the code: it is the absolute value of the CON-APA deviation in hexadecimal (reference units), so record how large the position mismatch is. 3. Cycle power and note whether the same deviation returns on the same axis; a repeatable deviation points to a data mismatch rather than a transient. 4. Verify the servo data file and NC data for the named axis are consistent and from the same machine configuration; reload the correct MCS/servo data if they were recently changed. 5. If data is consistent, the MCS controller itself is faulty and must be exchanged; then re-initialize, re-home the axis and verify CON and APA track within the limit.

Okuma OSP codes

axismd.ai

Okuma OSP Controller

Servo/Axis · Intermediate

Alarm 1153

Okuma OSP Alarm A 1153 - MCS CON APA deviation

The deviation between the calculated position (CON) and the actual position (APA) read back from the MCS exceeded the allowable limit. This alarm appears when the MCS itself has a fatal error and cannot monitor the normal DIFF value, so the NC software watches the CON-APA deviation instead.

Okuma OSPServo/AxisIntermediate

1153

Okuma OSP Alarm A 1153 - MCS CON APA deviation

MCS CON APA deviation

Common Causes

Faulty MCS controller
Mismatch between MCS data and NC data
Corrupted servo data after a software or file change
Fatal internal error in the MCS disabling DIFF monitoring

Troubleshooting Steps

1Read the code number shown with the alarm: code value = Absolute value of CON-APA deviation in hexadecimal (reference unit).
2Read the code: it is the absolute value of the CON-APA deviation in hexadecimal (reference units), so record how large the position mismatch is.
3Cycle power and note whether the same deviation returns on the same axis; a repeatable deviation points to a data mismatch rather than a transient.
4Verify the servo data file and NC data for the named axis are consistent and from the same machine configuration; reload the correct MCS/servo data if they were recently changed.
5If data is consistent, the MCS controller itself is faulty and must be exchanged; then re-initialize, re-home the axis and verify CON and APA track within the limit.

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.