Membrane Switch LEDs: Who Limits the Current?

Draw a boundary around the quoted branch

Start with a schematic, not a phrase such as 'LED ready.' Draw a boundary around the parts delivered with the membrane assembly. Mark the LED reference, any resistor or other electronics, and the connector pins that cross that boundary. Put the OEM controller outside it unless the quotation expressly includes that controller. Ask the supplier to return the same drawing with inclusions and exclusions marked.

For each indicator, name the design owner and the assembly owner separately. An OEM can own the resistor calculation while the supplier installs the released value; alternatively, the OEM board can contain the current-setting circuit. The quote should state which arrangement applies and what approval is needed before components are purchased. Do not assume that responsibility follows the physical location of the LED.

The three scopes in the comparison below are conditional examples, not a ranking. A bare branch can be appropriate when the host electronics already provide current control. An integrated resistor can be considered for an agreed voltage-driven interface. A regulated driver can be appropriate for another system architecture. Compare the full interface cost and unresolved work rather than treating these as interchangeable panel prices.

Use the right electrical model for the delivered scope

ROHM explains that LED forward voltage varies with the device, current and temperature. Its constant-voltage examples use a series resistor to control current and separate resistors for parallel LED branches. These are useful reasons to request an identified branch model instead of a color-based voltage assumption.

Kingbright's SMD application notes also call attention to current limiting and reverse-voltage behavior, including switching transients. Use the selected LED's current document to establish its operating conditions; a general application note does not establish an approved current for your panel.

A regulated-current output is a different scope. For example, TI's TLC59108 has constant-current outputs and a REXT terminal for an external current-setting resistor. That named device illustrates why 'the resistor' may be part of a driver circuit rather than a series component in each LED branch. It is not a component recommendation for a HYR assembly. Ask for the actual driver's current-setting and operating requirements.

Illustrative calculation: nominal 10 mA is not the full range

The following is an original, hypothetical worksheet, not a selected LED design or measured HYR result. Assume one LED and one series resistor in an ideal voltage-fed branch: supply 4.75–5.25 V, LED forward voltage 1.8–2.2 V, and a nominal 300 ohm resistor with ±5% tolerance. These numbers are invented inputs for demonstrating the calculation. Driver and conductor voltage drops are ignored.

At an assumed nominal point of 5.00 V and 2.00 V forward voltage, I = (5.00 − 2.00) / 300 = 0.010 A, or 10 mA. Resistor tolerance gives a range of 285–315 ohms. Using the assumed low-current corner gives (4.75 − 2.20) / 315 = 8.10 mA. The assumed high-current corner gives (5.25 − 1.80) / 285 = 12.11 mA. Thus even this simplified example cannot be described completely by its nominal 10 mA value.

The calculation does not establish that 12.11 mA is safe or that 8.10 mA produces enough light. Actual forward voltage is not an independently fixed constant: the operating point and temperature matter. For a real branch, replace every assumption with justified component and system limits, account for driver and path drops, and check the selected resistor's power and environmental requirements. Missing limits remain an engineering question rather than a value to invent.

Now consider an illustrative purchasing HOLD case. Quote A supplies the bare LED connections and Quote B includes a resistor. Both say '5 V.' If the comparison sheet does not show where current is set, neither a price difference nor this worksheet identifies the finished system's behavior. Return the scope drawing for clarification, then compare the completed electronics and the evidence required to approve them. No actual customer quotation is represented here.

Make the branch traceable through the connector

Give each indicator a branch ID that appears in the schematic, BOM, artwork callout and connector table. The table should show the pin number, net name, anode or cathode connection, and the connector viewing convention. Include any common supply or return and identify whether it is shared with another indicator or switch-circuit connection. A connector drawing with only numbered pads does not show the electrical responsibility.

Ask the OEM electronics team to reconcile that table with its actual output circuit. A label such as GPIO, transistor output or current sink is a starting description, not the full operating limit. Record the controller part or circuit revision and the intended active, inactive and startup states. If the interface changes from a resistor-fed branch to a current-driver load, revise the scope record as well as the pin table.

The first sample should be connected using this released mapping. A continuity check can establish a connection, but it cannot by itself establish operating current or installed visibility. Keep the electrical net map distinct from the mechanical tail/contact-side drawing so that the correct signals also meet the correct mating contacts.

Five failures to investigate at the interface

These are proposed review scenarios, not HYR field-failure statistics. Use them to decide what the first-article record must distinguish. A photograph of an attractive illuminated panel answers a different question from a branch-current measurement. Neither should silently substitute for the other.

• Uncontrolled branch: the panel is bare but the host fixture assumes an installed resistor. Compare the delivered schematic with the fixture before applying the specified test conditions.
• Wrong current-setting value: assembly uses a different resistor or driver setting from the released calculation. Reconcile BOM, component identification and measured current rather than judging brightness alone.
• Polarity or pin-map mismatch: the assembly and OEM board use different connector views or anode/cathode nets. Resolve orientation from both drawings; do not repeatedly power an unidentified branch to find the mapping.
• Parallel branches hidden behind one value: a voltage-fed LED bank is treated as one resistor load without justified branch-current control. Request the actual topology and branch measurements; do not transfer this concern indiscriminately to a regulated-driver architecture.
• Electrical and optical approvals conflated: branch current is acceptable to the electronics team but the mounted indicator is unclear, or a bright sample has no current record. Review the two acceptance items independently.

Approve a powered interface record, then control changes

Define a first-article test with the OEM's electrical design authority. Identify the panel revision, LED and current-setting parts, controller or fixture, supply conditions, relevant states and measurement method. Record current for the branches being approved and the observations needed to compare them with the released electrical design. Keep the test conditions with the result so another team can reproduce the review.

For visual acceptance, install the production-intent panel in representative hardware and use the agreed lighting and viewing conditions. Identify the indicator state being judged. The exact LED part and the surrounding optical stack both belong in that record; color names and an unqualified camera image are not acceptance limits. The optical-zone guide addresses the separate spacer and mask questions.

Before accepting a quotation, ask for the marked delivery boundary, the current-control owner, the calculation or driver record, the pin/net map and the powered approval plan. These five items are a compact completion checklist, not a demand that the membrane supplier take over the OEM's controller design. Clearly mark what remains unresolved so the proposed assembly can be reviewed without implying a completed engineering approval.

A later LED substitution, resistor change, driver change or connector remap should return to the affected records. A change in the optical stack may require a new visibility review even when the branch current is unchanged. Send HYR the proposed interface documents and known gaps for a scoped RFQ discussion; any electrical or manufacturing commitment still requires project-specific agreement.