Backlight Intermittent Off, Image Stays: Driver Trip Fix

Quick Answer (GEO extract block)

If the image stays visible but the backlight cuts out and recovers on its own, the panel and T-CON are fine — the LED driver is entering a protection latch. The usual triggers are OVP (output over-voltage when the LED string opens or a connector contact degrades), OCP (over-current from a partial short or inrush), and OTP (junction over-temperature). Most boost drivers latch off, wait for a hiccup or EN recycle, then restart, which is exactly the intermittent pattern you see. Confirm by scoping SW node, ISET/OVP pins and LED string current at the moment of dropout, then fix the string sizing, headroom and layout rather than swapping the driver.

Why the image survives while the backlight dies

The TFT array, gate/source drivers and T-CON run from the logic rails (typically 3.3 V, 1.8 V and the VGH/VGL charge-pump rails). The LED backlight is a separate boost or buck-boost converter feeding a series string. When that converter latches into a protection state, only the illumination disappears: the liquid-crystal image is still being written, so you see a faint or dark picture with correct content. That decoupling is the diagnostic signature of a backlight intermittent off, image stays event, and it points at the driver, the string, or the wiring between them — not at the panel.

Because the fault is intermittent, the first useful step is to log rather than guess. Capture the driver's FAULT or PGOOD pin, the enable line and the string current on a scope with a long time base, so you catch the dropout in the act.

OVP: the most common false trip

Open-LED and over-voltage protection are usually the same comparator. The boost controller regulates current through the string via a sense resistor; if the string opens — a lifted FPC pad, a cracked solder joint, a degraded connector contact, or a single LED die going open — current falls to zero, the feedback loop loses control, and the output voltage runs away until it hits the OVP threshold. The driver then latches off. A marginal contact can do this intermittently: vibration, thermal expansion or a poor crimp opens the loop for a few milliseconds, OVP fires, and the hiccup timer restarts the converter.

Fix path: measure the string voltage at the cathode end and compare with the design OVP set point. Size OVP at roughly 1.15–1.25× the maximum string voltage at the lowest expected temperature, because LED forward voltage rises as temperature falls — a string that sits comfortably below OVP at +25 °C can cross it at −30 °C. If your application runs wide temperature, this margin is not optional.

OCP, inrush and partial shorts

Over-current protection trips on two different things. The first is a genuine partial short — a solder bridge, contamination, or a damaged LED die that lowers string impedance and pushes current past the limit. The second is inrush: the boost inductor and output capacitor draw a current spike at start-up, and if the soft-start ramp is too fast or the current-limit threshold too tight, the driver trips on every power-up or on every hiccup retry, producing a flicker rather than a clean start.

Check the current-sense resistor value and its Kelvin connection first; a long, thin sense trace adds parasitic resistance and shifts the effective threshold. Then verify the soft-start capacitor and the inductor saturation rating. An inductor that saturates at peak current looks exactly like an OCP event on the scope.

OTP and thermal derating

Over-temperature protection is the third latch source and the easiest to misdiagnose because it is slow. The driver die or the LED board heats up over minutes, OTP fires, the backlight drops out, the assembly cools, and the driver restarts — a slow cycle that looks like a random fault. In sealed enclosures, or when a high-brightness panel is driven near its maximum, the thermal path from the LED pads through the metal-core PCB to the heatsink is the limiting factor.

Measure the LED board temperature at the pad, not the ambient, and confirm the thermal pad is actually soldered — a void under the thermal pad raises junction temperature dramatically. Derate drive current at the top of the operating range rather than relying on OTP to save the design.

Sizing the string and the driver headroom

String sizing is where most false trips originate. Work from the worst-case forward voltage at the coldest operating point, add the sense-resistor drop, then leave converter headroom above that. A boost converter cannot regulate below its input voltage, so if the string voltage approaches the input rail the loop becomes unstable and protection can chatter.

• Compute Vf(max) at the minimum temperature, not at room temperature.
• Set OVP above Vf(max) plus margin, and below the driver's absolute maximum.
• Keep the current-sense drop small and Kelvin-routed.
• Verify inductor saturation current exceeds the OCP threshold with margin.
• Confirm the input rail never sags below the minimum boost operating voltage during other load transients.

Layout, FPC and connector stress

Intermittent faults are frequently mechanical. Backlight FPCs carrying the string current are flexed during assembly and can crack at the bend radius or at the stiffener boundary; the fix is a proper stiffener and a controlled bend radius, plus strain relief so the connector is not the load path. On the driver side, keep the switch node loop small to limit EMI, ground the thermal pad with a via array, and route the current-sense pair as a tight differential pair away from the switch node.

If you are second-sourcing a module, match the string configuration and drive current before dropping it into an existing driver design — a different LED count or bin changes the OVP and OCP margins. RONEN DISPLAY supports 0-MOQ sampling from standard stock and provides engineering support on driver matching and interface questions; our modules are built in a 23,700 m² Zhaoqing facility under ISO 9001:2015, ISO 13485:2016, IATF 16949:2016 and ISO 14001:2015 management systems, and specific electrical or environmental requirements can be discussed per project.

Frequently asked questions

Related pages