For a mixed HMI, list each command and the confirmation the operator must receive before choosing a touchscreen zone or physical key. Touch detection, active haptic output, a membrane-key dome and a visible status indication are separate functions. A front-panel supplier can review physical construction and the circuit. The equipment owner defines the command response and approves the complete interaction. Put those owners on the same drawing revision before asking for a quote.
A current example makes the boundary easier to see. In its GV90 in-cabin release, published 2026-10-08, LG describes an eight-inch console touch screen for functions including HVAC, doors and seats, and says that screen has haptic feedback. LG also describes a separate communications unit. The release does not disclose the touch-screen haptic actuator design, specify a membrane key or name Baoshengda as a supplier. It is an example of system-level feedback ownership, not component acceptance evidence.
The older August 14, 2026 haptic-interface review classifies tactile sensing and feedback across several interaction scenarios. Its useful lesson for this article remains the distinction between detecting an input and giving the operator a response. Neither source sets the actuation force, travel, timing or safety behavior of a Baoshengda panel.
What the August 14 haptic review adds
Interactive Haptic Interfaces: From Tactile Sensing to Integrated Feedback Systems was published on August 14, 2026. The review groups interaction scenarios such as virtual-to-human, human-to-virtual, human-to-robot, robot-to-human and human-to-human, and separates tactile sensing from haptic feedback.
The review is not a Baoshengda HMI test and does not prescribe a dome, actuator, key layout, tail or connector. Detecting touch alone does not give the operator physical confirmation. The panel designer must specify that response separately.
Assign feedback ownership before copying a function across surfaces
The buyer risk is treating the word “haptic” as a transferable component requirement. A touchscreen may report contact and produce an active cue through its controlled system. A membrane key may give a dome snap when pressed. Neither cue alone proves that the equipment accepted the command. If a control moves from one surface to the other, the equipment team must repeat the function and confirmation review rather than carrying the old icon and acceptance result forward.
Use a control-by-control record with these separate columns: input surface and sensing owner; physical feel or active cue owner; visible or audible status owner; controller response; and the mounted acceptance case. For a membrane key, check the dome or emboss, actuator footprint, rear support, electrical closure, tail and connector after installation. For a touch zone, ask the system integrator for the touch and haptic implementation and its test method. The panel supplier should not quote an undisclosed touch actuator or claim that its passive printed overlay supplies the screen's active feedback.
| Control decision | Front-panel supplier evidence | System-owner evidence |
|---|---|---|
| Physical membrane key | Artwork, active zone, dome or emboss construction, tail pin map and mounted feel | Command mapping, debouncing, accepted-state indication and use-condition approval |
| Touchscreen zone with active haptic cue | Any separate printed border or overlay window geometry within the agreed scope | Touch detection, cue generation, controller response and installed interaction test |
| Shared icon or command across both | Revision-controlled legends, window/key datums and sample identification | Consistent command meaning, differing feedback method and failure-state behavior |
LG's example identifies functions and a haptic CTS, but it provides none of these part-level tolerances or mounted results. The drawing and test plan must come from the buyer's actual HMI architecture. The existing physical HMI cover photographs a membrane panel. It does not show the LG system or measured key feel.
Separate sensing from feedback in the panel map
Start with the command map. For every control, mark what the system senses and what the user must feel or see in return.
A touch position can be sensed without any tactile response. A physical key can produce a dome snap, an embossed surface, or a clear travel stop. A screen or robot face can add visual feedback, but it may be weak in motion, glare or glove use.
Do not assign the same feedback to every key. A start command, stop command, mode change and menu navigation can need different physical and visual treatment.
Assign the physical feedback boundary
For each control group, decide:
- physical key, touch zone or screen command;
- metal dome, emboss, flat non-tactile or another actuator;
- key travel and actuation force;
- visible confirmation through LED, backlight or display window;
- haptic feedback from the host system where applicable;
- required glove or wet-hand behavior.
An HMI panel solution review should keep the sensing layer and feedback layer in the same controlled package.
Use a feedback decision table
The table below converts the haptic framework into panel evidence. It is a review tool, not a universal pass and fail standard.
| Interaction signal | HMI panel question | Required evidence |
|---|---|---|
| Tactile sensing detected | Does the control also produce a physical confirmation? | Key travel, dome or touch response |
| Haptic feedback required | Which actuator or host system supplies it? | Feedback source and latency boundary |
| Virtual-to-human scenario | Can the panel remain legible without the virtual cue? | Fixed icon, label and LED state |
| Robot-to-human state | Does the operator know a command was accepted? | Visual plus physical confirmation map |
| Glove or motion use | Is the tactile response still identifiable? | Mounted sample test under the real condition |
Do not let one team change the haptic engine while another team changes the membrane key. The sensing, feedback, artwork, key and connector evidence must share one revision package.
Keep visual and haptic confirmation independent
A screen vibration or robot expression can be secondary feedback. The primary confirmation for a critical command should not depend on a host animation that may be delayed, disabled or washed out by sunlight.
For high-priority controls, use a fixed physical key with a stable tactile response and a separate LED or display state. For routine navigation, a touch or flat key may be acceptable when the screen remains visible.
The panel tail and connector also belong in the feedback plan. A key can feel correct on a loose sample and change after the tail is folded, the connector is mated, or the housing closes. Confirm the route and mounted feel together.
Test the mounted panel under the real interaction
Use the intended housing, glove or bare-hand condition, lighting, motion and actual command sequence. Test three observations separately: the input is detected, the expected physical or active cue occurs, and the controller shows the accepted state. Repeat after the panel is mounted and the tail is routed. Log unintended touches, missed electrical closures, weak dome feel, an absent or delayed host cue and connector access. A vibration, click or lit icon without the accepted controller state is an incomplete result.
The buyer defines the acceptance limits. The research review does not provide a universal haptic latency, force or actuation requirement for a Baoshengda panel.
Supplier boundary and limitations
The cited review is original haptic-interface research. It is not a Baoshengda test, an ergonomic certification, a safety analysis or evidence that any HMI panel is suitable for a product. Baoshengda can review the membrane switch construction, key and dome layout, overlay, backlight, tail geometry, connector and physical sample evidence for an agreed design. The buyer remains responsible for the complete HMI system, haptic engine, safety logic, environmental conditions and final product validation.
Do not copy a haptic classification or latency example from the review into a panel specification. The equipment owner must define the interaction requirements and acceptance evidence.
HMI haptic-feedback RFQ checklist
Send these items before requesting a firm prototype plan:
- control-by-control matrix naming the input surface, sensing owner, physical or active cue owner, visible status and controller response;
- separate mounted acceptance cases for touch and physical keys, including what happens when feedback or confirmation is absent;
- command map with sensing and feedback functions;
- physical key function list and touch versus physical control boundary;
- dome, emboss, actuator and key travel requirements;
- visual confirmation through LED, backlight or display window;
- haptic feedback source and latency boundary if the host supplies it;
- overlay artwork, window and label positions;
- tail exit, service loop, bend route and connector or pin map;
- glove, motion, lighting and mounted sample test plan;
- prototype quantity, production estimate and controlled revision numbers.
For an RFQ, send the control and feedback ownership matrix with the artwork, key section, housing support, tail pin map and identified sample conditions. Ask for an HMI panel construction review and request a quote for the physical part only. The equipment owner retains touchscreen cue design, controller behavior and final use validation. Use the same revision IDs when comparing mounted samples.
Need help reviewing a structure?
Send your drawing, photos, application, and quantity. Baoshengda can help check the structure before sampling.
Send Drawing for Quote