Heidenhain codes
HeidenhainSafetyIntermediate30-120 minutes

330-00B3

HEIDENHAIN 330-00B3 - MC self test not started

MC self test not started

A warning or error occurred during access to the HSCI hardware bus. This affects communication between control components.

Root Cause Summary

Alarm 330-00B3 occurs when an HSCI (Heidenhain Serial Component Interface) component fails to respond to a safety self-test signal during the TNC startup sequence. The specific HSCI component and signal type are identified in the alarm message, indicating either hardware failure or communication breakdown in the safety circuit.

Safety

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

Causes and Fixes

  1. 1

    Identify Failed Component

    Check the alarm message for STESTDEV_ parameter to identify which HSCI component (encoder, spindle interface, etc.) and note the HSCI address number.

    Cross-reference the HSCI address with MOD function to verify component assignment

  2. 2

    Verify Component Status

    Navigate to Setup > General > Machine Parameters and check parameters 100-109 (HSCI configuration) for the affected component address.

    Do not modify HSCI parameters without proper documentation

  3. 3

    Test Component Communication

    Use MOD function > Component Test to verify basic communication with the HSCI component before declaring hardware failure.

    Compare response times with known good components on the same system

  4. 4

    Replace HSCI Component

    If communication fails, replace the identified HSCI component and reconfigure using Setup > Axes > Encoder parameters.

    Ensure proper ESD protection and power-off procedures before component replacement

Service Recommendedmedium confidence

Call a technician if:

  • ·HSCI component replacement required
  • ·TNC HSCI port failure confirmed
  • ·Safety parameter restoration needed
  • ·Multiple HSCI components affected

Prevention

  • Perform regular HSCI cable inspection and cleaning
  • Monitor HSCI component response times via MOD diagnostics
  • Maintain proper cable routing away from EMI sources
  • Keep backup copies of all safety-related parameters

Common Mistakes

  • Testing HSCI cables with power applied
  • Modifying safety parameters without proper documentation
  • Ignoring EMI sources affecting HSCI communication
  • Replacing components without verifying cable integrity first

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.