230-0026

Access Bus Diagnostics

Use the TNCdiag tool or bus diagnostics feature on the control panel to identify the specific HSCI participant reporting a temperature issue. Look for bit REQ.SS2 in the local S status to pinpoint the device.

Save a screenshot or log of the diagnostics data for future reference or escalation.

Ensure the machine is powered down before accessing internal components if required.

Inspect Device Environment

Physically check the identified device for signs of overheating, such as hot surfaces or unusual odors. Verify that the ambient temperature around the machine is within the manufacturer’s specified range (typically 5-40°C).

Use an infrared thermometer for a quick, non-contact temperature check of the device.

Avoid direct contact with hot surfaces to prevent burns.

Check Cooling System

Inspect the cooling vents and heat sinks of the affected device for dust or blockages. Clean with compressed air if necessary, ensuring proper airflow. If the device has an active cooling system, confirm it is operational.

Schedule regular cleaning of cooling components to prevent recurring issues.

Disconnect power before cleaning to avoid electrical hazards.

Identify Affected Device

Use bus diagnostics or TNCdiag to locate the HSCI participant triggering the SS2/STOP2 reaction. Note any additional error messages related to fan failure or cooling issues.

Cross-reference error logs with device IDs to speed up identification.

Follow lockout-tagout procedures before proceeding with physical inspection.

Inspect Fan Operation

Physically check the fan of the identified device. Listen for operational sounds or visually confirm if the fan blades are spinning. If the fan is not running, it may be defective or disconnected.

A small mirror can help inspect hard-to-reach fans without disassembly.

Do not attempt to manually spin fan blades while power is on.

Replace or Repair Fan

If the fan is confirmed defective, replace it with a compatible unit as per the Heidenhain service manual. Test the new fan by powering on the device and verifying operation through diagnostics or physical inspection.

Keep spare fans for critical devices on hand to minimize downtime.

Ensure proper grounding when handling electronic components to avoid static damage.

Review Error Logs

Access the control system’s error log via the user interface or TNCdiag tool. Look for specific messages indicating a self-test failure or incomplete diagnostic routine.

Export logs to a USB drive for detailed analysis if the interface allows.

Do not clear logs without documenting them, as they are critical for troubleshooting.

Restart Control System

Perform a controlled shutdown and restart of the CNC control system to attempt re-running the self-test. Monitor the system during startup for any recurring error messages.

Ensure all peripherals are properly connected before restarting to avoid false errors.

Follow proper shutdown procedures to prevent data loss or system corruption.

Update or Reset Firmware

If the self-test continues to fail, check for firmware updates from Heidenhain that address known self-test issues. Alternatively, perform a system reset as per the service manual if updates are not available.

Backup system parameters before resetting to avoid losing custom configurations.

Firmware updates should only be performed by trained personnel to avoid bricking the system.

Run Bus Diagnostics

Use the TNCdiag or bus diagnostics tool to check for communication errors between HSCI participants. Look for dropped packets, timeouts, or other anomalies in the data stream.

Run diagnostics during idle and operational states to compare results.

Ensure no external interference (e.g., EMI) is affecting diagnostics.

Inspect Cabling and Connections

Physically inspect HSCI cabling and connectors for damage, loose connections, or corrosion. Secure or replace any faulty components as needed.

Use a multimeter to test cable continuity if damage is not visually apparent.

Power down the system before handling cables to avoid electrical shock.

Reset HSCI Network

Perform a reset of the HSCI communication network through the control interface if supported. Monitor the system post-reset to confirm stable communication.

Document network settings before resetting to ensure proper reconfiguration.

Incorrect network settings can cause further communication issues; refer to the manual.

Identify Faulty Participant

Use bus diagnostics to isolate the HSCI participant reporting errors or failing to respond. Note any specific error codes associated with hardware failure.

Compare current diagnostics with historical data to identify recurring issues.

Document findings before proceeding to avoid misdiagnosis.

Test Device Functionality

Perform a manual test of the identified device if possible (e.g., standalone power-up or signal test). Check for abnormal behavior or failure to initialize.

Use manufacturer-provided test protocols for accurate results.

Follow safety protocols during testing to avoid injury or further damage.

Replace Faulty Hardware

If the device is confirmed faulty, replace it with a compatible unit as per the Heidenhain service manual. Test the system after replacement to ensure the alarm is resolved.

Keep a log of replaced components for warranty or inventory purposes.

Ensure proper installation to prevent damage to the new hardware.