![\"How](\"https:\/\/www.ihylight.com\/wp-content\/uploads\/2026\/10\/How-to-Specify-Low-Flicker-COB-LED-Modules-PWM-PstLM-SVM-and-Driver-Design-1024x576.webp\")
<\/p>\n<\/p>\n
A low-flicker COB LED module cannot be selected by wattage, voltage, or a \u201cflicker-free\u201d label alone. PWM LED flicker, driver current ripple, dimming behavior, PstLM, and SVM all describe different parts of the same system-level problem. A COB LED may operate normally on a bench yet show visible flicker, unstable low-level dimming, or stroboscopic effects after it is connected to the final driver and controller.<\/p>\n
For OEM engineers, equipment manufacturers, repair teams, and technical buyers, the practical question is not simply \u201cWhat causes LED flicker?\u201d It is how to identify the source, define acceptable performance, and buy a COB LED and driver combination that can be verified in the finished equipment.<\/p>\n
COB LED flicker can originate from the LED source, driver, input power, dimming method, controller, wiring, or the interaction between these components. The U.S. Department of Energy notes that LED drivers play an important role in maintaining light output over time and that incompatibility between a driver and a dimming system can result in substantial flicker.A standard DC COB LED module is a passive semiconductor package (LED array on substrate) without active driver electronics. Thus, output flicker is fundamentally governed by the power supply\u2019s DC current ripple and the controller\u2019s dimming waveform, rather than the COB itself.<\/p>\n
That is why replacing the COB first is not always the correct troubleshooting step.<\/p>\n
Start by asking when the flicker occurs. If the COB operates steadily from a known stable current source but becomes unstable after a particular driver, dimmer, or controller is connected, investigate the electrical and control system before rejecting the COB.<\/p>\n
Flicker at every output level may point toward unstable input power, poor connections, loss of current regulation, or an unsuitable driver operating window. Flicker that appears only during dimming is more likely to involve the dimming method, PWM behavior, minimum driver load, controller signal, or low-level regulation.<\/p>\n
For a replacement project, record the existing COB current and forward-voltage requirements, driver output range, control interface, wiring, and operating conditions before ordering another module. Matching wattage alone can reproduce the original fault. A deeper electrical compatibility process is covered in choosing a driver for a high-power COB LED module<\/u><\/strong><\/a>.<\/p>\n PWM dimming controls average LED output by rapidly switching current on and off. This can provide precise control, but PWM frequency alone does not determine whether a system will have acceptable temporal light modulation.At low PWM duty cycles (e.g., < 1%), standard LED drivers may suffer from finite rise\/fall switching times or minimum pulse width limitations, causing pulse dropping, unstable current regulation, and visible low-frequency flicker.<\/p>\n The actual result depends on the switching frequency, duty cycle, waveform, driver response, controller behavior, and the application in which the light is used. A frequency that appears acceptable in general illumination may still require closer examination where moving objects, imaging systems, inspection equipment, or deep dimming are involved.<\/p>\n When evaluating why an LED flickers with PWM dimming, check more than the nominal PWM frequency. At low brightness, the duty cycle becomes shorter, which can expose unstable switching, irregular pulses, limited driver response, or controller timing problems that are not apparent at full output.<\/p>\n A higher PWM frequency may reduce some visible effects, but it should not automatically be treated as proof of a low-flicker system. The driver still has to regulate current correctly, respond consistently to the control signal, and remain stable across the required dimming range.<\/p>\n Buyers should therefore define the lowest usable dimming level, the intended control method, and any application-specific flicker requirements. Prototype testing should use the actual controller and driver rather than a simplified laboratory setup that does not represent the final equipment.<\/p>\n PstLM and SVM address different temporal light effects, so a supplier specification containing only one of them may not answer every engineering question.<\/p>\n PstLM is used to assess short-term flicker visibility for a static observer in a static environment. SVM, or stroboscopic visibility measure, addresses changes in motion perception associated with modulated light. For light sources within the scope of EU Ecodesign Regulation (EU) 2019\/2020, the applicable full-load requirements include PstLM \u2264 1.0 and SVM \u2264 0.4, subject to the regulation\u2019s scope and exceptions. A bare COB package or module should not automatically be assumed to fall under the same product classification.<\/p>\n An OEM should not treat PstLM and SVM as interchangeable versions of the same number. A system can perform differently depending on whether the concern is direct flicker perception or stroboscopic effects involving motion.<\/p>\n This matters when specifying lighting for equipment with moving parts, machine inspection, studio or imaging applications, or other environments where the interaction between light modulation and movement is important. For general illumination, the purchasing criteria may be different.<\/p>\n The more important procurement question is whether the supplier can state what was measured and under what conditions. A claim such as \u201cflicker-free\u201d has limited engineering value without the driver, controller, input condition, output level, and measurement method behind it.<\/p>\n The IEA 4E Solid State Lighting Collaboration has also highlighted the importance of measurement conditions in TLM testing, including the influence of the AC power supply on PstLM results.<\/p>\n Once the source of flicker has been narrowed down, corrective action should focus on the system rather than automatically replacing the LED module.<\/p>\n Driver current regulation, output ripple, the COB forward-voltage range, the dimming architecture, and controller compatibility all affect the result. A driver that powers a COB successfully at 100% output may still perform poorly near the bottom of the dimming range.To achieve ultra-low flicker (PstLM < 0.1, SVM < 0.1), select a driver with output current ripple under \u00b13% (or < 5% peak-to-peak) at full operating forward voltage range, or use high-frequency PWM (> 2 kHz) \/ hybrid CCR (Constant Current Reduction) dimming.<\/p>\n First confirm that the driver can regulate the required COB current while keeping the complete operating forward-voltage range inside its supported output window. Two COB modules with similar wattage can require very different voltage and current combinations, so nominal power does not establish compatibility.<\/p>\n Next, examine the dimming method. PWM, analog current reduction, and external control interfaces create different requirements. The driver, controller, and COB should be evaluated together, particularly when low-level dimming is part of the equipment specification.<\/p>\n Current ripple also matters because variation in LED current can translate into variation in light output. The acceptable level depends on the application and should be verified against the complete product specification rather than a generic rule.<\/p>\n A prototype that is stable at full brightness has passed only one operating point. Problems may appear at 50% output, near the minimum usable dimming level, during transitions, after warm-up, or when input conditions change.<\/p>\n A useful validation sequence should therefore include full output, an intermediate dimming point, and the lowest required operating level. Testing should be repeated using the intended production driver, controller, wiring, and representative thermal conditions.<\/p>\n IHY’s existing driver-selection guidance similarly notes that a driver may operate normally at full output yet develop flicker or control problems at low brightness.<\/p>\n For OEM development, the acceptance criterion should describe the configuration being tested. A single flicker result without the driver and operating condition can create false confidence during supplier approval.<\/p>\n Replacement projects carry an additional risk: the failed or unstable system may already contain a mismatched driver, controller, or electrical architecture.<\/p>\n Simply buying another COB with similar dimensions and wattage may restore light output without correcting the original flicker problem.<\/p>\n Before requesting a replacement, identify the module type and collect as much electrical information as possible: operating current, forward-voltage range, input architecture, driver model or output specification, dimming interface, connector arrangement, and the conditions under which flicker occurs.<\/p>\n Then isolate variables. Determine whether the problem changes with another known-compatible driver, whether it appears only below a certain dimming level, and whether poor wiring or unstable input power is involved.<\/p>\n The next purchase should be based on electrical and control compatibility rather than physical fit alone. If the existing design leaves uncertainty about the module boundary or driver architecture, comparing suitable integrated LED modules<\/u><\/strong><\/a>\u00a0can also help determine whether a more integrated replacement is appropriate for the equipment. IHY publicly lists DC, AC, UV\/IR, and cinematic or studio-lighting module categories, although final suitability still depends on the individual product specification.<\/p>\n For a new OEM project, \u201clow flicker\u201d should be translated into measurable purchasing requirements before samples are ordered. This is especially important when the COB, driver, and control system come from different supply boundaries.<\/p>\n A supplier needs enough information to determine whether a standard COB, an integrated module, or a customized light engine is the more practical solution.<\/p>\n A useful RFQ connects the application to the electrical and control architecture instead of requesting a generic \u201cflicker-free COB LED.\u201d<\/p>\n Where a standard module cannot satisfy electrical, mechanical, optical, or control requirements, custom COB LED design for OEM applications<\/u><\/strong><\/a>\u00a0can be considered. IHY’s published custom-design process emphasizes defining the application, electrical architecture, driver, dimming method, and final-system interfaces rather than choosing a COB by wattage alone.<\/p>\n Supplier evaluation should focus on engineering evidence rather than marketing terminology. Ask whether a low-flicker claim is tied to a defined driver, control method, dimming point, input condition, and measurement setup.<\/p>\n It is also important to establish the supply boundary. Is the supplier providing a bare COB, a regulated module, or a light engine that includes supporting electronics? The answer changes which party is responsible for driver compatibility and system validation.<\/p>\nHow Does PWM Dimming Affect LED Flicker?<\/b><\/strong><\/h2>\n
PWM Frequency, Duty Cycle, and Low-Level Dimming: What Actually Needs to Be Checked?<\/b><\/strong><\/h3>\n
PstLM vs SVM: Which Flicker Metric Should an OEM Check?<\/b><\/strong><\/h2>\n
When PstLM and SVM Tell You Different Things<\/b><\/strong><\/h3>\n
How to Reduce Flicker Through LED Driver and System Design<\/b><\/strong><\/h2>\n
![\"IHY](\"https:\/\/www.ihylight.com\/wp-content\/uploads\/2026\/10\/IHY-220V-50W-AC-COB-LED-module-with-integrated-smart-IC-and-driverless-design-1024x1024.webp\")
<\/p>\nDriver Current Ripple, Dimming Method, and Module Compatibility<\/b><\/strong><\/h3>\n
Why Full-Output Testing Is Not Enough for a Low-Flicker Design<\/b><\/strong><\/h3>\n
How to Troubleshoot or Replace a Flickering COB LED Module<\/b><\/strong><\/h2>\n
What to Check Before Replacing the COB LED or Driver<\/b><\/strong><\/h3>\n
How to Specify and Buy a Low-Flicker COB LED Module<\/b><\/strong><\/h2>\n
What to Put in a Low-Flicker COB LED RFQ<\/b><\/strong><\/h3>\n
\n\n
\n RFQ Item<\/b><\/strong><\/td>\n Information to Provide<\/b><\/strong><\/td>\n<\/tr>\n \n Application<\/td>\n Fixture or equipment type and operating scenario<\/td>\n<\/tr>\n \n COB electrical requirements<\/td>\n Target current and required forward-voltage range<\/td>\n<\/tr>\n \n Driver<\/td>\n Existing driver data or required output architecture<\/td>\n<\/tr>\n \n Dimming<\/td>\n PWM, analog, or other control method<\/td>\n<\/tr>\n \n Dimming range<\/td>\n Lowest required stable operating level<\/td>\n<\/tr>\n \n Flicker requirement<\/td>\n Required metric or acceptance target, if defined<\/td>\n<\/tr>\n \n Test configuration<\/td>\n Driver, controller, input, and operating condition<\/td>\n<\/tr>\n \n Validation<\/td>\n Prototype acceptance points and final-equipment testing<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n How to Evaluate a COB LED Supplier\u2019s Low-Flicker Claims<\/b><\/strong><\/h3>\n