014

Identify the exact command entered in MDI mode that triggered the alarm by reviewing the control screen or alarm history.

Check parameters 3201-3232 (G-code restrictions) and 3211-3242 (M-code restrictions) to verify if the command is blocked for MDI execution. Bit settings control MDI allowance.

If the command must be executed, either run it from a stored program in MEMORY mode or contact machine builder to modify parameter restrictions if operationally safe.

Modifying parameter restrictions may compromise machine safety interlocks. Verify with OEM documentation before changing.

For custom M-codes calling macros, verify the macro program exists and parameters allow macro execution from MDI (parameter 6071 bit settings).

Review the MDI command entry for program control statements like M98, M99, WHILE, DO, END, GOTO, or other flow control commands.

If subprogram execution is needed, create a simple main program calling the subprogram and run from MEMORY mode instead of MDI.

Break complex MDI operations into individual sequential commands executed one at a time rather than attempting multi-line program logic.

Verify parameter 3107 bit 0 (MDI program restart) is set correctly if attempting to restart interrupted MDI operations.

Check if the command involves G10 (programmable data entry), G65 (macro call), or system variables that are parameter-protected from MDI access.

Review parameters 3290-3299 and 8136 for write-protection settings on work coordinate systems, tool offsets, and macro variables during MDI operation.

Verify the control key switch position and parameter 3107 settings which govern MDI operation permissions and edit capabilities.

Key switch position may be required in specific setting for certain MDI operations per machine builder configuration.

If offset or coordinate changes are necessary, access through the offset screen directly or create a dedicated setup program in MEMORY mode with appropriate protection.