A resistor-ladder membrane keypad is read by the host board's ADC. Review the acceptable reading range for each individual key and for the no-key state, and check that the ranges remain distinguishable under the agreed conditions. One nominal voltage reading does not approve every recognition window. Include resistor tolerances, ADC and reference errors, the actual connection path and sampling configuration, then retain raw codes and decoded results from matching sample and board revisions. This article covers ordinary, non-safety inputs such as menu selection, not vehicle driving controls, emergency stops, interlocks or medical operating controls.
In its November 2, 2026 Compustar 710HD announcement, Firstech described a new receiver with an integrated vehicle interface module that retains factory climate controls, steering-wheel inputs and camera functions. This is recent equipment-integration news. The announcement does not disclose the key-input circuit topology or identify membrane keys or Baoshengda components.
If your own equipment uses a replacement host board while retaining existing ordinary membrane keys, will the original key recognition still apply? Where your project has confirmed a resistor-ladder input, the handover needs voltage or ADC-code windows with their conditions, not just a key-name-to-function list. The discussion below does not analyze the news product's internal design or prescribe wiring or component values.
Map each key to its electrical branch
Use the current schematic to identify every key, divider branch, common reference and ADC input. State whether the resistor network belongs to the customer's main board, an interface board or the proposed purchased assembly. Printed key names and connector appearance do not establish that mapping. Identify the resistors and connection paths included when a key closes, and retain the component and drawing revisions used.
AN1775, hosted by NXP, illustrates several keys sharing an ADC input through a resistor ladder and discusses resistor precision, ADC error and reading ranges. It describes a particular circuit and older microcontroller. Its resolution, resistor values and window boundaries cannot simply be transferred to another board.
Give each window limits and operating conditions
The electrical designer should review worst-case ranges using the project's circuit and component documentation. Include relevant resistor tolerances, reference and supply relationships, ADC error, and trace and contact effects within the actual branch. After reviewing individual keys, check neighboring windows, the no-key range and undefined regions. Distinct center values do not establish that the ranges remain separate after errors are included.
The following is a suggested review record, not a universal voltage standard. Identify voltage and ADC-code units separately and the reference used for conversion. If limits are unresolved, mark them as unconfirmed rather than filling both limit fields with a nominal value.
| Input state | What to record | Criterion requiring separate agreement |
|---|---|---|
| One key pressed | Key name, electrical branch, predicted range, actual sample raw codes and corresponding decoded results | Within approved conditions, readings belong to that key's window without ambiguity with another valid state |
| All keys released | No-key range, raw codes after release and return of the decoded state | No-key has an explicit identity; the last key value must not persist as a new input |
| Window boundary or undefined reading | Boundary assignment, handling of undefined regions and associated records | The designer defines the handling; do not arbitrarily map a reading to the nearest center value |
| Simultaneous keys allowed by the project | Allowed combinations, actual branches, raw codes and expected handling | Review the specific topology; distinguishable single keys do not prove distinguishable combinations |
Hand over the sampling configuration with the input node
Microchip's voltage-divider guidance relates source impedance to ADC acquisition requirements and notes the response-time trade-off when capacitance is added. Its values apply to the stated device, not membrane keys generally. Consult the ADC documentation for this project and retain input configuration, acquisition time, sampling sequence and reference settings. The responsible designer defines the review needed after channel or setting changes. This article does not recommend adding capacitors, changing resistors or copying another device's timing.
In an approved isolated bench or simulation environment, retain raw codes and software-decoded results for individual keys, release, agreed boundaries and permitted combinations. Associate them with sample, board, firmware and conditions. Do not retain only the final displayed key name: a stable filtered display can conceal the distribution of raw readings near a window boundary. The equipment owner approves the test plan, measurement points and criteria; do not short connections or attach instruments arbitrarily to operating equipment.
Define what the component and host-board suppliers hand over
Shenzhen Baoshengda Technology Co., Ltd.'s membrane-switch customization guidance (Chinese) calls for circuitry and tails to be reviewed against the host interface and for key mapping and continuity to be checked with matching housing and board revisions. Provide your branch diagram, key definitions, actual connection path and approved window table. Separately identify who designs, supplies and verifies the resistor network, ADC readout and firmware. The public guidance does not establish that Baoshengda supplies arbitrary analog interface boards, ADC algorithms or complete equipment functional validation.
A graphic overlay or keypad overlay alone does not include switch circuitry. For a metal-dome overlay used with the customer's PCB, list that PCB and its readout circuit separately. If only the contact assembly is purchased, component continuity or loop-resistance results do not replace equipment-level ADC recognition results. When resistors, board reference, connection paths or firmware settings change, retain the original windows and results and identify changed conditions and items requiring renewed confirmation.
For passive contacts versus interface-board quotation scope, see GPIO supply-boundary checks (Chinese). Row-and-column combinations are addressed separately in matrix ghost keys versus short circuits (Chinese). Use the project contact page to share branch mapping, the window table and unresolved items; see the English membrane-switch product page for the product scope. The cover shows an existing blue multi-key overlay, pale printed circuitry, tails and a lifted release liner. It does not establish an internal resistor network or verified ADC recognition.