What causes Siemens SINUMERIK alarm 12722?

Multiple cycle or macro calls combined in a single NC block (e.g., G81-G89 drilling cycles mixed with M-function macros). G65/G66 macro calls programmed together with M-macro invocations in the same block. ISO mode functions (G05, G08, G22, G23, G27, G28, G29, G30, G50.1, G51.1, G72.1, G72.2) mixed with other macro or cycle calls. Improper block syntax where multiple subroutine calls are stacked without proper block separation. G-code post-processor error generating multiple macro/cycle calls on a single line.

How do I fix Siemens SINUMERIK alarm 12722?

1. Review the NC program around channel %1 block %2 and identify all cycle and macro calls present in that single block 2. Separate conflicting calls into individual blocks - place each cycle call (G81-G89), G65/G66 macro call, and M-macro on its own line with proper NC block termination 3. Verify G-code syntax conforms to ISO 2/3 standards where only one primary cycle or macro invocation is allowed per block 4. If using a CAM post-processor, check output settings and regenerate code to ensure macro/cycle calls are not consolidated into single blocks 5. Test the corrected program in DRY RUN mode before executing on the machine to confirm alarm no longer triggers

Siemens SINUMERIK codes

axismd.ai

Siemens SINUMERIK Controller

Servo/Axis · Intermediate · 20-40 minutes

Alarm 12722

Siemens 840D 12722 - Channel block multiple ISO_2/3 macro or cycle calls in the block

A mixture of cycle and macro calls are programmed in a block, e.g. cycle calls with G81 - G89 together with an M macro in the block or a G65/G66 macro call together with M macros in the block. G05, G08, G22, G23, G27, G28, G29, G30, G50.1, G51.1, G72.1, G72.2 functions (ISO mode) also execute subrou

Siemens SINUMERIKServo/AxisIntermediate20-40 minutes

12722

Siemens 840D 12722 - Channel block multiple ISO_2/3 macro or cycle calls in the block

Channel block multiple ISO_2/3 macro or cycle calls in the block

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Common Causes

Multiple cycle or macro calls combined in a single NC block (e.g., G81-G89 drilling cycles mixed with M-function macros)
G65/G66 macro calls programmed together with M-macro invocations in the same block
ISO mode functions (G05, G08, G22, G23, G27, G28, G29, G30, G50.1, G51.1, G72.1, G72.2) mixed with other macro or cycle calls
Improper block syntax where multiple subroutine calls are stacked without proper block separation
G-code post-processor error generating multiple macro/cycle calls on a single line

Troubleshooting Steps

1Review the NC program around channel %1 block %2 and identify all cycle and macro calls present in that single block
2Separate conflicting calls into individual blocks - place each cycle call (G81-G89), G65/G66 macro call, and M-macro on its own line with proper NC block termination
3Verify G-code syntax conforms to ISO 2/3 standards where only one primary cycle or macro invocation is allowed per block
4If using a CAM post-processor, check output settings and regenerate code to ensure macro/cycle calls are not consolidated into single blocks
5Test the corrected program in DRY RUN mode before executing on the machine to confirm alarm no longer 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 free

Was this guide helpful?

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