230-0499

Access machine parameter editor

Press MOD key, select 'Machine parameters' from setup menu, navigate to CfgLaAxis section for the affected axis number shown in %2.

Use Ctrl+F to quickly search for 'MP_axManualJerk' in the parameter list

Verify parameter existence

Check if MP_axManualJerk exists in the axis configuration. If missing, add the parameter with appropriate jerk value (typically 10-50% of MP_axJerk).

Backup machine parameters before making changes

Configure jerk value

Set MP_axManualJerk to a value between 1000-10000 mm/min³ depending on axis characteristics and mechanical limits.

Start with 30% of the main MP_axJerk value and adjust based on machine performance

Restart control

Perform a control restart (Ctrl+Alt+Del) to activate the new parameter settings and clear the alarm condition.

Check configuration file integrity

Navigate to TNC:\system\cfg and examine the CfgLaAxis.cfg file for syntax errors or missing sections using the built-in text editor.

Do not edit system files without proper backup

Compare with backup configuration

Access Setup > Data backup/restore and compare current axis configuration with a known good backup to identify missing parameters.

Check the file timestamp to determine when corruption may have occurred

Restore from backup

If backup is available, restore the CfgLaAxis configuration file from a known good state using the TNC backup/restore function.

Ensure machine is in safe position before restoring configuration

Rebuild axis configuration

If no backup exists, manually recreate the axis configuration including all required parameters like MP_axManualJerk using machine documentation.

Identify triggering PLC sequence

Use PLC diagnostics (Setup > PLC > Program status) to identify which PLC program line is executing when alarm occurs.

Enable PLC trace mode to capture the exact sequence causing the alarm

Review axis movement commands

Examine PLC program for axis movement functions like M_AXIS_MOVE or interpolation commands that require manual jerk parameters.

Ensure PLC program is stopped before editing

Verify axis parameter requirements

Check PLC programming manual for specific parameter requirements for the movement commands being used, ensuring MP_axManualJerk is properly configured.

Cross-reference with machine manufacturer's PLC documentation for axis-specific requirements

Test PLC movement sequence

After parameter correction, test the PLC movement sequence in single-step mode to verify proper operation without alarm recurrence.

Check software version

Press Help key and select 'About' to verify current TNC software version and compare with previous working version.

Document software version before any updates for rollback reference

Review release notes

Access TNC software documentation to check if recent updates changed parameter requirements for PLC axis movements.

Always review release notes before software updates

Update parameter configuration

Add or modify MP_axManualJerk parameters according to new software requirements, following updated parameter documentation.

Contact Heidenhain support for parameter migration guidelines between software versions

Validate all axes

Check and update MP_axManualJerk parameters for all axes that perform PLC movements, not just the one triggering the alarm.