130-0195

Access PLC Task Diagnostics

Press MOD key → select 'System' → 'PLC' → 'Diagnostics' or 'Task Overview'. Review active cyclic tasks and their execution times. Look for tasks with unusually high cycle times or excessive quantity of timed OBs.

On iTNC 530/TNC 620/640, you can also access detailed PLC load information via MOD → Settings → System Configuration → PLC Runtime.

Review PLC Program Structure

Contact machine manufacturer for PLC source code review. Identify cyclic OBs (organization blocks) with time-critical triggering, particularly OB10-OB38 which are time-interrupt driven. Check if multiple fast-cycle OBs are running simultaneously.

Do not modify PLC program without machine manufacturer authorization and complete system backup, as this can affect safety functions.

Optimize or Consolidate PLC Tasks

Work with machine builder to consolidate redundant time jobs, increase cycle times for non-critical tasks, or move operations to the main PLC cycle (OB1) instead of using separate timed interrupts.

Moving routine checks from 10ms interrupt OBs to 50ms or 100ms cycles can significantly reduce scheduler load without affecting machine performance.

Check Software Version Consistency

Press MOD → Info → Version. Document NC software build number and compare with PLC compiler version. Access MOD → Settings → General → System Info to verify all system components match expected versions.

Mismatched PLC compiler and NC software versions after partial updates are a common cause of task scheduler failures.

Reload PLC Program with Clean Compilation

Backup current PLC via MOD → PLC → Backup. Obtain verified PLC source from machine manufacturer, delete existing compiled PLC object code, and recompile fresh using the TNC's PLC development environment or PlcEdit software.

Ensure you have verified backup and machine manufacturer support before deleting PLC programs. Machine safety functions depend on PLC operation.

Restore System Configuration

If available, restore TNC system configuration from known-good backup using MOD → Backup/Restore → System Restore. Alternatively, use Heidenhain Service Partition recovery (hold MOD+HELP during bootup on TNC 620/640) to restore factory system files while preserving PLC and parameters.

The Service Partition restore function reinstalls the real-time kernel without affecting machine-specific programs if performed correctly.

Verify Control Model Specifications

Check the TNC control ID plate and documentation. Compare installed machine complexity (number of axes, I/O points, PLC program size) against Heidenhain specifications for that control model. TNC 320 supports fewer concurrent tasks than TNC 640.

Heidenhain Technical Manual for your specific control version contains maximum task limits in the PLC system specifications section.

Evaluate Control Upgrade Feasibility

If machine complexity genuinely exceeds control capacity, consult with Heidenhain service or authorized retrofitter about upgrading to higher-capacity control (e.g., TNC 320 → TNC 640, iTNC 530 → TNC 620). Document current system load before recommendation.

Control upgrades require significant investment and machine downtime. Exhaust all optimization options first.

Implement PLC Optimization for Hardware Limits

Work with machine builder to reduce PLC complexity: eliminate unused functions, reduce I/O scan frequency for non-critical points, combine multiple simple tasks into single optimized routines, and remove diagnostic code not required for production operation.

Disabling extensive PLC diagnostic logging and trace functions can free significant real-time resources on resource-constrained controls.