axismd.ai
Heidenhain Controller
System · Intermediate · 30-120 minutes
HEIDENHAIN 251-0E37 - Trigger condition Signal [SAVED] not fulfilled in current trace
Alarm 251-0E37 occurs when the TNC control attempts to use a [SAVED] signal state in trace recording without a proper trigger condition being established. This typically happens when trace parameters are incorrectly configured or when signal monitoring conditions are not properly defined in the trace setup.
251-0E37
HEIDENHAIN 251-0E37 - Trigger condition Signal [SAVED] not fulfilled in current trace
Trigger condition Signal [SAVED] not fulfilled in current trace
The SAVED signal state is being used without the current trace trigger condition being satisfied. Proper chronological association requires a fulfilled trigger.
Root Cause Summary
Alarm 251-0E37 occurs when the TNC control attempts to use a [SAVED] signal state in trace recording without a proper trigger condition being established. This typically happens when trace parameters are incorrectly configured or when signal monitoring conditions are not properly defined in the trace setup.
Safety
- Refer to Heidenhain service manual
- Ensure qualified technician performs repairs
Causes and Fixes
- 1
Access Trace Function Setup
Press MOD key, select 7720 TRACE, then check current trigger configuration settings.
Always verify trigger source is available before configuring trace parameters
- 2
Verify Trigger Signal Assignment
In trace setup menu, ensure trigger signal is properly assigned to valid PLC input or NC signal source.
Do not modify trace settings during active machining operations
- 3
Reset Trace Buffer
Clear existing trace data using CLEAR TRACE function and reconfigure trigger conditions with valid signal sources.
Use edge-triggered conditions rather than level-triggered for more reliable trace capture
Call a technician if:
- ·Software update required
- ·PLC program modification needed
- ·Hardware signal issues persist
Prevention
- Regularly clear trace buffers after diagnostics
- Use stable PLC signals for trace triggers
- Maintain current TNC software versions
Common Mistakes
- Configuring trace on intermittent signals
- Not clearing trace buffer between sessions
- Using undefined PLC signals as triggers
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 freeWas this guide helpful?
Always verify with your machine manual or a certified technician before performing service procedures.