The operator sees an asymmetric display after a battery discharge: most of the MillPlus V400 interface is English, while the user softkeys remain German. The machine can run again after restoring BIOS parameters and machine constants, but changing the language constant alone may not refresh every displayed text layer.
The number that matters is not a machining load or software timeout. It is the loss of battery-backed configuration, followed by the controller’s activation sequence. A saved language selection requires both a warmstart and a main-switch power cycle before judging the result.
Battery-backed configuration loss
An exhausted backup battery can leave a controller unable to retain setup data while primary power is absent. In this case, recovery required restoring BIOS parameters and constants before the machine would operate. The mixed-language display appeared after that recovery.
This creates two separate diagnostic questions:
- Does the stored machine constant contain the intended language?
- Has the control completed the restart sequence that loads the selected language into the active interface?
A displayed language selection is not proof that every interface component has reloaded it. The MillPlus V400 procedure described here requires saving the constant, performing a warmstart by leaving MC-Edit for MDI, and then cycling the main switch. Until all three actions occur, the screen can continue showing a mixture of old and newly loaded resources.
Symptoms and deciding causes
| Observed condition | Likely decision point | Where to check |
|---|---|---|
| Main interface is English and user softkeys are German | The selected language has not been activated across all interface layers, or the recovered configuration contains mismatched language data | Language option reached through F4, Menu, and the final menu column; then inspect the related machine constant |
| German is already selected in the machine constants | The value may be saved but not active | Confirm the save operation, warmstart transition, and main-switch cycle |
| The display remains mixed after one German selection | The controller may need a forced resource reload | Select a third language, activate it fully, and then repeat the complete sequence for German |
The editor shows DIN ISO instead of the remembered DIN
|
Programming-language or editor mode may also have changed during recovery | Inspect the editor or machine-constant setting separately from the interface-language selection |
| Settings change again after power removal | Battery retention or restored configuration remains unresolved | Read the battery status indication and compare all recovered BIOS and machine constants with the machine record |
The mixed softkeys are the strongest clue. A completely wrong language points first to the selected language constant. A split interface points first to activation, cached resources, or separate text groups. That distinction makes a full activation cycle more useful than repeatedly editing the same value without powering the control down.
Supported correction approaches
| Approach | When to use it | Advantage | Limitation |
|---|---|---|---|
| Reselect German and restart | The language constant is wrong or has not been saved since configuration recovery | Shortest correction path | May leave the symptom unchanged if German was already stored and the active resources did not reload |
| Select another language, activate it, and return to German | German is already stored but English and German remain mixed | Forces a visible state change before the desired language is loaded again | Requires two complete save, warmstart, and power-cycle sequences |
Change the DIN ISO editor setting |
The programming or editor mode itself is wrong | Corrects an independently recovered editor configuration | It is not established as the cause of mixed user-softkey language |
| Restore configuration from the machine record | Multiple settings changed after battery loss | Addresses broader configuration loss instead of treating one display symptom | Requires a known-good machine-specific record or official service data |
For a machine that already shows German in the language constant, use the alternate-language method. It tests whether the selection mechanism works and forces the control through a real language transition. Treat DIN ISO as a parallel configuration check, not as the first language repair.
Language and editor-mode separation
The interface language and the editor’s displayed programming mode describe different functions. Interface language controls operator text such as menus and softkeys. An indicator such as DIN ISO identifies an editor or programming-language selection. Changing one may not change the other.
After battery-backed settings are lost, both values can differ from their former states because several constants may have been restored manually. A remembered DIN indication is therefore worth investigating, but using it to explain English menus and German user softkeys skips the direct language activation test.
Record the current value before changing any machine constant. The evidence identifies neither a constant number nor a parameter address for the language or DIN ISO setting. Read those identifiers from the actual MC-Edit screen or the machine-specific documentation rather than applying a value from another MillPlus installation.
Recommended language reload procedure
- Place the machine in a safe, non-cutting state and record the currently displayed language and editor-mode values.
- Open the relevant control menu with
F4, selectMenu, and page to the final column. Locate the language option. Menu availability or wording can depend on the recovered configuration. - Open the associated setting in
MC-Edit. If German is not selected, select it. If German is already selected while the display remains mixed, select a language other than German or English for the first test. - Save the changed constant. A screen selection that has not been saved will not survive the following restart operations.
- Perform the warmstart by changing from
MC-EdittoMDI. This transition is part of the stated activation sequence; it is not replaced by merely closing a menu. - Turn the main switch off, wait briefly, and turn it on again. No exact off-time is specified, so use the machine’s documented shutdown and restart practice rather than inventing a delay.
- After startup, check whether the main menus and user softkeys all changed to the test language. This confirms that the selection, save operation, and reload path are functioning.
- Return to
MC-Edit, select German, save the constant, and repeat the warmstart fromMC-EdittoMDI. - Cycle the main switch off and on again using the same controlled sequence.
Changing directly from German to German provides no visible proof that a new resource set loaded. The temporary third language supplies that proof. If the third language appears everywhere but German again produces mixed text, the fault is narrowed to the German resource selection or restored configuration rather than the restart procedure.
Activation timing and power-cycle control
The saved constant and the active display state are different layers. Saving writes the requested selection. The warmstart transfers control out of the machine-constant editor. The main-switch cycle causes startup initialization to reload the interface resources. Skipping a layer leaves the diagnostic incomplete.
| Quantity or state | Required condition | Where to read or observe it |
|---|---|---|
| Selected language | Desired language, or a third language during the forced-reload test | Language menu and related MC-Edit constant |
| Saved state | Changed constant committed before restart | Save confirmation or retained value when the setting is reopened |
| Warmstart | Transition from MC-Edit to MDI
|
Active control mode |
| Main-switch off-time | Brief wait using the machine’s documented shutdown practice | Main switch and machine documentation; no exact interval is given |
| Reload result | Menus and user softkeys show one language | Startup screen, normal menus, and user-softkey pages |
A software-only warmstart is insufficient for this reported language change. Likewise, cycling the main switch before saving the constant only reloads the previously stored selection. Keep the operations in order so that each observed result has one interpretation.
Verification and fault isolation
Verify more than the first page displayed after startup. Open a normal menu, the editor, and several user-softkey pages. All operator-facing labels should use the selected language, while the editor-mode indicator should match the separately required programming mode.
- Reopen the language setting and confirm that it retained the selected value after the main-switch cycle.
- Compare main-menu text with user-softkey text. A single language across both groups confirms the original symptom is cleared.
- Open the editor and record whether it shows
DINorDIN ISO. Correct that setting only from the machine’s known configuration record. - Run another controlled shutdown and startup. Confirm that the language and editor mode remain unchanged.
- Review other manually restored BIOS parameters and machine constants if any setting fails to persist. Battery loss can make a language symptom one visible part of a wider configuration problem.
If the alternate language also appears only on part of the interface, the issue is no longer just a German selection. Check for incomplete machine-specific data, user-softkey resources that are maintained separately, or a configuration set that does not match the machine. Avoid guessing constant numbers or copying a complete configuration from another machine.
Configuration preservation after recovery
Once the display and editor settings are correct, preserve the recovered state using the machine’s approved backup method. Record the final BIOS values, machine constants, language choice, and editor mode. The useful baseline is machine-specific because these values can govern more than operator text.
Resolve the battery-retention problem before relying on the repair. A language setting that works until the next loss of primary power indicates that persistence remains defective. Read the battery condition from the control or maintenance information available on the machine, and follow the manufacturer’s replacement procedure for the installed hardware.
Frequently asked questions
Can I activate the MillPlus V400 language without switching off the main switch?
The described activation requires saving the constant, performing a warmstart from MC-Edit to MDI, and cycling the main switch. A warmstart alone does not complete that sequence.
Does selecting German again fix German softkeys with English menus?
It may if the value was not saved or activated. If German is already selected, first activate a language other than German or English, then select German and repeat the full restart sequence.
Can I use the DIN ISO setting to change the display language?
Treat DIN ISO as an editor or programming-mode setting, separate from the operator-interface language. Check it against the machine record, but troubleshoot mixed menus and softkeys through the language setting first.
Does a saved language constant take effect immediately?
No. Save it, leave MC-Edit for MDI to perform the warmstart, then turn the main switch off, wait briefly, and turn it on again.
Can I keep troubleshooting if the language still will not persist?
Stop changing constants when the selected language fails to survive a controlled power cycle, multiple recovered settings remain wrong, or no known-good machine record is available. Escalate to DMG’s official support channel with the machine identification, MillPlus V400 control type, battery-loss history, recorded constants, and the results of the alternate-language test.