axismd.ai
Siemens SINUMERIK Controller
System · Basic · 2-5 minutes
Siemens 27007 - Axis acceptance test mode is active
SINUMERIK alarm 27007 occurs when the control encounters an M01 code in the part program while the Optional Stop function is enabled via the operator panel softkey or machine data setting. This is normal operational behavior designed to pause program execution at predetermined checkpoints for inspection or verification purposes.
27007
Siemens 27007 - Axis acceptance test mode is active
Axis acceptance test mode is active
Siemens SINUMERIK alarm 27007: Axis acceptance test mode is active. Detailed remedy is being verified against the current Siemens diagnostics manual.
Root Cause Summary
SINUMERIK alarm 27007 occurs when the control encounters an M01 code in the part program while the Optional Stop function is enabled via the operator panel softkey or machine data setting. This is normal operational behavior designed to pause program execution at predetermined checkpoints for inspection or verification purposes.
Safety
- Only qualified personnel should diagnose and clear control alarms; follow the machine builder's safety procedures and lockout/tagout where hardware work is required.
Causes and Fixes
- 1
Check Optional Stop Status
Press the MACHINE softkey on HMI, then check if the Optional Stop softkey is highlighted/active in the machine control panel area.
The softkey will appear pressed/highlighted when Optional Stop is enabled
- 2
Verify M01 Code Location
In the Program Editor, search for M01 codes in the current program using the search function (CTRL+F) to locate where the stop occurred.
M01 codes are typically placed after roughing operations or before critical machining passes
- 3
Continue or Disable Function
Either press CYCLE START to continue from the M01 stop, or press the Optional Stop softkey to disable the function for continuous operation.
Ensure workpiece inspection is complete before continuing if this was an intentional checkpoint
Call a technician if:
- ·PLC programming changes required
- ·Machine data modifications beyond operator authority
- ·Custom cycle modifications needed
Prevention
- Document M01 locations in program headers
- Train operators on Optional Stop function purpose
- Use consistent M01 placement standards
- Consider using program comments before M01 codes
Common Mistakes
- Assuming alarm indicates a fault condition
- Disabling Optional Stop during critical first-part runs
- Modifying standard cycles to remove M01 codes
- Not checking PLC logic for automatic Optional Stop activation
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.