230-0044

Access Machine Parameters

Press MOD key, enter password, select 'Machine Parameters' from the menu. Navigate to CfgAxisSim parameter group to review simulation settings.

Document all current parameter values before making any changes. Incorrect parameter modifications can affect machine behavior.

Verify Simulation Configuration Syntax

Check CfgAxisSim entries for each axis (X, Y, Z, etc.) for proper syntax: valid numerical ranges, correct axis names matching CfgAxes definitions, and no special characters or formatting errors.

Compare simulation parameters against a backup parameter file or factory defaults to identify discrepancies. Pay special attention to decimal separators and unit specifications.

Reset to Default Simulation Parameters

If corruption is suspected, restore CfgAxisSim parameters to default values from backup or factory settings. Document custom settings first for later reconfiguration.

Resetting parameters will remove custom simulation behavior. Coordinate with machine tool builder if special simulation settings were implemented.

Restart Control and Test

Perform a complete control restart (power cycle or use MOD > System > Restart). After reboot, enter simulation mode (Test Run) and attempt to execute a simple axis movement program to verify alarm clearance.

Compare CfgAxes and CfgAxisSim Parameters

In MOD > Machine Parameters, open CfgAxes and CfgAxisSim side-by-side (use documentation or printout). Verify that axis names, types (linear/rotary), and configuration match exactly between both parameter sets.

Use the TNC's parameter search function (search for axis name like 'X') to quickly locate all references to specific axes across parameter groups.

Verify Axis Type Definitions

Ensure each axis defined in CfgAxisSim has corresponding proper type definition in CfgAxes: linear axes must have matching linear simulation, rotary axes (A, B, C) must have rotary simulation parameters with correct modulo settings.

Rotary axis simulation parameters require special attention to modulo and display settings. Incorrect settings can cause simulation calculation errors.

Check for Recently Added or Modified Axes

If machine configuration was recently changed (additional axis added, axis renamed, or kinematics modified), verify all simulation parameters were updated accordingly. Update CfgAxisSim to reflect current machine configuration.

After machine modifications, always verify simulation parameters match the new configuration. Many technicians forget to update simulation settings after hardware changes.

Test Individual Axis Simulation

Enter Test Run mode and execute simple single-axis movements for each axis individually. Identify which specific axis triggers the alarm to isolate the parameter mismatch.

Perform Cold Boot of Control

Power off the control completely, wait 30 seconds, then power back on. This clears all volatile memory and reinitializes the simulation module. Do NOT use the soft restart function for this step.

Ensure no program is running and all axes are at safe positions before powering down the control.

Check Control Software Version

Press MOD key, select 'System Information' and note the current software version (NC Software). Check if alarm appeared after recent software update. Review Heidenhain service notifications for known simulation module issues in your software version.

Maintain a log of control software versions and alarm occurrences. Patterns often emerge that indicate software-specific issues requiring patches.

Verify Available System Memory

In MOD menu, check system resources and memory usage. If memory utilization is very high (>90%), remove unnecessary files, clear old program logs, or reduce number of loaded programs to free up memory for simulation module.

The simulation module requires adequate free memory. Large complex programs or many background processes can exhaust memory resources, causing simulation errors.

Isolate Software Conflict

Temporarily disable custom PLC program blocks related to simulation or axis control (if present). Test if alarm persists. This identifies whether custom programming interferes with standard simulation functionality.