Siemens SINUMERIK codes
AxisMD

axismd.ai

Siemens SINUMERIK Controller

Program/G-code · Intermediate · 30-60 minutes

Alarm 16941

Siemens 16941 - Action <ALNX> rejected because no program event has been

The setting of the MD20108 $MC_PROG_EVENT_MASK forces an asynchronous subprogram to be triggered automatically on RESET or PowerOn. The implicitly triggered asynchronous subprograms are normally called "Event- triggered program call" or "Program event". In the alarm situation, this asynchronous subprogram could not yet be activated; that is why the action (normally start of part program) must be rejected. Reasons for the fact that the asynchronous subprogram could not be triggered: 1. The asynchronous subprogram does not exist (/_N_CMA_DIR/_N_PROG_EVENT_SPF) 2. The asynchronous subprogram is allowed to start in the referenced state only (see MD11602 $MN_ASUP_START_MASK) 3. READY is missing (because of alarm) Control reaction: Alarm display.

Siemens SINUMERIKProgram/G-codeIntermediate30-60 minutes

16941

Siemens 16941 - Action <ALNX> rejected because no program event has been

Action <ALNX> rejected because no program event has been

The setting of the MD20108 $MC_PROG_EVENT_MASK forces an asynchronous subprogram to be triggered automatically on RESET or PowerOn. The implicitly triggered asynchronous subprograms are normally called "Event- triggered program call" or "Program event". In the alarm situation, this asynchronous subprogram could not yet be activated; that is why the action (normally start of part program) must be rejected. Reasons for the fact that the asynchronous subprogram could not be triggered: 1. The asynchronous subprogram does not exist (/_N_CMA_DIR/_N_PROG_EVENT_SPF) 2. The asynchronous subprogram is allowed to start in the referenced state only (see MD11602 $MN_ASUP_START_MASK) 3. READY is missing (because of alarm) Control reaction: Alarm display.

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.

Common Causes

  • The setting of the MD20108 $MC_PROG_EVENT_MASK forces an asynchronous subprogram to be triggered automatically on RESET or PowerOn.
  • The implicitly triggered asynchronous subprograms are normally called "Event- triggered program call" or "Program event".
  • In the alarm situation, this asynchronous subprogram could not yet be activated; that is why the action (normally start of part program) must be rejected.

Troubleshooting Steps

  1. 1Load program Check MD11602 $MN_ASUP_START_MASK Acknowledge alarm
  2. 2Clear alarm with the Delete key or NC START

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.