IO-Link Retrofit HMI RFQ: Define Local Maintenance Controls Before Quotation

Before asking for a membrane HMI quote for an IO-Link retrofit, divide every maintenance action between the fixed local panel and the PLC or PC tool. Keep only actions that need predictable at-machine access, such as an acknowledgement request, sensor teach request, mode request and display navigation, all subject to controller authorization. Put parameter editing, device identity, diagnostic history and configuration transfer in the software layer. Then freeze key IDs, state feedback, circuit, enclosure support, tail, connector and sample test as one package. This prevents the keypad supplier from guessing which functions belong in hardware and prevents a passing continuity check from being treated as approval of the machine control strategy.

An OMRON industrial-automation update published August 28, 2026 describes how IO-Link devices can reduce work around sensor connection, parameter setup, commissioning and replacement. Its practical message is that factories want less preparation and faster recovery, not data collection for its own sake. The source does not specify a Baoshengda keypad. It creates a timely buyer question: when diagnostics become richer and more software-driven, what must still remain clear and testable at the machine enclosure?

Start the quotation with a responsibility split, not a key count

A request for a six-key panel says almost nothing about the control responsibility. Two keys can share the same electrical contact style yet have very different conditions for use. One might move through display pages. Another might request that the controller acknowledge a non-safety process fault. A third might ask the controller to start a sensor teach sequence, but only while the machine is in an approved setup state.

Create a local-action matrix before artwork approval. Use the same key IDs in the matrix, circuit drawing, firmware map and sample script. The quotation should show who owns the decision, not just where the key sits.

This table keeps the membrane switch inside its proper scope. The panel creates contact inputs and visible interface zones. The controller decides whether an action is accepted, and the machine builder owns the control and safety architecture.

Decide which actions must remain at the machine

A local key is justified when the operator or technician needs a stable physical action at a known location, especially while looking at the sensor, fixture or workpiece. It is not justified merely because the older machine already had that function on a keypad.

Evaluate each proposed key against four questions. Must the user stay beside the machine to perform the task? Is the action needed when the engineering PC is absent? Can the controller clearly show whether the request is allowed? Does the action remain understandable across device and software revisions? If the answer is no, the function may belong in the protected software workflow instead.

Typical local candidates include page navigation, a limited maintenance-mode request, a non-safety fault acknowledgement request and a clearly bounded teach request. Detailed parameter values, device catalog data, trend history, bulk configuration and vendor-specific diagnostics usually fit the PLC, HMI software or engineering tool better. Keeping those data off a small membrane panel avoids crowded artwork and reduces the chance that a replacement overlay misrepresents a software-only function.

Do not use a thin-film key as a substitute for a separately engineered protective device. If a machine requires a safety-rated stop, guarded reset or other protective control, the qualified system owner selects, integrates and validates that hardware and logic independently.

Keep diagnostic visibility separate from command authority

IO-Link can expose identification, parameter and diagnostic information that conventional on-off wiring does not. Richer information does not mean every diagnostic message should become a local command. The front panel needs a concise indication that helps a person decide what to do next, while the software layer can retain the detailed cause and service record.

Define what the display window or indicators show for at least these conditions: normal, setup requested, request denied, device missing, device mismatch, communication unavailable and service required. A local indication should not promise that a sensor has been configured merely because a key contact closed. The controller must confirm the accepted state and drive the feedback.

Also freeze timing behavior. Specify short press, long press, repeat, simultaneous input, debounce and stuck-contact assumptions where they matter. If the panel has LEDs, state whether each indicator is driven directly, through the controller or through a separate circuit. Include voltage, current, polarity and connector-pin evidence supplied by the buyer.

The result should be a traceable chain: physical input, controller decision, software or network action, device response and visible confirmation. Sample approval is incomplete if only the first link was tested.

Freeze the mounted panel, tail and connector together

An IO-Link retrofit often changes the cabinet layout, sensor wiring and service access. The membrane HMI may be physically simple, but its tail can conflict with a new I/O block, cable gland, door hinge, DIN-rail component or wiring duct. Quote the panel as an installed assembly rather than an isolated front graphic.

The drawing package should control:

