10752

Check current MD32000 value

Access HMI > Commissioning > Machine Data > Channel/Axis Specific > MD32000 MAX_AX_VELO and note the configured maximum velocity for the affected axis.

Compare this value against your machine's actual capability - it should be 10-20% below mechanical limits

Analyze NC program block

In HMI > Diagnostics > Service > NC > Actual Values, check the 'Programmed velocity' display during alarm occurrence to identify the commanded feedrate.

Do not increase MD32000 without verifying mechanical and drive system capabilities

Modify program or machine data

Either reduce the programmed F-word feedrate in the NC program or increase MD32000 if mechanically justified, then reset NCK and test.

Use MD32010 JOG_VELO_RAPID to set appropriate rapid traverse limits

Check encoder diagnostics

Navigate to HMI > Diagnostics > Drive > Encoder and examine signal quality indicators, checking for error counters or amplitude warnings on the affected axis encoder.

Look for intermittent C1, C2 track errors or envelope violations

Verify encoder connections

Inspect encoder cable connections at motor and drive module, checking for loose connections, cable damage, or EMI interference near high-power cables.

Power down system before checking encoder connections

Monitor actual velocity trace

Use HMI > Diagnostics > Service > Trace to record actual velocity signals during motion and identify velocity spikes or erratic feedback patterns.

Set trace trigger on velocity values near MD32000 limit to capture fault conditions

Compare with backup parameters

Access HMI > Startup > Data Backup/Restore and compare current MD32000 values with previous working parameter sets to identify recent changes.

Check the parameter change log in HMI > Diagnostics > Service > Logbook for MD32000 modifications

Verify against machine specifications

Cross-reference MD32000 setting with machine manufacturer specifications and drive system ratings, ensuring the limit allows normal operating velocities.

Never exceed mechanical limits specified in machine documentation

Restore correct parameter value

Set MD32000 to appropriate value based on machine capability, perform NCK reset via HMI > Startup > NCK > Reset, and verify normal operation.

Document the change in machine logbook with justification and date

Check drive parameters

Access HMI > Commissioning > Drive > Optimize and review velocity loop parameters P1442 (Kv factor) and P1470 (velocity loop integral time) for stability.

Look for recent drive optimization changes that may have destabilized the velocity loop

Analyze velocity following error

Monitor drive parameter r1482 (velocity actual value) and r1479 (velocity setpoint) to identify excessive following errors or oscillations during motion.

Velocity loop instability can cause mechanical resonance and damage

Perform drive optimization

Run automatic drive optimization via HMI > Commissioning > Drive > Optimize > Speed Control or manually adjust velocity controller gains to achieve stable response.

Use STARTER software for detailed drive parameter analysis and optimization

Check mechanical movement

Manually verify smooth axis movement in JOG mode at low velocity, listening for unusual noises or feeling for binding or rough motion.

Ensure machine is in safe state before manual movement checks

Monitor drive current

Observe drive parameter r1482 (motor current actual value) during motion to identify excessive current indicating mechanical resistance or binding.

Compare current levels with normal operation baseline values

Inspect mechanical components

Check ballscrews, linear guides, and coupling components for damage, contamination, or improper lubrication that could cause erratic motion.

Use dial indicator to check for mechanical backlash or play in drive components