Heidenhain codes
HeidenhainParameterIntermediate30-120 minutes

140-0046

HEIDENHAIN 140-0046 - Data change without effect

Data change without effect

Data changes have no effect because multiple MP subfiles are loaded or PLC modules have modified parameters. The active configuration overrides the changes.

Root Cause Summary

This alarm specifically indicates that the TNC control has accepted and stored a configuration change, but the change resides only in the saved parameter set and has not been loaded into the active runtime environment. Certain machine parameters, kinematic settings, and system configurations require the NC kernel or PLC to reinitialize before new values become operational.

Safety

  • Refer to Heidenhain service manual
  • Ensure qualified technician performs repairs

Causes and Fixes

  1. 1

    Identify Changed Parameter

    Press MOD function key, navigate to 'Machine Parameters' and look for parameters with different values in 'Active' vs 'Set' columns. Parameters requiring restart show 'R' in the description field.

    Use the search function (FIND key) in machine parameters to quickly locate recently modified parameters by pressing CTRL+F and entering the approximate parameter number.

  2. 2

    Verify Restart Requirement

    Check the parameter documentation (press HELP key while parameter is selected) to confirm whether 'Effective after restart' or 'Effective immediately' is indicated in the parameter description.

    Parameters affecting NC kernel operation (CfgAxisPar, CfgServoCtrl, CfgEnDat) almost always require restart.

  3. 3

    Perform Control Restart

    Exit all active programs and return to manual mode. Press MOD key, then simultaneously press CTRL+T (Control Key + T) to access system menu. Select 'Restart Control' option. Control will reboot and load new parameter values.

    Ensure no part program is running and machine is in safe position before restart. Axis positions may need to be re-referenced after restart depending on parameters changed.

  4. 4

    Verify Parameter Activation

    After restart, return to MOD > Machine Parameters and confirm that 'Active' and 'Set' columns now show identical values for the changed parameter. Alarm 140-0046 should no longer appear.

    Create a parameter backup via MOD > Data Transfer after confirming changes are correct and functional.

DIY Feasiblehigh confidence

Call a technician if:

  • ·PLC program modifications required
  • ·Multiple complex MP subfiles need restructuring
  • ·Parameter conflicts affect safety systems

Prevention

  • Maintain organized MP subfile naming convention
  • Document PLC parameter control logic
  • Use version control for parameter files
  • Establish clear parameter modification procedures

Common Mistakes

  • Editing parameters without checking source
  • Ignoring MP subfile loading sequence
  • Not restarting control after parameter changes
  • Modifying parameters during program execution

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.