What causes Okuma OSP alarm 1172?

Faulty pulse generator (PG) delivering wrong counts. PG gear tooth count on the machine does not agree with what the servo data file expects. Wrong servo data file loaded for this axis. PG coupling or gearing changed without updating the servo data file.

How do I fix Okuma OSP alarm 1172?

1. Read the code number shown with the alarm: code XXXX = PBU set value: expected count number for one PG turn.; code YYYY = Actual count number measured for one PG turn. 2. Read the code: XXXX is the PBU set value (expected count for one PG turn) and YYYY is the actual count measured, so compare them to see how far the PG is off. 3. Count the teeth on the PG gear fitted to the axis and compare against the tooth count the servo data file assumes; a changed gear or wrong file produces exactly this kind of count mismatch. 4. Verify the correct servo data file is loaded for the named axis, especially if axes or data files were recently swapped. 5. Inspect the PG mounting and coupling for looseness that could drop or add counts per turn. 6. If the gearing and data file agree, replace the faulty pulse generator, then re-home the axis and verify one-turn counts match the PBU set value.

Okuma OSP codes

axismd.ai

Okuma OSP Controller

Servo/Axis · Intermediate

Alarm 1172

Okuma OSP Alarm A 1172 - MCS Pulse generator count over

The pulse generator (PG) count value per one revolution differs from the data specified in the servo data file for the axis or spindle named in the object. The feedback device is not delivering the expected number of counts per turn, so position and speed data are wrong.

Okuma OSPServo/AxisIntermediate

1172

Okuma OSP Alarm A 1172 - MCS Pulse generator count over

MCS Pulse generator count over

Common Causes

Faulty pulse generator (PG) delivering wrong counts
PG gear tooth count on the machine does not agree with what the servo data file expects
Wrong servo data file loaded for this axis
PG coupling or gearing changed without updating the servo data file

Troubleshooting Steps

1Read the code number shown with the alarm: code XXXX = PBU set value: expected count number for one PG turn.; code YYYY = Actual count number measured for one PG turn.
2Read the code: XXXX is the PBU set value (expected count for one PG turn) and YYYY is the actual count measured, so compare them to see how far the PG is off.
3Count the teeth on the PG gear fitted to the axis and compare against the tooth count the servo data file assumes; a changed gear or wrong file produces exactly this kind of count mismatch.
4Verify the correct servo data file is loaded for the named axis, especially if axes or data files were recently swapped.
5Inspect the PG mounting and coupling for looseness that could drop or add counts per turn.
6If the gearing and data file agree, replace the faulty pulse generator, then re-home the axis and verify one-turn counts match the PBU set value.

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.