239-001C

Check CC card supply voltages

Navigate to MOD > Service > Diagnosis > Voltage monitoring and verify all supply voltages on the affected CC card are within specification (+24V ±5%, ±15V ±5%).

Use the TNC's built-in voltage display rather than external meters for initial diagnosis as it shows what the FS controller actually sees.

Inspect power supply connections

Power down and check all connector contacts on X101 (24V supply) and X102 (±15V supply) on the CC card for corrosion, looseness, or damage.

Always follow LOTO procedures and wait 5 minutes after power-down before handling connections.

Measure external supply stability

Using a DMM, verify the incoming 24VDC supply stability under load - voltage should remain within 22.8V to 25.2V during axis movement.

Check supply ripple with oscilloscope - excessive ripple (>200mV p-p) can cause intermittent FS monitoring faults.

Reset FS monitoring system

After correcting voltage issues, perform FS system reset via MOD > Service > FS Reset and cycle power to reinitialize voltage monitoring.

FS reset requires machine parameter MP7300 to be temporarily set to 1 - restore to 0 after reset.

Verify FS microcontroller status

Check MOD > Service > Diagnosis > FS Status for additional FS-related error codes that would indicate microcontroller hardware failure.

Look for concurrent alarms in the 238-xxxx or 240-xxxx ranges which often accompany FS microcontroller failures.

Perform FS self-test

Execute the FS built-in self-test via MOD > Service > FS Self-Test to isolate whether the monitoring circuits or other FS functions are compromised.

FS self-test will disable all axis motion during execution - ensure machine is in safe state.

Check FS firmware version

Verify FS microcontroller firmware version in MOD > Service > Version Info matches the TNC software version - mismatched versions can cause monitoring failures.

FS firmware updates require special Heidenhain service tools and should typically be performed by authorized technicians.

Replace CC axis card

If FS self-test fails and firmware is correct, the CC card FS microcontroller has likely failed and requires card replacement.

CC card replacement requires axis parameter backup and restoration - document all MP parameters before replacement.

Check grounding integrity

Verify PE (protective earth) continuity from CC card mounting to main electrical cabinet ground - resistance should be <0.1 ohms.

Use a low-resistance ohmmeter or continuity tester specifically designed for ground testing.

Inspect cable shielding

Examine all cables connected to the affected CC card for damaged shielding, particularly encoder and motor power cables which can radiate interference.

Damaged motor cable shielding can create dangerous voltage potentials - handle with appropriate PPE.

Identify interference sources

Monitor alarm occurrence pattern - if intermittent, correlate with operation of nearby equipment like welders, VFDs, or other high-power switching devices.

Use the TNC's alarm log with timestamps to correlate interference patterns with external equipment cycles.

Implement EMI suppression

Install ferrite cores on affected cables and verify proper separation (>6 inches) between power and signal cables in cable management systems.

Heidenhain recommends specific ferrite core part numbers for different cable types - consult technical documentation for optimal suppression.

Monitor CC card temperature

Check current CC card temperature in MOD > Service > Diagnosis > Temperature - should be below 60°C during normal operation.

Temperature readings above 55°C indicate inadequate cooling and potential component stress.

Verify cooling system operation

Inspect cabinet cooling fans, air filters, and ventilation paths to ensure adequate airflow across the CC card heat sinks.

Clean filters only with compressed air while wearing appropriate respiratory protection.

Check thermal cycling correlation

Monitor if alarm occurs during temperature transitions (startup/cooldown) which would indicate thermal stress on voltage reference components.

Use the alarm log to identify patterns - thermal issues often show up 15-30 minutes after power-on or during ambient temperature changes.

Implement temperature mitigation

If temperature is excessive, improve cabinet ventilation or consider relocating heat-generating components away from the CC card area.

Maintain cabinet ambient temperature below 40°C and ensure minimum 100mm clearance around CC cards for proper convection cooling.

Verify FS monitoring parameters

Check machine parameters MP7310-MP7319 (FS monitoring configuration) to ensure they match the CC card specifications and haven't been inadvertently modified.

Compare current MP values with machine documentation or backup parameter files to identify unauthorized changes.

Review CC card type parameters

Verify MP1010 (axis card type) correctly identifies the installed CC card model - incorrect identification can cause wrong monitoring thresholds.

Changing MP1010 requires power cycle and may affect other axis parameters - backup all settings first.

Restore default FS parameters

If parameter corruption is suspected, restore FS monitoring parameters to factory defaults via MOD > Machine Parameters > Reset FS Parameters.

Document current parameter values before reset in case custom tuning was intentionally applied.

Perform parameter validation

After parameter correction, cycle power and verify alarm clears, then test all axis functions to ensure proper FS monitoring operation.

Always perform complete axis function testing after FS parameter changes to ensure safety systems remain operational.