23A-001E

Identify the Device and Cable Path

Note the device name from the %2 parameter in the alarm display. Trace the communication cable from the TNC rear panel (typically X116 for system bus, X126 for additional devices) to the specific device. Consult the machine's electrical drawings to identify the exact cable routing.

The %2 parameter often shows abbreviated device names like 'INV1', 'PLC', 'ENC3' — cross-reference these with the System Configuration to find the physical location.

Inspect Cable and Connectors

Power down the machine. Disconnect both ends of the communication cable and inspect for bent pins, corrosion, or physical damage. Check for proper cable shielding continuity. Look for stress points where cables bend sharply or pass through cable carriers.

Always perform controlled shutdown via MOD > System Shutdown before disconnecting communication cables to prevent data corruption.

Reseat or Replace Cable

Clean connectors with contact cleaner if necessary. Firmly reseat connectors ensuring proper locking mechanism engagement. If damage is visible or cable has been in service for many years, replace with genuine Heidenhain cable (specify part number from electrical documentation).

Heidenhain communication cables have specific impedance and shielding requirements — never substitute with generic cables, as this causes intermittent communication errors.

Test and Verify Communication

Power up the control and observe if the alarm clears during initialization. Access MOD > System Configuration > Device Status to verify the device shows 'Active' or 'OK' status. Monitor for 5-10 minutes to ensure stability.

If the alarm is intermittent, use the Event Log timestamp feature to correlate communication loss with machine movements that may flex cables.

Access System Configuration

Press MOD key, enter password if required, select 'System Configuration' or 'Machine Parameters'. Navigate to the communication/device section where peripheral devices are listed. Locate the device corresponding to %2 in the alarm message.

On iTNC 530 and TNC 620/640, this is typically under MOD > System Parameters > CfgDeviceManager or similar menu path depending on software version.

Verify Device Address and Type

Check that the device address matches the hardware DIP switch settings or rotary switch on the physical device. Verify the device type selection matches the actual hardware model. Look for any red error indicators or 'Not Found' status messages.

Changing device addresses or configuration may require a backup of machine parameters before proceeding — use MOD > Data Backup function.

Compare with Known-Good Configuration

If available, compare current configuration with the commissioning documentation or a previously saved parameter backup. Check for recent parameter changes that may have inadvertently altered device settings. Restore from backup if a working configuration is available.

Many machine builders provide a USB stick with factory parameters — keep this accessible for comparison during troubleshooting.

Re-initialize Device Communication

After correcting any configuration errors, perform a device re-scan or initialization. This may be labeled 'Scan Devices', 'Re-detect Peripherals', or require a full control reboot. Monitor the boot sequence messages for successful device recognition.

On TNC 640 controls, the boot screen shows device enumeration — watch for the specific device to appear with 'OK' status during startup.

Check Device Power Supply

Verify that the device has proper power indicated by status LEDs. For 24V DC powered devices, measure voltage at the device terminals (should be 24V ±10%). Check for blown fuses or tripped circuit breakers in the device power circuit. Inspect power supply connections for tightness.

Use appropriate voltage measurement safety procedures and ensure measurements are taken at accessible test points, not on live bus bars.

Observe Device Status Indicators

Most Heidenhain peripheral devices have multi-color status LEDs. Consult the device-specific manual for LED code interpretation. Common patterns: solid green = OK, flashing red = error, no LED = no power or device failure. Document the LED pattern observed.

Inverters and PLCs often have specific diagnostic LED sequences that indicate communication vs. internal faults — the manual decode is essential for accurate diagnosis.