Sinumerik 840D NCU 7-Seg Status 'b': Resolving HMI Error 120202

Problem Overview: NCU Status "b" and HMI Error 120202

On Sinumerik 840D and 840D sl controllers, the NCU (Numerical Control Unit) carries a single-digit orange 7-segment status display on its front panel, accompanied by the PR, 5 V, and (on later revisions) NCOK LEDs. The display is the operator's most direct observation of the embedded controller's state because it remains visible even when the HMI link is broken. The failure mode described here is unambiguous: after a long shutdown of a 5-axis machine, the NCU halts at a lower-case "b" character on its 7-segment display, while the HMI operator panel reports error 120202 "Wait for the connection to the NC/PLC". The status never advances to the "6" runtime indicator, and the HMI cannot establish the host link.

The reference document for these states is the SINUMERIK 840D sl Operating System NCU (IM7) manual on Siemens Industry Online Support, document ID 109481527. Per the IM7 documentation, the lower-case "b" is the canonical visual for the BIOS post-code state. The 840D / 840D sl NCU uses an embedded bootloader that cycles through BIOS post codes during the load-BIOS phase; the lower-case "b" distinguishes this BIOS phase from runtime indicators. Under normal conditions, the "b" clears within 30 to 90 seconds as the bootloader moves on to load the Linux-based HMI runtime and the NCK operating system, eventually settling on the "6" state (the legacy indicator for "NCK ready"). On older NCU revisions used with MMC 103 / PCU 50 panels (as in the reported case), the same "b" character persists as the visual until the HMI/PLC host link is fully operational.

The most likely categories of root cause for this fault cluster are the NCU's hardware chain (battery, CompactFlash, NV-RAM license), the PROFIBUS / MPI physical layer between the NCU and the operator panel, and the HMI operator-panel bus configuration. The diagnostic procedure below resolves them in sequence; substituting parts without isolating the category wastes time and budget.

NCU 7-Segment Display State Reference

The single-character 7-segment display on the 840D NCU and 840D sl NCU is a hardware-encoded state machine. Engineers rely on it as the first diagnostic because it does not require an HMI link to be functional. The table below summarises the most frequently observed characters during the controller's lifecycle.

Color-Coded LED Cross-Check

Each front-panel LED corresponds to a specific subsystem. Always cross-reference the 7-segment character with these LEDs to localise the fault:

• 5 V (green): The internal DC rail generated by the SINUMERIK power module from the backplane. If this LED is OFF, the NCU has no logic supply and the 7-segment will be blank.
• PR (yellow/green): PROFIBUS/MPI token activity. Steady ON or slow blink indicates token passing; constant OFF with "b" stuck is the classic "host link not coming up" pattern.
• NCOK (green, on later revisions): Replaces the older PR state on certain NCU boards. Constant ON = NCK has accepted its software and the PLC is in run; OFF = NCK boot stalled.

Why Lower-Case "b" Specifically

The 7-segment glyphs for lower-case "b" and upper-case "B" are visually distinct: the lower-case glyph uses only the lower-left, bottom, lower-right, and middle segments. The display firmware uses the lower-case glyph specifically to indicate the BIOS phase. When the BIOS hand-off to OS loader completes, the bootloader rewrites the same physical segment with the upper-case "B" character, then advances through C, D, E, and the rest. The use of a unique glyph for BIOS state eliminates ambiguous interpretation when reading the display from a distance or in a low-contrast cabinet.

BIOS POST Code Sequence and the Lower-Case "b"

The IM7 documentation defines that during the load-BIOS phase the 7-segment display cycles through an ordered series of BIOS post codes documented as: B, C, D, E, F, G, H, I, J, K, L, M, N, O, Ö, P, Q, R, S, T, U, Ü, V, W, X. Each letter is an opaque milestone in the embedded controller's POST. The lower-case "b" is rendered only when the BIOS is actively running and the controller has not yet transitioned to the OS loader.

A healthy boot moves off "b" within 60 to 90 seconds and continues through the OS load states before settling at "6". If the display never moves off "b", the post sequence has stopped, is retrying in a loop, or has failed to find the NCK operating system image on the CompactFlash card. The same IM7 document notes that the BIOS phase uses an orange segment color, switching to green once the OS load begins. Observing the color transition provides additional confidence that the boot chain has reached the OS loader.

Communication Architecture: NCU ↔ Operator Panel

