239-01C2

Power Down System Safely

Execute emergency stop and power down the complete system following proper shutdown sequence in MOD 'Machine' menu.

Never disconnect FS cables while system is powered - this can damage safety circuits

Inspect FS Communication Cables

Check all cables between TNC control unit and FS module for physical damage, loose connections, or corrosion at X116/X117 connectors.

Look for cable stress points where they enter cable chains or pass through machine structure

Verify Cable Continuity

Use multimeter to test continuity on FS communication lines, checking for opens or shorts in the differential signal pairs.

FS communication uses differential signaling - test both positive and negative lines of each pair

Replace Suspect Cables

Replace any damaged FS communication cables with genuine Heidenhain parts maintaining proper cable routing and strain relief.

Check FS Module Status LEDs

Examine the status LEDs on the FS module - normal operation shows steady green, while red or flashing patterns indicate hardware faults.

Document the exact LED pattern as this provides specific fault codes for Heidenhain service

Access FS Diagnostics

Navigate to MOD 'Diagnosis' → 'FS Status' to view detailed FS microcontroller diagnostic information and communication status.

Screenshot all diagnostic screens before clearing alarms - this data is crucial for troubleshooting

Perform FS Module Reset

Execute controlled FS reset through TNC diagnostic menu or by cycling power to FS module following proper safety lockout procedures.

FS reset will disable all safety functions until system restart and validation is complete

Monitor Communication Recovery

After reset, monitor FS communication status in real-time through diagnostic screens to verify stable cyclic communication restoration.

Check TNC System Status

Access MOD 'Diagnosis' → 'System Info' to verify main processor status and check for additional communication-related alarms.

Look for patterns of multiple communication alarms which indicate main processor issues

Verify TNC Software Version

Check current TNC software version in MOD 'System' → 'Software' and compare against FS module compatibility requirements.

FS communication protocols are version-specific - mismatched versions cause cyclic communication failures

Perform TNC Communication Test

Execute built-in communication diagnostics through MOD 'Service' → 'Communication Test' to isolate TNC interface functionality.

Communication tests may temporarily interrupt machine operation - ensure safe machine state first

Clear Communication Buffers

Reset TNC communication buffers through service menu and restart cyclic communication to FS microcontroller.

Identify Interference Sources

Check for new electrical equipment, welders, or high-power devices operating near the machine that could generate EMI affecting FS communication.

FS communication is particularly sensitive to interference in the 1-10 MHz range

Verify Cable Shielding Integrity

Inspect FS communication cable shielding for breaks or improper grounding, ensuring 360-degree shield connection at both ends.

Use an oscilloscope to check for noise on FS communication lines during machine operation

Check Electrical Panel Grounding

Verify proper grounding of TNC control cabinet and FS module mounting, ensuring low-impedance path to machine ground.

Always verify power isolation before checking ground connections

Install Additional EMI Filtering

Add ferrite cores or EMI filters to FS communication cables if interference sources cannot be eliminated or relocated.