EV Charger Keypad RFQ: Define Feedback States Before the Key Layout

For each EV charger key, separate the physical press, the controller's acceptance of the command and the equipment state shown to the user. A sample approval record should identify the signal and owner at each step. A local acknowledgement of a START press is not evidence that the charger is delivering power. Define the command-to-feedback map before approving the artwork for a custom backlit membrane switch.

Specify waiting feedback when the controller supports it

On 2026-10-20, LAZ and indiGOtech announced an apartment and condo charging joint venture, with EverCharge SmartPower as the first offering. The release describes chargers sharing a building's available electrical capacity. Its deployment and power-management description supplies no membrane keypad specification or measured interface result.

For a charger whose controller permits a waiting or constrained-power state, a valid start request may need a different indication from controller-confirmed charging. Whether that state exists, what causes it and what the user should see must come from the equipment owner's actual state machine. The announcement does not establish those behaviors for a particular charger, and it provides no evidence that the named companies use Baoshengda components.

The relevant component question is how the panel will represent the states the buyer actually specifies. If one lamp covers both an accepted request and confirmed charging, ask how the user can distinguish them. A separate window, display message or documented light pattern might be appropriate; the system team must choose and validate the meaning. Adding a brighter LED cannot resolve an undefined meaning.

Show these meanings on the drawing before fixing illuminated areas, circuit channels or connector pins. The supplier needs the panel brief; the equipment owner controls electrical-capacity allocation.

Give every key a command and evidence record

List the project's actual states, such as unavailable, ready, authorization pending, connector detected, charging, paused, complete, fault and service. Identify public-user and service-only states. Do not assume every project needs this whole list or that each state needs its own lamp.

For each key, record when it is active, the permitted press type, the immediate response, delayed or rejected behavior, and the device responsible for deciding the result. Keep the key identifier consistent between the artwork, circuit drawing, controller input list and test record. Distinguish a tactile response from a contact closure, a received command and an accepted command.

Use a record with enough detail to locate an ambiguous transition:

Use this record format with the project's state machine and agreed timing limits. It contains no completed test results or universal acknowledgement time. Keep electrical observations and controlled pass or fail records alongside any video of the sequence.

Assign each light to a defined owner

A membrane keypad may provide fixed legends, tactile keys, transparent indicator windows, backlighting, a flexible circuit tail and an electrical connector. LEDs may be included when agreed for that construction. The panel does not independently know whether authorization succeeded, the connector locked, power is flowing or a receipt is complete. Those meanings depend on the appropriate controller or software signal.

Assign feedback to the relevant channel: tactile response, a local light, charger display text, an equipment-controlled sounder or a remote record. Identify which channel each observation actually verifies. If a lamp has several meanings, control its colors, steady or flashing patterns, timing ranges, startup appearance and communication-loss state. Document which indication takes priority when states overlap.

The electrical handoff should specify the supply, voltage and current limits, polarity, circuit arrangement and pin assignment. Identify whether the controller switches the high side, low side or another agreed circuit. Number the keys, indicators and common circuits consistently. Show the connector viewing direction and mating orientation so the supplier and PCB drawings do not reverse the pin order.

For lighting, agree the inactive appearance as well as the illuminated appearance. Identify daylight-readable legends, any dead-front requirements, brightness control, uniformity and acceptable adjacent-zone light leakage. A faint inactive icon may be acceptable on one design and misleading on another. Keep these choices tied to the actual screen, accessibility needs and market requirements rather than copying colors from an unrelated charger.

Keep the mounted construction in the approval

Separate frequently used public controls from maintenance and reset functions. Review spacing, shape, embossing, active area, overlay material and finish, tactile target and backlight allocation. A gloved outdoor action may require different geometry from a protected service key. Show the keypad-to-display spacing where arrows, colors or wording could be confused.

Keep emergency and legally required safety functions within the equipment owner's validated architecture. A printed red area does not establish an emergency-stop function. Do not make a service reset accessible as an accidental public navigation action.

Include the housing opening, adhesive landing, ribs, fasteners, display bezel, drainage and tail exit. Define tail length, allowed bend zone, flat region, stiffener, connector access, service loop and strain relief. Check that the mating connection remains accessible after enclosure closure. The housing and adhesive must support the intended key geometry.

Test the bonded assembly on its intended housing or a controlled representative fixture. Use the target controller or identify the simulator and its limitations. Record continuity and pin checks before and after mounting, connector seating, tail retention and service access. Bench continuity alone leaves the charger state transitions untested.

Run allowed, delayed, rejected, blocked and ignored actions under the applicable states. Include startup, restart, communication loss and power recovery, plus rapid repeats, long presses and simultaneous keys where relevant. Check the named daylight, night, glove, wet-use and environmental conditions, including cleaning method and temperature range. These are project-defined requirements, not performance claims for the pictured keypad.

Keep expected and observed results in the same record. If firmware changes a timing rule, priority or status output, update the state-table revision and repeat affected approval tests. Record the controller, artwork, circuit and mounted-fixture revisions together.

Keep the earlier research in its proper role

The original guide cited EV charging-context research first published on 2026-08-12. Its analysis covered 202 charging events from 21 participants. Lower state of charge was associated with selection of higher charging rates and more negative emotion before charging; charging rate was not a significant predictor of post-charging emotion. The authors highlighted charging context and information about availability and range prediction.

Those observations describe that study, not a keypad performance result or a universal user response. Keep them as background for the information brief. They do not establish an indicator color, a charging-state algorithm, a safety function or a guaranteed improvement in user experience.

Start an inquiry before every drawing is finished

An existing panel photo or sketch, the intended user action, approximate quantities or one unresolved feedback question is enough to start a keypad engineering inquiry. If a drawing or controller I/O list is already available, include it. A complete production drawing package is not a prerequisite for first contact.

Before sample release, close the open items in the command/state map, artwork and electrical handoff. Confirm the active areas, lighting zones and inactive appearance, tail and mating details, housing and adhesive conditions, exposures and cleaning, quantities and controlled revisions, and mounted acceptance records. A firm quotation or prototype plan may need these details resolved even when the initial conversation starts with a photo.

Baoshengda's component review covers the agreed overlay, tactile construction, lighting, printed circuit, tail, connector and physical sample evidence. The charger owner retains responsibility for software, payment, cybersecurity, power electronics, availability data, regulatory compliance, safety and final equipment validation.

The retained product photograph shows modem-status keypads with complete tails and connectors. It illustrates physical keys and indicator windows, not an EV charger installation, a charging-state layout or a verified test result.