The 840D NCU, the PCU 50 / PCU 70 operator panel, and any legacy MMC 103 are linked through a single PROFIBUS / MPI segment that runs RS-485 differential signalling. The segment carries NC services (NCK variable read/write, axis commands), PLC services (PLC flag / DB read/write, status), and HMI rendering commands and operator input. Without that link, the operator panel cannot render the SINUMERIK Operate pages, and the NCU cannot be commanded.

The topology is a single linear RS-485 bus terminated at both physical ends. Termination is mandatory because reflections on an unterminated bus corrupt the differential signal at higher baud rates and the bus token-passing protocol breaks. The most common physical-layer failures for the "stuck on b / error 120202" symptom are exactly within this segment.

Bus Speed and Distance Limits

The PROFIBUS / MPI segment length is dictated by the baud rate. Refer to the IEC 61158 / IEC 61784 series for the formal reference. The 840D-era installed base most commonly uses:

Root Cause Analysis for Persistent Status "b"

Field experience with the 840D shows that an NCU stuck on "b" with HMI error 120202 always traces to one of the following root cause families. Distinguish them with the diagnostic procedure below before swapping parts, because mis-diagnosis between the bus and the NCK firmware chain is the most expensive route.

Family A — Host Communication Physical Layer Failure

• Broken or shielded PROFIBUS cable (opens, shorts, water ingress, crushed sheath)
• Missing, open, or incorrectly placed termination (Rt ON / OFF)
• Reversed pin assignments on the 9-pin D-Sub (A-line ↔ B-line swap)
• Shield bond broken at one or both cabinets
• Ground reference (M5V, pin 5) lift due to dissimilar cabinet grounds

Family B — Bus Parameter Mismatch

• HMI baud rate set to a value the NCU does not support (for example 12 Mbps entered against an MPI-only NCU)
• HMI address conflict with another master on the segment
• Highest station address (HSA) set above the actual number of stations, causing token rotation timeouts
• Wrong bus type (MPI vs PROFIBUS-DP) chosen at the HMI when the NCU expects the other

Family C — NCK Firmware Not Loading

• CompactFlash card seated incorrectly or partially ejected
• Card corrupted (improper shutdown, file system error, missing directory structure)
• Missing or invalid license file on the card
• NCK and PLC binaries mismatched in version
• Service / commissioning switch left in a non-default state

Family D — Battery / NV-RAM Fault

• Internal battery exhausted during long shutdown (typical after 2–5 years depending on type)
• Battery holder corrosion interrupting contact
• NV-RAM checksum failure causes NCK to skip the boot stage

Family E — HMI Boot Failure

• PCU/MMC may also be stuck in its own POST
• Operator panel CF/HDD faulty
• HMI software not licensed, or operator-panel firmware corrupt

Family F — Hardware Fault in the NCU

• Failed PLD, RAM, or step-down converter on the NCU motherboard, causing the BIOS to stall in the post sequence
• Backplane connector oxidation between NCU and power module

Tools, Prerequisites, and Safety

Diagnostic Procedure — Step by Step

Execute the steps in order. Each step eliminates a category before you change parts, preventing wasted time and component costs.

Step 1 — Power and Battery Verification

1. Confirm the SINUMERIK power module outputs 24 V DC and the internal 5 V DC rail is healthy. The 5 V LED on the NCU front panel must be ON steady.
2. Power down and open the NCU service cover. Locate the lithium backup battery holder (typical part on the 6FC5247 family).
3. Measure the open-circuit voltage. Expected 3.4–3.7 V.
4. If the voltage is below 3.4 V, replace the battery. Note: replacing the battery while the NCK is alive with valid machine data preserves the data; if the NCK has already lost the data, re-load it from the commissioning backup.
5. Power-cycle the NCU. Observe the first 90 seconds of the 7-segment display with a camera. Capture the entire sequence including any brief flashes.

Step 2 — CompactFlash Card and NCK Image Verification

1. Power down completely.
2. Remove the CompactFlash card from the NCU slot.
3. Inspect the contacts for oxidation. Clean with isopropyl alcohol if necessary, then dry completely before re-inserting.
4. Re-seat the card firmly; a partially seated card presents to the BIOS as empty and the post sequence halts.
5. Read the card on a PG (card reader) running the appropriate SINUMERIK service tool. Verify the directory structure: /siemens, /user, the NCK binary, PLC binary, and the license file must be present.
6. If the firmware is suspected corrupted, re-load the NCK image from the project's archived backup.

