126-007F

Check module LED indicators

Observe the LED status on both the CC and MC modules. Normal operation shows steady green LEDs. Flashing red or orange LEDs indicate a module fault. Document the LED pattern for diagnostics.

Do not remove or reseat modules while power is applied to prevent module damage

Perform complete power reset

Disconnect AC power and 24VDC supply to the control. Wait minimum 60 seconds to ensure all capacitors discharge completely. Restore power and observe startup sequence. Monitor for any additional error codes during boot.

Extended power-down (2-3 minutes) can sometimes clear transient hardware faults in the control modules

Review system error log

Access MOD function, select option 9 (Service functions), then option 3 (Error log). Review all logged errors chronologically. Look for preceding errors related to CC, MC, or bus communication that occurred before alarm 126-007F.

Error sequences often reveal the root cause - look for patterns like repeated communication errors before the self-test failure

Verify module seating and connections

With power disconnected, carefully check that the CC and MC modules are properly seated in their backplane connectors. Check for corrosion, bent pins, or visible damage to module connectors. Reseat modules if necessary.

Use proper ESD protection when handling control modules. Ground yourself before touching modules.

Prepare for module replacement

If alarm persists after all checks, the CC or MC module requires replacement. Document control serial number, software version (visible in startup screen or MOD 9 6), and complete error log. Contact Heidenhain service for replacement module with matching firmware.

Heidenhain modules are serial-numbered and paired to the control license - replacement requires proper authorization and configuration transfer

Check backplane connections

With power off, inspect the backplane bus connectors for physical damage, corrosion, or contamination. The CC2 bus is critical for inter-module communication on TNC controls. Check for any visible damage to the backplane PCB traces.

Backplane inspection requires control cabinet access - follow proper LOTO procedures

Verify grounding and shielding

Check that the control cabinet has proper PE (protective earth) connection and that shield grounding is intact. Poor grounding can cause bus communication errors. Measure resistance between control chassis and PE ground - should be less than 0.1 ohm.

EMI interference from nearby VFDs or welders can disrupt the CC2 bus - verify cabinet shielding integrity

Inspect power supply voltages

Using a multimeter, verify stable 5VDC and 3.3VDC on the backplane. Voltage fluctuation or ripple can cause communication errors. Check at multiple points along the backplane with control powered and running (if it boots at all).

Use extreme caution when measuring voltages on live circuits - ensure proper meter settings and probe placement

Attempt Service Mode boot

Try booting the control into Service Mode by holding the appropriate key combination during startup (varies by control model - typically MOD + CE during power-on). Service Mode bypasses some communication checks and may allow module diagnostics.

If Service Mode boots successfully but normal mode fails, this confirms a communication initialization issue rather than total hardware failure

Check software version consistency

Access MOD function, select option 9 (Service), then option 6 (Version information). Compare firmware versions of all modules - CC, MC, and NC core must match exactly. Note any version discrepancies.

On iTNC 530 and TNC 640, firmware version must match across all modules to within the same build number

Review update history

Check if a software update was recently attempted or interrupted. Review maintenance logs for any documentation of incomplete updates or power failures during update procedures.

Never interrupt power during a Heidenhain firmware update - this can brick the control requiring factory repair