140-0036

Review the specific change details

Press RECALL key to display full alarm text showing the data object name ('%1'), the changed value ('%2'), and the affected attribute ('%3'). Note these details for verification.

The attribute name often indicates the category (e.g., 'CfgAxisLinear', 'CfgSpindle', 'CfgEnc') which helps identify the affected system area.

Access Configuration Editor

Navigate to MOD → 13 (System Parameters) → Configuration Editor. Search for the data object name shown in the alarm message to view current settings.

Changes in Configuration Editor require appropriate password level (typically OEM or higher). Incorrect modifications can affect machine behavior.

Verify change was intentional

Compare the new value against machine documentation or consult with the person who performed maintenance. Check timestamp of change in system log.

Access system log via MOD → TNC System Info → Event Log to see exact time and user context of parameter change.

Clear informational message

If change is verified as correct, acknowledge the message by pressing CE (Clear Error) key. The message serves only as notification, not as operational alarm.

Document accepted changes in machine commissioning records for future reference and traceability.

Identify the changed data object

Note the complete alarm text with object name and attribute. Cross-reference with PLC documentation to determine if this object is accessed by PLC logic.

Common PLC-modified objects include spindle mode settings, axis enable states, and adaptive parameter sets for different machining conditions.

Review PLC program logic

Access PLC programming environment through MOD → PLC Program to check for WRITE DATA OBJECT commands or system calls that modify configuration parameters.

PLC program access requires OEM password level. Do not modify PLC code without complete understanding of machine logic.

Check PLC operating mode

Verify if PLC is in automatic mode and executing sequences that might trigger parameter changes. Review M-function implementations that interface with configuration system.

Use PLC Test Functions (MOD → PLC → Test) to monitor data object access in real-time during program execution.

Validate automated change

If PLC change is part of normal machine operation (e.g., automatic tool changer configuration, adaptive control), acknowledge message and ensure behavior meets operational requirements.

Consider implementing PLC logging for critical parameter changes to maintain audit trail of automated adjustments.

Verify recent software changes

Check MOD → TNC System Info → Version to confirm current software version and compare against previous version. Review if update was recently performed.

Software version changes often require parameter migrations. Multiple 140-0036 messages after update are typically normal.

Review update documentation

Consult the Heidenhain software update documentation (Release Notes) to identify expected parameter changes or data object migrations for the installed version.

After major version updates (e.g., 340.5xx to 340.6xx), always perform complete machine verification before production use.

Compare parameter sets

Export current machine parameters via MOD → 7 (Backup/Restore) and compare against pre-update backup to identify all changes. Use configuration comparison tools if available.

Create a dedicated comparison folder on CF card: TNC:\system\compare\ to store before/after parameter exports.

Perform functional verification

Execute machine reference run, test all axes in manual mode, verify spindle operation, and run test programs to ensure all changed parameters maintain correct machine behavior.

Use Heidenhain's machine test cycles (if provided by OEM) or systematic axis movement tests to validate configuration integrity post-update.

Document and clear messages

Document all parameter changes in machine service log, create new baseline backup of verified configuration, then clear informational messages with CE key.

Label backup with software version and date: 'TNC530_v340xxx_YYYY-MM-DD_PostUpdate.zip' for clear version control.