Step 3 — Physical Layer Verification of the PROFIBUS / MPI Link

1. Power down both NCU and PCU/MMC before unplugging.
2. Disconnect the bus cable from each end. Visually inspect the 9-pin D-Sub connectors for bent pins, cracked shells, or loose backshells.
3. Use a multimeter to measure the bus termination: with both terminator switches ON at the two end nodes, the resistance between pins 3 (RxD/TxD-P, B-line) and 8 (RxD/TxD-N, A-line) must read between 110 Ω (two 220 Ω in parallel) and 220 Ω (only one termination active).
4. Verify shield continuity from end to end using the shield pin (pin 1) at one end to the shell at the other.
5. Inspect the shield bond at each cabinet where the cable enters. A drained shield bond at one cabinet can let common-mode noise into the bus and cause intermittent token loss without breaking the segment outright.
6. Replace the entire cable if any conductor or shield reading is open or short.

Step 4 — Bus Termination Switch Positions

The two physical end nodes of the segment must have their termination switches in the ON position; all intermediate nodes must be OFF. On 840D-era PCU and NCU front panels the termination switch is a slide switch next to the bus connector, often labelled "Rt ON" / "Rt OFF".

A wrong switch position (for example termination ON at a middle-of-line NCU) corrupts the bus and the HMI will not connect; meanwhile, the NCU may still load its own firmware internally, which is why the 7-segment indicates activity but the operator panel times out with error 120202. Verify switch position by physical inspection of every device on the segment.

Step 5 — HMI Operator Panel Communication Parameters

1. Power up the PCU/MMC and wait for its own POST to complete (the operator panel itself has its own 7-segment if it is an MMC 103, or a software boot indicator on a PCU 50).
2. Enter the Start-Up menu via the operator panel. Softkey path: Start-Up > MMC > Operator Panel.
3. Capture screenshots of every parameter in this page. Compare with the documentation in the 840D / 611D startup manual.
4. Verify and adjust the parameters listed in the table below.

The 187.5 kbps baud rate is the documented default for the legacy MPI path between the HMI operator panel and the NCU. If the speed has been changed in a previous attempt, revert to 187.5 kbps first and confirm operation before further tuning. As the field report notes, even changing baud rate to 187.5 kbps did not resolve the issue, which points to a bus-physical or NCK-NV-RAM category rather than a simple parameter mismatch.

Step 6 — Capture and Interpret POST Codes

1. Power-cycle the NCU.
2. Record the 7-segment sequence with a video camera in slow-motion mode. Even phones with 240 fps are sufficient.
3. Cross-reference each character against the IM7 manual's BIOS post-code table (ID 109481527).
4. A repeatable stop on a single character (for example "I" or "P") indicates that a specific subsystem of the embedded controller is failing; the IM7 manual maps each character to a sub-function.
5. If the controller reliably stalls on lower-case "b" without ever transitioning to upper-case "B", the BIOS is in a tight retry loop and the firmware image or hardware should be suspected.

Physical Layer Verification: Cable Specs, Termination, and Shielding

The PROFIBUS / MPI segment is an RS-485 differential bus. The 840D's standard PG/OP interface uses PROFIBUS-DP cable type A (purple sheath) or the equivalent MPI cable. Hard requirements per IEC 61158 / IEC 61784:

• Conductor cross-section ≥ 0.34 mm² (22 AWG)
• Characteristic impedance 135–165 Ω at 3–20 MHz (PROFIBUS DP cable type A)
• Loop resistance ≤ 110 Ω/km
• Shield: copper braid, ≥ 80 % coverage, bonded at both ends through the D-Sub metal backshell
• Stub length (drops) ≤ 1 m; cumulative stubs ≤ 6.6 m per segment
• Segment length ≤ 1.2 km at 187.5 kbps; ≤ 200 m at 1.5 Mbps

Termination must be 220 Ω ± 5 % resistor pairs at both physical ends, energised only at the bus power node (typically the NCU side). The standard PROFIBUS 9-pin D-Sub pinout is:

Cable Replacement Procedure

1. Power down NCU, PCU, and any other stations on the segment.
2. Discharge and lock out per cabinet safety rules.
3. Cut the new PROFIBUS cable to the exact length required between the two physical end devices; avoid coiling excess cable.
4. Crimp the two D-Sub connectors to the IEC 61158 pinout above. Use the metal backshell specified by Siemens for shield bonding.
5. Torque the connector screws to 0.5–0.7 Nm. Avoid over-tightening on plastic shells.
6. Re-engage termination ON only at the two end devices; verify all intermediate devices are set to Rt OFF.
7. Power up the segment and immediately check for token activity on the PR LED of every station.
8. Execute the HMI Start-Up verification to confirm.

