勛圖tv

Tunable White LED Board Routing: Channel Identity, Bins and Verification

A tunable white LED board needs more than two strings that can be dimmed independently. The released product must preserve which emitters belong to each channel, how their current is measured, which combinations are allowed, and how the assembled optics are checked. A board can pass a light-up test while its warm and cool channels are exchanged or its purchased LED bins no longer match the calibration data.

This review is for engineers releasing a two-channel light engine and its driver interface. It concentrates on routing, channel identity and production evidence. Use the LED driver circuit and headroom guide for topology selection; the task here starts once the intended driver and emitter families are known. The examples below are design-review assumptions, not component ratings or 勛圖tv test results.

Keep the two current paths identifiable through the complete assembly

Warm and cool driver blocks feeding named emitter groups from a shared input
Original engineering schematic: channel identity and sensing boundaries, not a released driver circuit. The actual controller determines the required grounding and sensing arrangement.

Freeze the channel map before placement

Make one table connecting the firmware channel name, driver output, connector pin, LED reference-designator group and intended optical population. Labels such as CH1 and CH2 are useful electrically but do not establish warm versus cool. A supplier can assemble the correct footprints and still reverse the optical groups if the BOM and placement drawing disagree. Use explicit net and assembly labels, and check the connector from both mating views.

Include the service cable in that map. A drawing viewed from the wire-entry side can reverse the apparent order relative to the PCB mating face. Record pin numbers instead of relying only on wire colors. Where a connector can be fitted in more than one position, identify the mechanical feature that prevents the wrong assembly or require an appropriate verification step. Do not let a photograph be the only polarity reference.

For interchangeable light engines, specify which information belongs to the board and which belongs to the controller. If calibration coefficients follow an LED population, replacing that population may require a corresponding configuration change. A controller serial number alone does not identify the installed emitters. The broader LED PCB manufacturing route helps define whether the quotation covers a bare board, populated light engine or its associated driver assembly.

Route regulated current and its measurement as different tasks

Start with the exact driver layout guidance. Identify the switching loops, output-current path, current-sense terminals and control references for each channel. Keeping warm and cool channels identifiable does not mean cutting the ground plane into arbitrary islands. The correct return arrangement depends on the controller, switching topology and where current is sensed. Draw both channels in their relevant switching states before deciding where shared copper is acceptable.

A sense connection should represent the voltage intended by the controller, rather than an unknown combination of that voltage and another channel’s return drop. Review the connection at the sense element terminals and the reference path back to the controller. Keep noisy switching copper away from sensitive control nodes. If a filter is included, use the device guidance and verify its transient behavior; an apparently smoother signal is not proof of a correct measurement.

Check shared connectors and supply paths at every permitted channel combination. A common feed that is adequate when either channel operates alone may be inadequate when both are enabled during startup, calibration or a fault. Conversely, some designs deliberately limit total current across the two channels. That limit must be implemented and tested, not inferred from the intended user interface.

Consider an illustrative shared return resistance of 0.08 ohm. One 350 mA channel produces 28 mV of drop. Two such channels operating together produce 56 mV and 39.2 mW of resistive loss in that shared segment. These are simple circuit calculations, not temperature predictions. Whether the voltage affects regulation depends on the sensing topology. Include connectors and cable contacts when evaluating the real path, and use the copper-trace review for the separate geometry and thermal questions.

Check the warm and cool voltage corners separately

Equal series counts do not establish equal string voltage. The selected warm and cool emitters may have different voltage distributions at the intended current and temperature. For an illustrative six-LED string, assumed forward voltages of 2.9 V and 3.2 V per emitter give 17.4 V and 19.2 V respectively. Against a nominal 24 V supply, the remaining voltage is 6.6 V or 4.8 V before connector, wiring and regulation requirements are considered.

Neither number is an approval margin. Repeat the review using the minimum supply at the actual driver terminals, the relevant maximum string voltage, and the driver’s operating constraints. At the other corner, examine losses and protection behavior. Do not apply a linear-regulator dissipation calculation to a switching stage. Keep the two channels as separate rows so a comfortable warm-channel result cannot hide an inadequate cool-channel condition.

Thermal review also follows the allowed state table. Warm-only, cool-only and mixed operation distribute heat differently, even when their input powers are similar. Record the mounting plate, interface material and enclosure. If an insulated metal substrate is proposed, review the metal-core PCB construction as part of the entire heat path. Its metal base alone does not determine LED junction temperature.

Use optical placement to guide the physical channel pattern

