4029

Navigate to NCK → Parameters → MD and locate the axis container definition. Verify the container assignment via MD10100 AXCONF_MACHAX_NAME_TAB (Axis Configuration Machine Axis Name Table).

Cross-check critical MD parameters for all axes in the container: MD32100 (travel distance), MD32200 (feedrate numerator), MD32210 (feedrate denominator), and MD36100 (rapid acceleration time). Document any mismatches.

Differing values indicate axes are not equivalent for container membership.

Align the divergent MD values across all axes in the container. Perform this modification offline before power-cycle to prevent runtime conflicts.

Perform a full power-down (cold restart) of the 840D control. On reboot, the NCK will re-validate container MD consistency. The alarm will clear automatically once synchronization is confirmed.

Warm restart (Ctrl+Alt+Del) may not trigger full MD synchronization; a power-cycle is required.

Check the axis-to-channel assignment via NCK → Parameters → MD10101 AXCONF_CHAN_AXIS_ASSIGN for all active channels. Verify that no recent axis reassignment has occurred without MD validation.

For each axis involved in a swap or reassignment, verify that load-dependent parameters (MD36050 AXMEAS_LOAD_MASS, MD36051 AXMEAS_LOAD_INERTIA) and friction compensation (MD36400 AXMEAS_FRICTION_CONST) are identical between the old and new container positions.

Load mismatch can cause servo instability and axis protection errors post-synchronization.

If parameters cannot be matched, remove the axis from the shared container assignment and create a dedicated container via MD10100 modification, or reassign the axis to a single-axis container.

Execute a complete NCK restart (POWER OFF → POWER ON sequence). Monitor the system message log (Diagnostics → Messages) to confirm alarm 4029 clears and no follow-up servo or axis allocation errors appear.

Verify the source and timestamp of the current MD backup. Compare MD10100 and MD10101 values in the running system against the original documented configuration to confirm no partial restore has occurred.

If a restore is suspected, use the Commissioning tool (or HMI Diagnostics → System Information → Machine Data Export) to export current MD values and manually validate axis container consistency before power-cycle.

Do not perform blind power-cycle if backup integrity is uncertain; data corruption risk exists.

If backup inconsistency is confirmed, reload a verified baseline machine data set or re-commission axis parameters from the original hardware documentation and machine nameplate specs.

Perform a controlled power-up with HMI monitoring enabled. Allow the NCK to complete the MD synchronization cycle (typically 30–60 seconds). Confirm alarm 4029 transitions to INFO/CLEARED status in the message log.