27094

Identify the source part program triggering the alarm by reviewing the active program name in Diagnostics > Program Status on the 840D HMI or via SINUMERIK Operate menu.

Search the offending part program for direct writes to safety variables using syntax patterns like '=', 'MOV', or 'MOVE' commands targeting $SFT_ prefixed variables or safety memory ranges (typically MD 32000-32999 related variables).

Do not attempt modifications to safety variables outside _N_SAFE_SPF; this will trigger alarm 27094.

Move all safety variable write operations to the NCK Safety Part Program (_N_SAFE_SPF) located in the part program directory. Use SINUMERIK Editor to open _N_SAFE_SPF and consolidate safety logic there.

Verify the corrected program by performing a cold restart (MODE > OFF, then MODE > AUTO) and re-execute the part program. Monitor Diagnostics > Alarms for confirmation that 27094 no longer appears.

Verify the exact filename of the safety part program using the SINUMERIK file browser (Menu > Part Programs > All). Confirm it is named precisely '_N_SAFE_SPF' with the correct underscore prefix and no additional characters or extensions.

The SINUMERIK system is case-sensitive and requires exact matching of the reserved program name.

Check that _N_SAFE_SPF is stored in the correct directory path: /_N_CST_DIR/_N_SAFE_SPF (Customizing directory). Verify via Siemens automation tool or direct HDD inspection if needed.

Confirm the safety SPL program header includes the proper declaration syntax. Open the program and verify it starts with appropriate safety block markers and does not have conditional logic that might bypass safety variable access.

If the safety program structure is corrupted, restore it from the machine's backup or system image. Restart the NCK (cold start) to reinitialize the safety program registry.

Enable NCK trace logging (Service > Diagnostics > Trace) and capture the exact timestamp and source of alarm 27094. Cross-reference with PLC cycle logs and external interface activity to determine if the write originates outside the NC domain.

Audit the PLC program (STEP 7 or IEC code) for any MOV, MOVE, or assignment instructions targeting NCK safety variables or SIEMENS-reserved memory addresses (check symbol table for $SFT_ or 0x8000+ address references).

PLC writes to safety variables are not permitted; coordinate variable modifications solely through the NCK part program.

If external systems (PROFINET, HMI terminals, or network clients) attempt variable writes, configure access control lists in the SINUMERIK communication parameters (Parameters > Network > Access Rights) to block non-NCK write requests.

Document the corrected logic flow and perform an integrated test (NC + PLC + external interface) to confirm alarm 27094 no longer appears.