At a machine-tending station, the ordinary confirmation key on a membrane panel submits a recipe. Show “Applied” only after the controller responsible for execution confirms it has applied the recipe and the recipe ID and revision read back from that controller match the request. A completed transfer, a lit button or a new screen does not prove that the recipe is active. This is a recipe check, not a robot start command or a safety permission.
On November 11, 2026, DOBOT announced robotics platforms in Frankfurt and named machine tending, sorting and assembly as uses for PULSA. The announcement did not describe its keys, its recipe workflow or any Baoshengda supply relationship. In a separate project that handles several part types at one station, changeovers may use the same physical panel. If the operator selects B on screen, how can they tell whether the controller is using B or still running A?
The selected recipe and the recipe in use
Use separate fields for the recipe pending application and the recipe currently in use. If the screen says “Pending B” but the controller still reports A, show both. Put the recipe name and revision in the changeable display area. If the physical key only submits the request, label it “Apply recipe,” not “Changeover complete.” If the display uses a short name, keep the actual ID and revision in the record.
The Siemens WinCC Advanced V14 SP1 communication manual distinguishes a data-record transfer in progress from a transfer that ends with or without an error. Those are transfer states, not proof that another machine has applied a recipe. If the project also selects a robot task or confirms a fixture, identify the controller that applies the recipe and the readback that proves it. Record the key input, transfer feedback and recipe application separately. See also membrane-key indicator lights and action results (Chinese).
Test with B selected but not yet applied
In a project-approved offline or non-driving environment, make A the active recipe, then select B and check the following cases. After the normal changeover works, test with late feedback to see whether the screen mistakes a previous result for confirmation of the latest request. This checklist is a suggested engineering check, not a requirement from the Siemens manual or DOBOT announcement.
- B is selected but has not been requested: keep “Current: A” visible. A highlighted list item is not an applied recipe.
- B was requested, but the transfer is incomplete or the controller still reports A after it ends: log the transfer state and the controller readback. Do not mark B as applied.
- B was requested, the operator then selected C, and feedback for B arrived late: use a request ID or equivalent to match late feedback to its own request, not to C. If the active recipe cannot be verified from readback, mark it unconfirmed.
- The controller responsible for execution confirms application of B, and the ID and revision read back match the request: confirm only that B is active. Do not record the fixture, part or robot movement as accepted.
Keep the key input, request ID, target ID and revision, transfer result, controller readback and screen display side by side in the commissioning record. If the input arrives but readback differs, check recipe application and the feedback path before replacing the membrane switch. If the physical key action differs from its label, see how to check HMI key functions against printed labels (Chinese). Emergency stops, enabling devices, interlocks and robot motion validation remain separate tasks for the equipment owner.
The Baoshengda custom membrane switch page describes confirming keys, circuitry and tail connections against equipment operation, the board interface and installed samples; see the Chinese product reference. When ordering only a membrane panel or keypad overlay with no switch circuitry, check the surface part scope, including labels and fit. The equipment maker defines the recipe logic. The cover is an exploded view of a membrane switch, not the station configuration or evidence of software capabilities.
If you are specifying this panel, use the project contact page to share a key layout, fixed legends and display location if those details can be shared. Identify the controller responsible for recipe readback, what the confirmation key does and which checks are planned for the prototype.