• overall panel outline, display window, key centers and tactile or non-tactile zones;
• enclosure cutout, recess depth, surface finish and rigid support below each active key;
• continuous adhesive land or gasket relationship, corner radii and prohibited gaps;
• tail exit position, conductor side, first-bend keepout, length and allowed fold direction;
• stiffener, exposed-contact or connector specification, pin-one orientation and mating part;
• clearance from hinge hardware, cable glands, wiring ducts, sensor leads and service tools;
• connector access for initial assembly and later panel replacement;
• artwork, circuit, enclosure and firmware revision references on the approval record.

The first bend deserves a real dimension. A tail that fits while the door is open may crease, twist or pull the connector when the door closes. Excess slack can rub against wiring or become trapped under a cover. Test the entire door movement using the intended routing clips and mating connector, then repeat continuity and key checks.

Approve samples through commissioning and sensor replacement

A useful sample sequence follows the work that created the retrofit. It should expose errors before production quantities are ordered.

**Mechanical fit review.** Install the panel on the representative door or bezel. Confirm edge contact, display registration, key support, tail slot, bend keepout, connector reach and enclosure closure. Photograph the route, but also record controlled dimensions and revisions.

**Electrical mapping review.** Check every key ID against the circuit and controller input. Verify connector orientation, common circuits, indicator polarity and any unused pins. Use the buyer's electrical limits rather than an assumed generic interface.

**State-action review.** Run each local request in allowed and denied machine states. Confirm that the controller feedback matches the matrix. Include repeated presses, simultaneous keys and a disconnected tail where these conditions are relevant.

**IO-Link commissioning review.** Connect the named master and representative sensors. Exercise the teach or setup request only through the approved state. Confirm that parameter work remains in the software layer and that the local panel shows a concise accepted, denied or unavailable result.

**Replacement review.** Substitute a correct device, an incorrect device where safe for the test fixture, and a disconnected lead. Verify identification, parameter restoration, local feedback and recovery steps. Then replace the membrane panel or door assembly using the intended service access and repeat the critical checks.

Record the keypad, enclosure, connector, controller, IO-Link master, sensor, configuration file, software and fixture revisions. A pass on one combination does not approve every future device or cabinet revision.

State the component supplier boundary

A membrane-switch supplier can manufacture the overlay, window, tactile stack, spacer, adhesive geometry, printed circuit or FPC, tail, stiffener, connector and agreed indicator features. The supplier can inspect print registration, dimensions, appearance, continuity, contact behavior, tail geometry and connector assembly against released inputs. It can also support component samples and agreed mounted-fit checks when the buyer provides the representative enclosure and test conditions.

The supplier does not define the IO-Link network, select the master or sensor, create device-description files, write PLC logic, decide parameter values, authorize maintenance states, design machine interlocks, validate protective functions or approve the completed machine. It also cannot confirm that a software diagnostic is correct from a keypad continuity result.

Write this boundary into the quotation and sample report. It protects both parties from treating component conformance as system acceptance. It also gives the buyer a clearer change-control rule: a new sensor, controller, connector, enclosure or firmware revision can trigger only the relevant retest instead of forcing an undefined full restart.

Send one drawing, sample and RFQ package

For a custom industrial automation HMI with controlled key, window, tail and connector interfaces, send one revision-controlled package containing:

• machine type, retrofit purpose, installation location and operator or technician roles;
• local-action matrix with key IDs, allowed states, denied states and required feedback;
• explicit separation between ordinary HMI requests and independently validated protective controls;
• front artwork, display window, indicator plan, key spacing and tactile requirements;
• circuit map, electrical limits, connector pinout, mating part and pin-one orientation;
• enclosure drawing with cutout, recess, support land, hinge, cable gland and wiring-duct datums;
• tail exit, first-bend keepout, route, length, stiffener, connector access and strain relief;
• IO-Link master, sensor and controller references needed only for the agreed sample sequence;
• mechanical, electrical, state-action, commissioning and replacement acceptance criteria;
• prototype quantity, expected annual range, packaging, traceability and change-notification needs.

Submit that package through the Request Quote page. The supplier can then quote a defined physical HMI and evidence plan without guessing which maintenance functions belong on the panel or in the IO-Link software workflow.