Heidenhain codes
HeidenhainParameterIntermediate30-120 minutes

231-C022

HEIDENHAIN 231-C022 - C022 SMB or SPL configuration error

C022 SMB or SPL configuration error

This TNC 640 error indicates invalid machine parameter settings. The control has detected configuration data that does not match the hardware setup.

Root Cause Summary

The 231-C022 alarm specifically indicates that the Heidenhain control has detected an inconsistency in the functional safety configuration data for the Safety Motion Block or Safety PLC subsystem. This typically results from configuration file corruption, version mismatches between safety software components, or incomplete acceptance of safety parameter changes during commissioning or modification procedures.

Safety

  • Refer to Heidenhain service manual
  • Ensure qualified technician performs repairs

Causes and Fixes

  1. 1

    Access Safety Configuration Directory

    Use MOD function with authorized password, navigate to File Management, and browse to TNC:/sys/SafetyPLC/ or TNC:/sys/SMB/ to verify presence and integrity of configuration files (SafeConfig.xml, SafetyPar.saf, or similar).

    Only authorized and trained personnel should access safety-related files. Unauthorized changes can compromise machine safety.

  2. 2

    Check Safety Configuration Checksum

    In MOD > Safety Configuration, verify the displayed checksum value matches the documented value from commissioning documentation. Mismatch indicates configuration corruption or unauthorized modification.

    Always document the safety configuration checksum during initial commissioning and keep it with machine documentation for future verification.

  3. 3

    Restore from Backup

    Navigate to TNC:/sys/backup/SafetyPLC/ and identify the most recent validated backup. Copy the backup files to the active TNC:/sys/SafetyPLC/ directory, replacing corrupted files.

    Ensure the backup being restored is from the correct machine configuration and has been validated for this specific control and safety I/O setup.

  4. 4

    Reinitialize Safety System

    After restoring configuration files, perform complete power cycle (not just NC reset). Upon restart, navigate to MOD > Safety Configuration and verify configuration is accepted and checksum is correct.

    If no backup exists, contact machine builder for original safety project file or use Heidenhain SafetyDeveloper software to regenerate configuration from documented parameters.

DIY Feasiblehigh confidence

Call a technician if:

  • ·CC software update required
  • ·MC configuration corruption with no backup
  • ·Multiple HSCI devices showing same error

Prevention

  • Regular backup of HSCI configuration parameters
  • Document SMB/SPL device versions during installation
  • Verify software compatibility before connecting new safety devices

Common Mistakes

  • Mixing SMB and SPL device parameters in same configuration
  • Forgetting to reset HSCI after parameter changes
  • Using incorrect MP7680 device type settings

Seeing Multiple Alarms?

Seeing another alarm with this one? Enter the code.

Get machine-aware diagnosis

AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.

Start free

Was this guide helpful?

Always verify with your machine manual or a certified technician before performing service procedures.