HMI Operator Panel Communication Parameters (Detailed)

The HMI operator panel's bus configuration is stored locally on the PCU/MMC. To access the parameters from the HMI itself, navigate to Start-Up > MMC > Operator Panel. On a fresh install the most common field values for an 840D are:

If the panel accepts rate changes but error 120202 persists, the issue is not the parameter set but the link layer. If the HMI Start-Up page itself is not reachable (the field reports that navigating to the page was successful), then a Panel-PC level fault can be ruled out and the path is at the link layer or NCU boot chain.

Bus Parameter Diagnostic Quick Reference

Use this matrix to triage symptom combinations:

NCU Firmware, CompactFlash, Battery, and Long-Downtime Recovery

The 840D NCU is a real-time computing platform; without a properly imaged CompactFlash card and a healthy backup battery, the BIOS has no path to load the NCK operating system. The "long downtime" history in the original field report is a strong indicator for battery exhaustion — lithium thionyl chloride cells on the 6FC5247 family have a typical service life of 3 to 5 years depending on temperature and load, and storage beyond that window with no charging cycles (the controller was off) often drops the battery below the voltage threshold required to retain NV-RAM.

Battery Verification and Replacement

• Open the NCU service cover and locate the lithium backup battery holder.
• Measure the open-circuit voltage with the controller powered down. Expected 3.4–3.7 V.
• If below 3.4 V, replace with the correct part from the 6FC5247 family (refer to the BOM for the exact article number for the NCU revision in use).
• After replacement, re-apply the last known good machine data from the commissioning backup archive. The machine data archive normally lives on the project server or in the documentation directory of the machine.
• Note that some NCU revisions support "battery change while NCK is alive" (hot-swap); refer to the IM7 manual (ID 109481527) for the specific NCU version.

CompactFlash Card Verification

• Pull the card and inspect contacts for contamination or bent pins in the NCU socket.
• Validate the card in a card reader on a PG running the appropriate SINUMERIK service tool.
• Check for the existence of the NCK directory, PLC image, and the license file. A corrupt license will stop the NCK before it finishes loading.
• If the card is unreadable, re-image from the project's archived backup (typically delivered with the machine documentation).

Field-Specific Considerations After a Long Downtime

When the machine has been out of service for more than 6 months, address the following in addition to the standard procedure:

1. Connector oxidation. Disconnect and reconnect each D-Sub to wipe the contacts. Use DeoxIT D5 or equivalent if the cabinets show signs of humidity.
2. Corrosion on the backplane. Inspect the NCU ↔ power module backplane fingers for green/white corrosion.
3. Battery recap as preventive. Replace the battery even if it measures above 3.4 V; a long-discharged cell can drift rapidly after being re-loaded.
4. Drive modules. The 611D modular drives also have backup batteries / capacitor-backed memories; if those have been lost, the drive parameters revert to defaults and the drives will not enable until re-loaded.
5. HMI licensing. The license may have expired (time-limited) on the operator panel; verify on power-up.

Verification Checklist After Repair

After each intervention, run the full verification below before declaring the machine operational.

1. Power-cycle the NCU and observe the 7-segment display with a camera. Confirm it cycles through the BIOS post codes (B, C, D, …) within 30–60 s, advances through the OS load numbers, and finally settles on "6".
2. Confirm the 5 V LED is steady green throughout the sequence.
3. Confirm the PR LED is steady green and the NCOK LED (if fitted) is steady green at the end of the sequence.
4. On the HMI operator panel, confirm that error 120202 clears and the start-up page appears within 30 s of NCU reaching "6".
5. Navigate to Start-Up > MMC > Operator Panel and confirm the bus link parameters are healthy. Save a screenshot for the commissioning archive.
6. Move each axis through the manual / handwheel test routine to confirm full NC ↔ drive ↔ motor path.
7. Execute the PLC stop / start transition and observe that the PR LED continues to blink (token passing is healthy).
8. Run the SINUMERIK Operate diagnosis page to read any residual axis / drive alarms.
9. Sign off the commissioning checklist from the machine's electrical documentation.

Frequently Asked Questions