Before quoting a sidewalk delivery robot service keypad, freeze the recovery-state map and the mounted environmental interfaces together. Name who can wake, pause, recover, release a controlled access request or place the robot in service mode, and define what each key does in every allowed and blocked state. Then control the overlay, tactile zones, sealing land, tail exit, connector, strain relief and enclosure support as one assembly. Approve it through dry-fit, controlled wet-use and recovery-state tests on a representative robot hatch. An A3 deployment update published August 27 reports more than 2,000 deployed sidewalk robots and new micro-depot activity. That scale makes repeatable service evidence a practical sourcing issue, not merely a styling detail.
Quote the recovery map before counting keys
A drawing that asks for `three service buttons` does not define a usable interface. One key might request a normal pause, another might acknowledge a recoverable fault, and a third might open a controlled service sequence. Their electrical contacts can look identical while their permitted users, controller responses and acceptance evidence differ.
Start the RFQ with a state-action table. It should belong to the robot owner or system integrator and should use the same key IDs as the artwork, circuit map and test script.
| Service condition | What must be frozen before quotation | Evidence for sample approval | Boundary to keep explicit |
|---|---|---|---|
| Normal delivery wait | User role, permitted wake request and feedback | Mounted key actuation plus visible controller acknowledgement | The keypad requests an action; it does not decide route readiness |
| Ordinary pause | Allowed robot states, press behavior and resume authority | Accepted and blocked-state responses on the controlled test setup | Ordinary pause is not automatically a safety-rated stop function |
| Recoverable fault | Fault class, acknowledgement sequence and next permitted state | Repeatable recovery attempt with the exact controller and software revision | The component supplier does not define the robot fault strategy |
| Service or depot mode | Authorized user, access method and functions exposed | Service-mode entry, exit and denied-use checks | Access control and maintenance policy remain system responsibilities |
| Water or contamination event | Inspection trigger, dry-out or cleaning rule and release owner | Controlled wet-use test followed by continuity, key and recovery checks | A generic water claim cannot replace the buyer's mounted test condition |
The timely A3 article is deployment context, not proof of a particular robot keypad. It shows why charging, staging and servicing infrastructure matters as fleets expand. The buyer still has to define the robot states, environmental exposure, safety architecture and service procedure for the actual project.
Separate public recovery from technician authority
A sidewalk robot operates around members of the public, weather and curbside obstacles. That does not mean every external control should expose maintenance functions. Divide controls by authority before deciding where they sit on the enclosure.
A public-facing recovery input might request a simple assistance state, but it should not enable motion, bypass a fault or enter depot diagnostics without the controller's authorization. Technician functions can require a protected hatch, keyed access, a separate service connector or a defined electronic credential. If a key is intended only for a depot technician, put that restriction in the artwork and state table rather than relying on training alone.
Also decide what happens when an input is pressed in the wrong state. A blocked request should create an agreed feedback response or remain deliberately inactive. A button that sometimes appears to work because the controller accepted a request late is difficult to diagnose in the field. Capture debounce, long-press, repeat, simultaneous-key and stuck-contact assumptions in the controller-side specification.
The physical interface can support clear key spacing, tactile differentiation and protected placement. It cannot police user identity or guarantee that higher-level software applies the correct authority rule.
Freeze the wet-side mechanical stack
Outdoor quotation language often collapses to the word `waterproof`. That is not enough to select an overlay, adhesive or gasket. Describe the actual exposure: rain, splash from wheels, condensation after temperature change, wet gloves, cleaning spray, road film or brief pooling at a horizontal edge.
Control these drawing interfaces as one mounted stack:
- the complete keypad outline and front-edge sealing path;
- the enclosure recess, surface finish and supported adhesive land;
- any gasket location, compression target and corner continuity supplied by the enclosure owner;
- the display-window opening and the rigid support behind each tactile zone;
- screw, latch and hinge locations that can distort the hatch;
- drainage direction so water is not trapped against the keypad edge or tail exit;
- acceptable gaps and steps after the production-intent hatch is closed.
A loose panel on a flat bench cannot reveal a bowed hatch, interrupted adhesive land or fastener that lifts a corner. Sample approval should name the hatch material, coating, gasket, fasteners and assembly method. If the enclosure revision changes, the owner decides which wet-use and adhesion checks must be repeated.
Avoid turning the component quote into an unsupported ingress rating. The complete robot enclosure, seams, vents, sensors, charging ports and service doors affect system performance. State the mounted test method and pass criteria instead of asking the keypad supplier to infer a device-level claim.
Treat the tail exit as a service interface
The cover-side keypad can look correct while the hidden tail fails during assembly or depot replacement. Freeze the tail route from the printed circuit to the mating connector. Show the exit slot, first-bend keepout, tail length, conductor side, stiffener, exposed-contact or connector definition, pin-one orientation, mating part, latch access and strain-relief location.
The route should stay clear of the hatch hinge, fastener tips, sharp ribs and any path where pooled water can follow the tail inward. It also needs enough controlled slack for the hatch to open without pulling the connector, but not so much loose tail that it rubs a wheel well or moving linkage. If technicians disconnect the panel during service, specify the allowed pull point and the number of representative replacement cycles used in sample evaluation.
Do not approve only front-side continuity. Inspect the mounted circuit while the hatch moves from service-open to fully closed. Check whether the tail twists, creases, slides out of its clip or pushes the connector sideways. Then repeat electrical and key-response checks after the environmental sequence, not only before it.
Build a mounted sample sequence that can fail usefully
A useful sample plan exposes the uncertain interfaces in stages. It should let the team identify whether a problem comes from artwork, mechanics, environment, connector routing or controller logic.
**1. Drawing and state review.** Close the key IDs, state-action table, circuit map, connector definition, enclosure datums, sealing interfaces and open-item list. Do not cut production tooling while authority or tail geometry is still provisional.
**2. Dry mounted fit.** Assemble the keypad on a representative hatch. Check edge contact, key support, window registration, hatch closure, tail bend, connector access and strain relief. Exercise every key in allowed and blocked states on a controlled controller setup.
**3. Controlled wet-use exposure.** Apply the buyer-defined rain, spray, condensation or wet-glove condition with the robot or representative fixture in the stated orientation. Record where water is applied, duration, temperature, hatch condition and whether the robot is energized. Avoid dramatic hose tests that do not match service conditions.
**4. Post-exposure recovery.** Inspect for edge lift, moisture at the tail exit, false activation, missed input, altered tactile response and connector contamination. Run the recovery-state script again and compare results with the dry baseline.
**5. Depot replacement trial.** Use the intended tools and access route to remove and reinstall the keypad or hatch assembly. Confirm connector handling, routing, seal restoration and revision identification. A successful first build does not prove a service spare can be fitted consistently.
Each result should name the keypad, hatch, gasket, controller, software, test fixture and procedure revisions. Photographs can support the record, but they do not replace measured acceptance limits or the state-response log.
Know what the keypad supplier can approve
A custom membrane-switch supplier can manufacture the printed overlay, display window, tactile or non-tactile key stack, spacer, adhesive geometry, printed circuit or FPC, tail, stiffener, connector and agreed indicators. The supplier can inspect dimensions, print registration, appearance, continuity, contact behavior, tail geometry and connector assembly against controlled inputs. It can also support component-level samples and agreed material or cleaning checks.
The supplier does not own autonomous navigation, remote assistance policy, public-access authorization, obstacle detection, brake or motor control, battery and charging safety, cybersecurity, fleet software, risk assessment, regulatory obligations or final robot validation. An ordinary membrane-switch contact must not be described as a validated safety stop unless the qualified system owner has designed and verified that function separately.
Put this boundary in the quotation and sample report. It prevents a passing keypad continuity test from being read as approval of the complete robot recovery system.
Send one drawing, sample and RFQ pack
For a waterproof membrane switch with controlled sealing, tail and connector interfaces, send a revision-controlled package that includes:
- robot purpose, installation location, operating climate and realistic rain, condensation, cleaning and contamination exposure;
- user-role list plus one state-action row for every wake, pause, acknowledge, recover, service and denied input;
- clear separation between ordinary HMI requests and any independently validated protective function;
- front artwork, key IDs, tactile requirements, display window, indicator locations and night or glare conditions;
- circuit map, connector-side pinout, mating-part definition, polarity and buyer-supplied electrical limits;
- panel outline, hatch cutout, recess, adhesive land, rigid key support, gasket path, screw and hinge datums;
- tail exit, first-bend keepout, routing, length, stiffener, connector orientation, latch access and strain relief;
- dry-fit, wet-use, post-exposure recovery and depot-replacement test conditions with acceptance criteria;
- exact hatch, gasket, PCB, harness, controller, software and fixture revisions used for approval;
- prototype quantity, expected annual quantity range, packaging, traceability and change-notification needs.
Submit the package through the Request Quote page. A supplier can then quote the physical keypad and mounted sample evidence without guessing about robot authority, outdoor exposure or service access.
Need help reviewing a structure?
Send your drawing, photos, application, and quantity. Baoshengda can help check the structure before sampling.
Send Drawing for Quote