A MillPlus control on a 1997 DMU50 V that stops at Heidenhain Service Menu has reached a startup branch but has not continued into the normal machine application. In the reported case, a faulty or sticking operator-panel key held the startup sequence in that branch. Pressing the affected key released or changed its state, after which the machine completed startup. Diagnose the key state before treating the symptom as lost machine data or a failed control.
Initial startup decision
- Record the exact displayed text. For this symptom, confirm that the screen reads
Heidenhain Service Menu. A readable menu shows that the display and part of the control startup path are operating; it does not prove that the normal MillPlus application has loaded. - Do not select service functions merely to escape the screen. Service menus can contain data-transfer, backup, restore, and configuration functions. An unverified selection can turn a startup-input problem into a data or configuration problem.
- Inspect the entire operator keyboard and panel for a key that remains physically depressed, returns slowly, sits lower than adjacent keys, or feels different when pressed. Before anything else, confirm that every key returns freely.
- Press and release only the suspect key while observing its travel and return. In the documented case, operating the faulty key allowed the machine to continue booting.
- If the menu clears and normal loading begins, allow the startup sequence to finish without pressing additional keys. The resolving branch is a false or retained key input during startup.
- If no key is visibly or mechanically abnormal, continue with controlled key isolation rather than guessing at menu commands.
Operator-panel key-state check
A key can remain electrically active even when its cap appears released. Contamination, mechanical wear, a damaged return mechanism, or a contact that does not open cleanly can leave the keyboard interface reporting an active input. Startup logic may evaluate that input before the normal control application loads. If the input selects or arrests a maintenance path, the display remains at the service menu.
Use the following observations to separate a key problem from a general startup failure:
| Reading or observation | Meaning | Next check |
|---|---|---|
| One key is visibly low or does not return | Mechanical retention can hold its electrical contact active | Release and exercise that key, then observe whether startup continues |
| A key feels normal but operating it clears the menu | The contact may have been electrically retained or intermittent | Repeat a controlled cold-start test without touching the panel |
| All keys release, but the menu appears only intermittently | An intermittent panel input remains plausible | Compare the symptom with panel vibration, key movement, and repeated starts |
| The menu persists regardless of all key movement | The simple mechanically stuck-key branch has not resolved the fault | Stop experimenting with menu options and escalate to panel-input or control startup diagnostics |
Do not move on until the panel has been checked as a complete input surface. A second depressed key can mask the effect of releasing the first. Include function keys, membrane areas, and any key close to an enclosure edge where a damaged bezel could apply pressure.
Controlled key isolation
Randomly pressing keys once restored this installation, but random operation is not a repeatable maintenance method. Convert that observation into a controlled test:
- Photograph or write down the current menu before touching the panel. This preserves the initial state and prevents uncertainty about whether a selection changed.
- Look across the keyboard from a low angle and compare the height of each key. Press no menu-confirmation key while making this inspection.
- Choose only a key that appears retained or has abnormal travel. Press it once and release it fully.
- Watch for one of three outcomes: normal loading resumes, the highlighted menu item merely changes, or nothing changes. Normal loading directly associates that key action with release of the startup hold. Cursor movement alone shows that the keyboard is responding but does not identify the startup cause.
- If normal loading resumes, identify and label the suspect key for repair. Do not treat one successful release as proof that the contact is reliable.
- If the display does not change, do not work through every key by trial. Power down using the machine’s established shutdown practice and have the operator panel input state checked through the applicable service diagnostics or electrical measurements.
The decisive measurement is whether any key input remains active when no key is being touched. Read that state in the machine’s applicable keyboard diagnostic, if available, or test the panel through the manufacturer’s service procedure. The exact key identifier and intentional service-menu entry sequence are not specified here, so selecting a supposed shortcut would be guesswork.
Startup-branch mechanism
The symptom differs from a blank display or a control that never executes visible startup code. The machine presents a named menu, which places the failure after basic display output becomes available but before the normal MillPlus operating state is reached. The useful diagnostic question is therefore not “Does the screen work?” but “What input or startup condition selected this branch?”
For this machine, changing the state of a faulty key allowed the boot process to continue. That makes the operator keyboard the first diagnostic boundary. A momentary press can free a mechanically bound cap, wipe an oxidized contact surface, or cause an intermittent contact to open. Those mechanisms also explain why the fault may disappear during investigation and return at the next power cycle.
The presence of the service menu alone does not show that machine files failed to load or were erased. File loading occurs later in the normal path, so a branch taken beforehand can prevent the operator from seeing the usual loading sequence even when the stored data remains intact. Confirm storage or data loss only from the control’s later diagnostics, not from this menu symptom.
Symptom-to-cause boundaries
| Symptom | Primary interpretation | Confirming action |
|---|---|---|
Heidenhain Service Menu appears immediately after the main switch is turned on |
The control entered or remained in a service startup branch | Inspect untouched key states before navigating the menu |
| Normal boot resumes after one abnormal key is pressed and released | A retained or faulty key input caused the startup interruption | Repeat startup with all keys untouched and confirm whether the symptom returns |
| The menu returns on later starts | The key or its electrical input remains unreliable | Repair the key or panel and verify inactive input state |
| The menu never clears after the panel check | The demonstrated stuck-key remedy does not resolve this occurrence | Check keyboard input diagnostics and the control’s startup diagnostics without altering service data |
| Normal operation starts but a specific key later misbehaves | The panel fault remains present during operation | Remove the machine from unattended use and correct the operator-input fault |
This boundary prevents two common diagnostic errors: interpreting a visible service menu as proof of missing data, and interpreting one successful boot as a permanent repair. A startup that succeeds after key manipulation confirms a useful cause-and-effect relationship, but repeated untouched starts are needed to test whether the condition has actually been removed.
Resolving procedure and repair acceptance
- Turn the machine off using its normal shutdown sequence, then leave every operator-panel key untouched.
- Inspect key height, freedom of travel, and return action. Correct external mechanical interference only if it can be done without dismantling energized equipment or changing control settings.
- Start the machine and observe the display. If
Heidenhain Service Menuappears, operate only the previously identified suspect key once and release it. - Confirm that the service menu disappears and that normal machine data loading proceeds. Do not move on until the control reaches its usual operating screen.
- Shut down and repeat the startup without touching any key. If the menu returns, repair or replace the faulty key, keyboard assembly, or associated input path as determined by the panel diagnostic.
- After repair, check that the suspect input reads inactive with the key released and active only while it is deliberately pressed.
- Perform multiple controlled startups with no keys held. Each cycle must bypass the service menu, complete normal loading, and leave every operator key responding once per deliberate press.
Service access and data backup boundary
The service menu may be relevant to data backup or interface work, but the accidental-entry symptom does not identify the intentional entry sequence. Obtain that sequence from the documentation matched to the installed MillPlus control and machine configuration, or from an official service channel. A key sequence from another control revision can select a different function or fail to apply.
Before intentional service access, record the machine state, define which data set will be backed up, identify the destination interface, and establish how the backup will be verified. Entering the menu is not itself a backup. A usable backup requires a completed transfer and a verification method appropriate to the control’s documented procedure.
Keep troubleshooting and backup work separate. First correct the unintended key input and prove repeatable normal startup. Then schedule deliberate service-menu access using the matched procedure. This separation prevents an intermittent keyboard input from disrupting a transfer or causing unintended menu navigation.
FAQ
Why does my MillPlus stop at the Heidenhain Service Menu?
A retained operator-panel key can hold the startup sequence in the service branch. Inspect every key, then press and fully release the abnormal key; this action allowed the 1997 DMU50 V installation to complete startup.
Why does pressing a key make the MillPlus boot normally?
The press can release a mechanically bound key or change an intermittent contact from active to inactive. Treat that result as identification of a panel-input fault, then repair the input and test again without touching the keyboard.
How do I verify that the MillPlus startup fault is fixed?
Confirm that the suspect key input is inactive when released and active only while pressed, then perform multiple startups with every key untouched. The final verification is normal data loading and arrival at the usual operating screen without displaying Heidenhain Service Menu.