Okuma OSP codes
Okuma OSPServo/AxisIntermediate

1186

Okuma OSP Alarm A 1186 - MCS Collision detected

MCS Collision detected

The NC torque limiter saw the axis hit something by watching the relation between motor output torque and motor acceleration. A sudden torque spike that does not match the commanded motion means a collision.

Common Causes

  • Actual collision of the axis with the workpiece, chuck, fixture, or tailstock
  • Motor encoder feedback error causing false torque/acceleration relation
  • NC torque limiter set value too sensitive for the application

Troubleshooting Steps

  1. 1Read the code number shown with the alarm: code XXXX = Detected torque, sum of torque data collected for 3.2 ms, +-2^-12 MAXTRQ; code YYYY = Detected acceleration, average torque measured for 3.2 ms, about 0.1 1/min/ms
  2. 2Stop and inspect the machine immediately: check the named axis path for a crashed tool, fixture, or workpiece before any reset.
  3. 3Read the code: XXXX is the detected torque (sum of torque data collected for 3.2 ms, in units of 2^-12 MAXTRQ) and YYYY is the detected acceleration (average torque over 3.2 ms, about 0.1 1/min/ms); large values confirm a real impact.
  4. 4After clearing any physical obstruction, check the tool, holder, and workpiece for damage and requalify the setup before running.
  5. 5If no physical collision is found, check the motor encoder feedback on the named axis for noise or looseness that could falsify the torque/acceleration relation.
  6. 6If the alarm recurs without a real collision, review the NC torque limiter set value with Okuma service before adjusting it.

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.