Alternating warm and cool packages can be a useful starting arrangement, but it does not guarantee spatial color uniformity. Pitch, lens geometry, diffuser spacing, viewing angle and thermal gradients all affect the assembled result. Keep optical and mechanical review connected to placement changes. Moving one string to simplify routing may change the visible mixing pattern even when the electrical schematic remains identical.

Define measurement positions that represent how the product will be used. A single central reading can miss edge color separation. Test the final optics at relevant output settings rather than accepting the bare board because all LEDs illuminate. If white solder mask contributes to the optical path, use the white-mask reflectance review to specify that material property separately from electrical or thermal performance.

Release a reproducible color and assembly record

LED procurement bins linked to assembly identity, calibration and optical verification
Original release-record diagram. A procurement bin, a control coefficient and a measured product result are related records, not interchangeable acceptance evidence.

Do not calculate mixed CCT by averaging Kelvin labels

The two nominal CCT values printed in a catalog are not sufficient to calculate the required current ratio for every intermediate white point. The U.S. Department of Energy’s explains two-primary white mixing and why its chromaticity path can differ from the blackbody locus. A midpoint between nominal Kelvin labels is therefore not a reliable firmware calibration rule.

Build the control mapping from defined optical targets and measurements for the actual emitter population and operating conditions. Record the measured color coordinates or agreed color specification, output level, channel currents, temperature condition and instrument geometry together. A changed emitter bin or optic should trigger a review of that mapping. The task is to reproduce an agreed result, not to preserve old coefficients regardless of what changed.

Texas Instruments’ is a documented example of separately controlled warm and cool LED strings. Its reported efficiency, dimming range and hardware choices belong to that implementation. Use the design files to understand its boundaries; do not transfer its measured performance to a different light engine or describe those figures as manufacturing capability.

Write a bin-controlled BOM and an exception process

The purchasing specification should identify the exact LED family and the accepted selections relevant to the product: color grouping, luminous-flux grouping and forward-voltage grouping where used. Record the supplier’s actual bin notation and document revision. A generic note saying equivalent LED permitted is insufficient when a substitute changes the current-to-color mapping, thermal pad connection or optical distribution.

Decide whether lots may be mixed within one light engine and which traceability record is retained. The answer depends on the optical acceptance plan and supply strategy. Avoid inventing a universal rule that all mixed lots fail or all nominally identical bins are interchangeable. For an alternate part, review the package, electrical limits, thermal interface and optical evidence before accepting a procurement-only change.

Minimum channel-release record
Record What to retain What it does not prove
Channel map Firmware output, nets, connector pins and emitter references Optical calibration
LED procurement Exact part, accepted bins and lot identity Finished-luminaire uniformity
Control data Coefficient revision and applicable population Correct physical assembly
Test record Currents, optical condition, limits and equipment Unperformed lifetime or safety qualification

Make the production test distinguish likely mistakes

Begin with an electrical check that exercises each channel independently. Verify that the expected population illuminates and that its measured current lies within the released limits. Then exercise the defined mixed states and startup sequence. A single full-brightness test can conceal exchanged channels because both strings appear illuminated. A simple channel-specific test is more useful than an undifferentiated pass indication.

Keep electrical functional testing distinct from optical characterization. Determine which optical checks are needed on every unit and which belong to a sampling or qualification plan. Specify warm-up time, measurement geometry, operating state and acceptance quantities. If an automated fixture stores results, retain the assembly and firmware revisions with them. A database entry without the tested configuration cannot support a later change review.

Prototype work should deliberately test ambiguous cases: the minimum dimming setting, transitions between endpoints, a restarted controller, an open channel where safe and supported, and the maximum allowed combined load. Use the prototype assembly route to separate these engineering trials from the routine checks intended for production. An engineering experiment is not automatically a factory acceptance procedure.

Send the manufacturing boundary with the files

Provide the board outputs, schematic, exact BOM, placement data, channel map and mechanical thermal interfaces. State which optical or current-setting tasks are requested and which remain with the product team. Include known open questions instead of hiding them behind a general requirement for tunable white. For the bare-board construction, connect the stackup and finish requirements to the PCB manufacturing specification.

A useful quotation request identifies quantity, assembly scope, accepted component alternatives and the required evidence. It also states whether calibration data must be programmed or simply preserved. Ask 勛圖tv to review the tunable-white board package with those boundaries and any unresolved channel, bin or thermal questions. The review should lead to a defined build and test scope; it does not replace optical, electrical-safety or lifetime qualification for the final product.