What causes Okuma OSP alarm 1195?

Faulty MCS unit. Faulty MCS software. Corrupted or lost communication frames between the tandem stations.

How do I fix Okuma OSP alarm 1195?

1. Read the code number shown with the alarm: code XXXX=1 = Communication data was not counted (frame lost); YYYY is always 0; code XXXX=2 = Format code of the communication data did not match; YYYY is the low-order byte of that code 2. Record the full XXXXYYYY code shown on screen before resetting. 3. If XXXX=1, the communication data was not counted (a frame was lost); YYYY will read 0. This suggests an intermittent link or unit fault. 4. If XXXX=2, the format code of the received data did not match; YYYY shows the low-order byte of that code, indicating corrupted data on the link. 5. Power down, lock out, and reseat the communication connections between the MCS units handling the master and slave axes. 6. If the alarm returns, the probable causes are the MCS unit or MCS software; record the alarm number, code, and axis and contact Okuma service.

Okuma OSP codes

axismd.ai

Okuma OSP Controller

Communication · Intermediate

Alarm 1195

Okuma OSP Alarm A 1195 - MCS Tandem control communication error

During tandem (synchronous master/slave axis) control, the slave axis received corrupted communication data over the inter-station link. The synchronous axes cannot stay coordinated, so the control stops with this alarm.

Okuma OSPCommunicationIntermediate

1195

Okuma OSP Alarm A 1195 - MCS Tandem control communication error

MCS Tandem control communication error

Common Causes

Faulty MCS unit
Faulty MCS software
Corrupted or lost communication frames between the tandem stations

Troubleshooting Steps

1Read the code number shown with the alarm: code XXXX=1 = Communication data was not counted (frame lost); YYYY is always 0; code XXXX=2 = Format code of the communication data did not match; YYYY is the low-order byte of that code
2Record the full XXXXYYYY code shown on screen before resetting.
3If XXXX=1, the communication data was not counted (a frame was lost); YYYY will read 0. This suggests an intermittent link or unit fault.
4If XXXX=2, the format code of the received data did not match; YYYY shows the low-order byte of that code, indicating corrupted data on the link.
5Power down, lock out, and reseat the communication connections between the MCS units handling the master and slave axes.
6If the alarm returns, the probable causes are the MCS unit or MCS software; record the alarm number, code, and axis and contact Okuma service.

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.