How Does G154 Call O9014 on DMG MORI MAPPS Controls?

The current configuration contains four working call mappings: G150 through G153 select programs O9010 through O9013. Adding a fifth program exceeds that configured set, but it does not exceed the available mapping range. No spindle current, axis load, or thermal condition causes this symptom; the number that matters is the NC parameter that associates a G code with a protected macro program.

Fixes That Leave the Call Unmapped

Three changes can make O9014 look correct without making G154 execute it. Each change affects a different layer of the control.

The new program and variable can both be valid while the call still fails. The missing operation is the entry of 154 in NC parameter #6054.

Macro-Call Mapping Mechanism

Parameters #6050 through #6059 specify which G codes call programs O9010 through O9019. The parameter and program numbers advance together:

For the fifth entry, the program offset is four: 9014 - 9010 = 4. Apply that same offset to the start of the parameter range: 6050 + 4 = 6054. Enter the G-code number as 154, without the letter G, in #6054. The resulting association is G154 to O9014.

This mapping is separate from the macro-variable system. A block containing G154 is interpreted through the NC parameter table, while references to #604 inside O9014 read or write macro data.

Numbers, Limits, and Read Locations

The leading # makes the two numbers look related, but their functions are different. #604 holds macro data. #6054 configures a call association. Typing 154 into the comment field for #604 changes neither value nor mapping.

NC Parameter-Screen Access

On a regular MAPPS interface, locate the green SYSTEM key to the right of the numeric keypad. Press it, then select the NC Systems soft key; this is the F1 key below the display in the described layout. The resulting screen uses an older NC-style presentation rather than the normal MAPPS presentation. More than one press may be needed before the NC system screen appears.

Once the parameter screen is visible, type 6054. Select the soft key labeled SEARCH to move directly to that parameter. This is an NC parameter page, not the custom macro-variable window that displays #604.

On a CELOS-equipped machine, the SYSTEM and SETTINGS controls are located to the left of the upper screen. Use those controls to reach the same NC-system and parameter functions. Confirm which interface is installed from the physical panel instead of applying one key location to both layouts.

Parameter-Change Procedure

1. Place the machine in a safe, idle condition under the facility's approved parameter-change procedure. Record the existing value of #6054 before editing it.
2. Confirm that O9014 exists and that its program number is exactly O9014. Review its two changed references and verify that both use #604.
3. Search the relevant programs and variable assignments for existing use of #604. A shared variable can couple otherwise independent macros if another routine reads or writes it.
4. Press SYSTEM, select NC Systems, open the NC parameter screen, enter 6054, and select SEARCH.
5. Switch the control to MDI mode. Open the Setting menu in the same control cluster as the System function and enable Parameter Write.
6. Expect the alarm to sound when Parameter Write is enabled. In this interface, that indication does not prevent the parameter edit.
7. Enter 154 as the value of #6054. Keep the G-code letter out of the numeric parameter field.
8. Read the displayed parameter back and confirm #6054 = 154.
9. Disable Parameter Write after the edit and return the control to the operating mode required by the approved test.

If #6054 already contains another value, stop before overwriting it. Identify which production program uses that mapped G code and decide whether the old association must remain. A parameter copy or maintenance record provides the recovery value if the new mapping has to be reversed.

Program Logic and Variable Separation

The call mapping only selects O9014; it does not validate the serial-number logic inside the macro. Compare O9014 with the working programs O9010-O9013 and isolate the intended changes. If the only required differences are two variable references, the executable differences should be the two substitutions from #600 to #604.

Check the initial value and ownership of #604 before releasing the macro. The serial-number result depends on whether that variable already contains a value, where it is initialized, and which programs update it. Read those facts from the macro-variable display and the associated program logic; a correct G-code mapping cannot repair an incorrect starting serial number or an unintended second writer.

Treat comments as documentation. A comment beside #604 can identify its purpose, and a comment in O9014 can state that the intended call is G154, but the executable link remains #6054 = 154.

Controlled Verification and Fault Isolation

1. Reopen the NC parameter page and verify that #6054 reads 154 after Parameter Write has been disabled.
2. Verify that the program directory contains O9014 and that the control can display its executable blocks.
3. Record the current value of #604. Confirm that it matches the serial-number value expected before the first call.
4. Run an approved test containing the intended G154 call in the shop's controlled prove-out mode. If the macro contains motion or marking operations, use the same guarding, offsets, workholding, and single-block practices required for that operation.
5. Observe the program display or execution trace and confirm that control transfers to O9014, not one of O9010-O9013.
6. After execution, read #604 and inspect the produced serial-number result. Confirm both the intended value change and the absence of changes to #600-#603.

Frequently Asked Questions